What I want to know before public money is committed

Before I support a project paid for with public money, I want to understand the deal. What problem are we trying to solve? What are taxpayers putting in, and what should we get back? A new building or a promising jobs announcement can be good news. I still want to see the cost, the timeline and who has to answer when either changes.

A capital project does not begin and end with a press conference. Someone has to define the work, identify a funding source, obtain authority to spend, select a delivery team and manage the work after a contract is signed. Each of those decisions can affect the public long before a ribbon is cut.

My March 2025 strategy proposed stronger oversight and public progress updates for infrastructure and capital projects. I was interested in a practical question: can residents follow the same basic project from its first public commitment through the changes, the finished work and the results it was intended to produce?

A useful starting record should explain the problem, the proposed scope, the location, the funding and the organization responsible for delivery. It should say which public body made the decision and link to the records that establish it. If the price or schedule is still an estimate, say so. If only one phase has been authorized, don't present the entire project as funded.

I also want to know what is outside the stated price. A construction budget may not include every cost of land, financing, utilities, equipment, maintenance or future operation. Those costs need their own explanation, not an assumption that they are either included or missing.

Residents should be able to compare an announced benefit with a specific commitment. A proposed community facility, for example, should have a clear description of the services it is expected to provide and who is responsible for operating it. The promise of a service is not proof that it has begun.

Budgets and schedules change for legitimate reasons. A site condition may be different from what was expected, a design may change or prices may rise. The public should be able to see the earlier baseline beside the new figure, the date of the change, the reason given and the official action or contract document that supports it.

Here is a simple illustration, not a description of a real project: suppose a City estimates a facility at $10 million with an opening planned for June. Later, it approves a $1 million change and moves the opening to October. A useful update would show the original estimate and date, the revised figures, what the change pays for, who approved it and whether the amount is a budget, contract change or payment. A single $11 million label cannot answer all of those questions.

The same care applies to progress percentages. Fifty percent complete may describe a contractor's estimate, a phase of construction or money used from one budget. Without a definition and a date, a number that looks precise can be difficult to interpret. A changed scope can also make a comparison with an earlier percentage misleading.

An adopted budget is permission to use resources for stated purposes; it is not proof that cash has been paid. A contract or purchase order creates a different kind of commitment. An expenditure in an accounting report is not necessarily a vendor payment, and a payment alone does not tell residents whether the work was completed.

I want public updates to keep authorization, budget, contract, payment and delivery distinct. When the records do not yet answer a question, the page should say what is missing rather than fill the gap with a plausible number. That is especially important when a financing package supports several projects: the total cannot automatically be assigned to one building or one neighborhood.

A completed building, road or park can be an important milestone. It still leaves questions: is it open, can people use it as intended, what does it cost to operate and has the original problem changed? Those answers may come from different sources and at different times. A completed project should not automatically be described as a proven outcome.

My interest in public reporting comes from that chain of responsibility. I want a resident who is following a project to find a clear starting point, understand material changes and see the original records without having to reconstruct the whole story from scattered documents.

In the March 2025 strategy, I proposed “public updates on project status” alongside performance dashboards. This page expands on that historical direction; it does not claim that the City adopted the proposal, built a particular dashboard or delivered a specific result because of it. Any current project would need its own records and responsible officials.