procurement_coverage_cells: 68
This data as json
| rowid | source_key | source_label | record_kind | record_kind_label | fy_key | state | n_records | prev_n_records | why_code | why_text | evidence_kind | evidence_sql | evidence_citation | evidence_lf_id | probed_for_publication | is_crawl_dependent | drill_url | computed_at | run_id |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 68 | checkbook | Territorial checkbook | purchase-order-reference | A purchase order, encumbrance, contract or award number on a payment | not-applicable | NOT HELD | 0 | 0 | no-po-field-on-payments | Not one field of the published payment feed names a purchase order, an encumbrance, a contract or an award. The 46 keys the feed publishes were enumerated once by hand, and the query beside this cell re-checks every column we ingested from them on every run. The one free-text field is cut at source: its longest value is 30 characters, 142,218 rows sit exactly at that length and 0 are longer, so an identifier written into it is routinely cut mid-string - 50 of 365,361 rows carry a full-shape purchase-order number at all. This is not a join we have not built. It is a field the government does not publish. We probed this feed and make no claim about any other government publication. | MEASURED | SELECT COUNT(*) FROM pragma_table_info('checkbook') WHERE lower(name) LIKE '%purchase%order%' OR lower(name) LIKE '%encumbr%' OR lower(name) LIKE '%contract%' OR lower(name) LIKE '%award%' | 1 | 0 | /procurement/coverage#why-no-po-field-on-payments | 2026-11-21T22:40:46Z | 2026-11-21T22:36:15Z |