Section 1 of Monroe Ordinance 12,293 adopts the May 1, 2026–April 30, 2031 capital program, but the same webpage’s heading names 2025–2030. Its appropriation section also mixes a first-year budget description with the five-year date range. Those are specific record conflicts to resolve before treating a budget figure as spending authority. Adoption alone does not show that a project was bid, built or paid for. Adopted ordinance.

The legislative chronology

The ordinance’s own chronology identifies five calendar dates:

  • January 30, 2026: the Mayor submitted the proposed program.
  • March 10: the first listed public hearing.
  • March 24: ordinance introduction.
  • March 27: publication of the ordinance notice.
  • April 14: the second listed hearing and adoption; the recorded vote lists three ayes, no nays and two absent members.

These are the legislative milestones the ordinance reports, not construction dates.

Five records connect a program to finished work

StageRecord neededWhat it establishes
Proposed programSubmitted schedule and project listWhat was proposed at that date
Hearings and adoptionNotices, minutes, ordinanceWhat legislative action occurred
AppropriationAdopted first-year budget and amendmentsSpending authority for stated purposes
Project implementationDesign, bid, award, contract, change, payment recordsWhat happened on an individual project
CloseoutAcceptance, final amount, as-built and outcome recordsWhat was completed and at what documented result

The City Council route is useful for legislative records; Project Management is a starting point for implementation records. A project can move through these stages on a schedule different from another item in the same program.

Three record mismatches to resolve

Record locationWording in the sourceWhy it needs reconciliation
Ordinance heading versus section 1Heading: May 1, 2025–April 30, 2030; adoption section: May 1, 2026–April 30, 2031The heading is not a reliable substitute for the operative section and signed record
Ordinance section 2Calls the first-year amount the capital budget but prints the full 2026–2031 rangeDo not silently rewrite that as a verified one-year appropriation period
Earlier linked hearing pageURL/title contains “2026,” but the body gives a March 11, 2025 hearing for FY 2025–2026Its proposed-program table is not established as the attachment adopted in April 2026

Sources: Ordinance 12,293 and the earlier hearing page. We retain the latter as a documented mismatch, not as evidence that the April 2026 hearing occurred.

The ordinance incorporates a program attachment, but the rendered ordinance page did not provide it when checked September 19. We also inspected the Council and budget-hearing routes; a separately listed March 2026 operating-budget notice is not the missing adopted capital schedule. That does not prove the attachment is unavailable elsewhere.

Before quoting an adopted program total or first-year appropriation, request the signed ordinance, its complete adopted attachment, the first-year schedule and any amendments. Identify the project line and funding source rather than summing selected figures from another year’s hearing page. No program total is calculated here.

Questions for one listed project

Ask for the exact program line, current appropriation, funding source, design status, procurement record, contract amount, approved changes, payments, schedule, and closeout. Identify the date of each answer. “In the capital plan” should never be rewritten as “under construction.”

Source and methodology

Local Service Ledger read the complete ordinance and earlier hearing-page text, current Council and Project Management pages, and the budget-hearing index on September 19, 2026. We preserved the useful program-to-project comparison and replaced a vague inconsistency warning with three exact document mismatches and the five-date chronology. The signed ordinance and complete adopted attachment remain necessary for a budget-total or appropriation analysis. We did not audit City finances, obtain records through a private request or verify construction status.