What the report changes at a glance
Across the four detailed schedules, project rows labeled Removed sum to ₱113,339,418,750 in gross House allocations. DPWH accounts for 3,479 removed rows and ₱99,281,538,750 of that amount. This “Savings” figure is the value of lines removed from the House schedule; it is not a net budget reduction or realized savings, since other lines may be added, restored, renamed or increased.
Separately, DPWH’s General Summary allocation moves from ₱654,102,015,000 in the House bill to ₱587,902,738,000 in the Senate report: net ₱-66,199,277,000. The dataset has 20,835 project rows, 2,719 Annex A rows, 186 Annex B provision amendments, and 37/38 listed checks passing. Source definitions, caveats and documents are recorded in the supplied dataset README.
How SCR changes should affect existing flags
Green · resolved or corrected
Keep the original HGAB flag and add an SCR note when the cited Senate change directly resolves it: for example, the line is cut, a title/location is corrected, or the amount/scope concern is explicitly corrected. The note should cite the SCR page and say what changed.
Red · new or worse
Add a red flag when SCR adds a project that triggers an existing flag rule, or when a Senate revision introduces or strengthens a concern (such as a larger amount, broader scope or a new location/attribution issue). Cite the report page and state the rule triggered.
Review · stage change alone
A cut, rename, addition or increase is not automatically a finding. Match the row to the original flag and its rule first. Preserve historical HGAB evidence, then annotate the later status so the reader can see how the finding changed over time.
This page marks stage disposition from the published dataset. It does not automatically claim that any specific existing flag is invalid or newly substantiated; that requires a defensible row-to-flag match.
Which analyses can benefit from SCR
Prioritized by schedule coverage and whether a later-stage row can change the evidence behind a flag.
| Page | Priority | Potential SCR comparison |
|---|---|---|
| documents.html Proposal + HGAB document inventory | High | The document-type totals are aggregate rows and should not get a project disposition. Add SCR columns only to project-level tables that expose a reliable project title; do not infer that a missing file is resolved by an SCR cut. |
| dpwh.html DPWH HGAB projects and documents | Highest priority | The all-project coverage table and POW line items expose DPWH project titles. Add the SCR column on uniquely matched project rows; keep document-presence findings separate from SCR budget disposition. |
| nia.html NIA irrigation and named projects | High | Add SCR disposition where a project title joins uniquely. Location and workbook review tables remain NIA-specific evidence and should keep their existing flags. |
| fmr.html FMR coordinate and manual review | High | The project tables can join to the FMR schedule. The manual red-flag list has a defensible SCR overlap for a removed-row summary; coordinate concerns remain evidence about the House version. |
| dpwh-transparency.html DPWH Transparency inventory | Conditional | The inventory is not a direct budget-stage table. Add row-level SCR only where the inventory project title and allocation identify one DPWH report row. |
| congress.html Project flags and district allocations | High | Aggregate district totals cannot take a project SCR column. Project-detail rows can be annotated when title joins uniquely; do not imply that district attribution establishes sponsorship. |
| flags.html Flag index | Highest priority | Join the row-level flagged project list to SCR by title and amount. The hero can count matched flagged lines removed, while each flag and its historical HGAB basis stays visible. |
| undocumented-hgab.html Undocumented HGAB | High | Project rows can show whether the House line remains in SCR. A cut changes the later-stage allocation status; it does not retroactively supply missing House documents. |
| repeats.html Project repeats | Medium | Annotate each matched project occurrence in a pair row. A removal changes stage survival but does not establish that the pair was a duplicate. |
| out-of-place.html Out of Place | High | The selected-project card can show its SCR disposition. The hero can summarize removed coordinate-review rows and their gross House value; this does not erase the original location signal. |
| cost-per-km.html Cost per meter | High | The 191 high-rate scope-review candidates can be joined to DPWH SCR rows. The hero can sum gross House allocations for candidates labeled Removed; this is not net or realized savings. |
| pccp-cost-per-unit.html Cost per Unit · DPWH Atlas | Conditional | Add a project SCR column to identifiable project rows; keep material/benchmark comparisons separate from Senate allocation changes. |
| cost-per-unit.html Cost per Unit · peer comparison | Conditional | Project-and-office rows can show SCR disposition when the budget row is identifiable. Unit-cost comparisons need scope and quantity checks before a cut is called savings. |
| cmpd-cost-per-unit.html CMPD · cost per unit | Conditional | POW project rows can receive an SCR link only where the project name uniquely matches. Office material-price references are not Senate project rows. |
| expectation-vs-reality.html Costing vs proposed allocation | High | Project rows can show SCR title and allocation changes where they join uniquely. Keep estimate-to-allocation differences distinct from SCR removals. |
| rcs.html RCS project scope | Conditional | Add SCR disposition to identifiable DPWH project rows; RCS scope status alone does not show that a budget change resolves the scope review. |
| mpb.html MPB flags | High | Project-level location and source rows can show SCR status where matched. A Senate cut changes the later-stage budget line, not the observed geographic evidence. |
| barangay.html Barangay allocations | Conditional | A barangay aggregate is not a project-level SCR row. Add the column only in project-detail rows with a reliable title match. |
Project row comparison
Search Senate, House or NEP title and row identifiers. By default, unchanged and NEP-only rows are hidden so review focuses on SCR-stage changes. Every displayed row retains source page links for all available stages. Savings counts a row’s House allocation only when the SCR labels it Removed; it is not the net budget change.
| Schedule / status | Senate report title | House bill title | Office / region | NEP | House | Senate | Savings · Removed | SCR evidence | Stage sources |
|---|
Rows shown . Amounts are pesos. A blank amount means the source dataset does not supply one for that stage.
Sources and method
The data comes from the supplied senate-2027-dataset package. It covers Senate project schedules for DPWH, DA farm-to-market roads, DOH HFEP and NIA; it is not a complete row-level transcription of every department. Department-wide amounts come from the report’s General Summary. Status and matching conventions are defined in the linked README.
Source validation recorded by the build: 37 of 38 checks pass; the README records page-level misses and describes the remaining review needed. The report pages are evidence references, not proof of implementation or spending.
