The union counts rows once; 62 rows match both sources and 2,362 have no current match in either. Proposal links use direct title matches or selected NEP counterparts; Senate matches use title-linked support files and uniquely resolved file-code siblings. File presence does not verify document contents. T5 / Cloudflare file check: 34,418 of 34,420 manifest files are SHA-256 verified across the source folder and parser cache; 34,317 of 34,317 available PDFs have scan records; 2 manifest entries are currently unavailable on T5.
Proposal and Senate supporting documents · All HGAB projects
The combined row count includes Proposal documents matched directly or through selected NEP–HGAB counterparts, plus Senate HGAB files. Each HGAB row counts once. The chart separates Proposal matches from Senate file matches by type; each source count deduplicates HGAB rows, and categories can overlap. “Other” is not one of the five named types used for document-set completeness.
Loading all-document scan…
Download all-HGAB document matches and extracted signatory candidates ↗
How these counts are computed
The denominator is all HGAB project rows. Proposal documents link directly by title or through a selected NEP–HGAB counterpart. Senate PDFs link by exact or accepted relaxed first-page title, or by a file in a uniquely resolved HGAB code. Ambiguous code links are left unassigned. Each source and document type deduplicates by House row ID; source counts and categories can overlap. Signatory names are document-extracted candidates, not verified identities or a current officeholder roster. Photo pages and embedded coordinates are not content-verified. A row without a match is not proof that no document exists.
All HGAB projects · document matches and signatories
One row per HGAB project. Proposal documents, Senate HGAB files and extracted signatories are listed in separate columns. Signatories are document-extracted candidates, not verified current officials or project sponsors. Document presence does not verify contents.
Download all HGAB project rows as JSON ↗
| HGAB code | Project | Office · region | HGAB allocation | Proposal docs | Senate HGAB docs | Signatories in related documents |
|---|---|---|---|---|---|---|
| Loading all HGAB document coverage… | ||||||
Senate-provided HGAB POW line items
These machine-extracted line items come from HGAB files provided by the Senate. Exact title matches identify House ledger projects; amounts and descriptions remain under verification. Source paths and links are withheld.
Compare HGAB allocations with matched POW estimates →
Parsed line-item details load after the project summary.
| Senate HGAB file code | Matched House ledger project | Bill item | Quantity | Unit | Amount | Cost category | POW page |
|---|---|---|---|---|---|---|---|
| Loading parsed HGAB bill details… | |||||||
How parsed bill totals are counted
Bill rows and amounts are machine-extracted from parsed POW PDFs. The counts describe recovered parser rows and do not verify the printed quantities or amounts; extraction coverage can lag the number of scanned files.
Senate BP 202 and POW file matches · All HGAB projects
This section summarizes rows linked to Senate BP 202 and POW files across all HGAB project rows. The wider all-document scan below also includes Development Council, geotagged-photo, Certificate of Implementability and other files.
Loading Senate document title-scan summary…
How this subset is counted
Files link through an exact or accepted relaxed title match, or through a uniquely resolved same-code sibling file. Rows are deduplicated by House project ID across BP 202 and POW. This subset does not include the other Senate document categories, and file contents are not verified.
Senate HGAB files · selected NEP–HGAB matches
These Senate-provided POW files have exact-title matches to selected House ledger projects. File codes are shown; source paths and links are withheld.
How selected-pair Senate files are counted
These rows use the selected one-to-one NEP–HGAB project crosswalk and exact Senate HGAB title matches. They list matched file codes, not source links; a selected pair is not itself proof that a file exists.
View DPWH Transparency portal inventory, NEP comparison and document-link statistics →
HGAB document links · selected NEP–HGAB matches
These counts use Senate-provided HGAB file codes matched to selected House ledger projects by exact title, then count files with the same HGAB code in the local inventory. This is file-presence evidence only; document contents are not verified. Source paths and direct links are withheld.
How file-code inventory counts are computed
Each selected HGAB row is linked to exact-title matched Senate HGAB codes; local files sharing those codes are counted by filename type. Counts indicate files present and do not verify contents.
Project document lookup
Search Senate-provided HGAB file codes or project titles, or Proposal codes. Where both records match, they appear together as a Proposal-HGAB code pair. HGAB source links are withheld.
Search by HGAB file code or project title, or choose a project from the suggestions.