All articlesPublic-private partnerships
How to Get Cost Certainty for Municipal Building Construction
How to get cost certainty for municipal building construction is not a matter of finding one early number and treating it as final. Public owners improve confidence by defining the facility need, making estimate assumpti...

Managing Director

How to get cost certainty for municipal building construction is not a matter of finding one early number and treating it as final. Public owners improve confidence by defining the facility need, making estimate assumptions visible, testing uncertainty, and updating the estimate as design and procurement decisions become clearer. A disciplined process cannot remove every change or guarantee a final price, but it can help officials understand what the current estimate covers, what could move it, and which decisions are needed next.
Request a project-specific feasibility conversation
What does cost certainty mean for a public building?
Cost certainty means having an estimate appropriate to the current level of project definition, with scope, assumptions, exclusions, risks, and next steps clearly recorded. It does not mean that a concept-stage budget is a guaranteed construction price. A municipality may still need to resolve site conditions, complete design, obtain approvals, procure the work, and establish a contract before it knows the amount it is obligated to pay.
Officials should distinguish at least three figures. A planning estimate supports an early decision about whether to advance a need, based on a preliminary description of the facility and site. A current project estimate is a more developed forecast reflecting documented design, market information, schedule assumptions, and identified risks. A contract amount is established through a particular procurement and agreement, subject to its stated scope, allowances, contingencies, and change provisions.
These figures answer different questions. An early estimate helps a council decide whether to fund planning. A developed estimate may support an appropriation or procurement choice. A contract sets obligations as defined in the agreement; it does not automatically include every future operating, maintenance, financing, or lifecycle cost. A project report should label each figure so that a preliminary planning number is not mistaken for an approved commitment.
Cost confidence should therefore be communicated with context. Alongside a total, show the estimate date, stage of design, included scope, exclusions, escalation assumptions, contingency treatment, and unresolved decisions. When officials can trace a number to the information behind it, they can ask focused questions instead of debating a total that hides its own limits.
Why do municipal building estimates change?
Estimate movement is not always evidence of poor estimating. The project may be better understood later than it was at concept stage. Site investigations can reveal conditions that were unknown; user groups can refine operational needs; code or permitting reviews can identify additional requirements; and market pricing can differ from assumptions made earlier. The proper test is not whether a forecast ever changes, but whether changes are explained, managed, and reflected in decisions.
Common sources of uncertainty include:
- Incomplete scope: room counts, adjacencies, security, equipment, technology, and support spaces may not yet be settled.
- Site conditions: utilities, access, drainage, environmental constraints, demolition, and property needs require investigation.
- Design development: systems, materials, structural choices, and performance requirements become more specific over time.
- Schedule: approval timing, procurement duration, phasing, and construction-season assumptions affect the forecast.
- Market conditions: bids and supplier pricing can differ from earlier assumptions.
- Risk allocation: the agreement determines which party carries particular cost and schedule exposures, and under what conditions.
- Owner decisions: changes to scope, quality, or delivery requirements can change cost after an earlier baseline is established.
A useful estimate identifies uncertainty rather than hiding it in an unexplained allowance. Contingency is not an unrestricted pool with no purpose. It should relate to identified risks, project maturity, and the owner's view of what uncertainty remains. As risks are investigated or resolved, the team should explain whether contingency is adjusted and why. Keep the explanation consistent from one estimate update to the next.
It also helps to separate a change in the project from a change in the forecast. If a department adds a secure interview room, that may be a scope decision. If a site investigation identifies a utility relocation, that is new information about the selected site. If the pricing date moves, that is a market or schedule assumption. Categorizing the cause makes it possible to decide whether to revise scope, find a mitigation, or accept a changed forecast.
How should a municipality define the project before estimating?
Begin with the public service the facility must support, not an assumed building size or a preferred delivery label. Establish who will use the facility, what work happens there, what capacity is required, what must remain operational during construction, and what constraints shape the site. A clear project brief gives estimators and decision-makers a consistent basis for comparing options.
1. Describe the service need and users
Document the functions the building must support, the users and visitors it serves, operating patterns, security needs, accessibility, and relationships between departments or spaces. For a public-safety facility, for example, the team may need to describe operational adjacencies and continuity requirements. For a civic administration or community building, it should describe public access, service functions, and shared spaces. These are prompts for facility-specific programming, not assumptions about a particular project.
Separate required scope from preferences that can be evaluated later. Ask each department to identify what is essential on opening day and what could be deferred, reduced, or delivered in a later phase without undermining the public purpose. Record who has authority to approve these choices. If two user groups need the same space at different times, describe the operating assumption rather than simply adding duplicate rooms to the program.
2. Establish capacity and performance criteria
Set planning assumptions for capacity, flexibility, resilience, energy and operating objectives, technology, and maintainability. A criterion should be concrete enough to guide design and estimating. If a requirement is unsettled, mark it as an open decision, assign an owner, and describe its possible cost implication rather than silently choosing an assumption. For example, “allow future expansion” needs a practical definition: reserve a site area, design an extension interface, or provide adaptable interior space. Those are different requirements and may lead to different estimates.
3. Confirm the site and existing conditions
Identify candidate sites and the information available for each. Track property control, access, utilities, geotechnical and environmental investigations, drainage, traffic, demolition, and connections to surrounding infrastructure. Do not treat an unverified site condition as resolved merely because an early estimate includes a placeholder. State what investigation is needed, its timing, who will arrange it, and how the estimate will be updated when findings arrive.
When more than one site remains under consideration, use a common checklist and identify what is known, unknown, or different for each. A site with an attractive purchase price may require substantial access or utility work; another may have a higher initial acquisition requirement but fewer unresolved connections. Avoid declaring a preferred site on an incomplete cost comparison. Document nonfinancial considerations too, such as service access, adjacency, public access, and the consequences of construction on current operations.
4. Define boundaries and exclusions
State whether the estimate includes site work, furniture, fixtures, equipment, technology, professional services, permitting, testing, commissioning, temporary facilities, relocation, escalation, financing, and owner costs. The exact categories depend on the project and delivery arrangement. The point is to make boundaries visible. Two proposals cannot be compared reliably if one includes an item that the other excludes or puts under a different party's responsibility.
Use a written basis-of-estimate document. It can be concise, but should record the design information used, pricing date, assumptions, exclusions, allowances, contingency, escalation basis, and responsible preparer or reviewer. Keep revisions so officials can see what changed between estimate versions. If an item cannot yet be priced responsibly, state the information needed to price it and the decision date that depends on it.
How can the estimate mature with the design?
Estimate updates should follow decision gates. At each gate, agree on the information available, the decisions required, and the level of detail appropriate for the next choice. Avoid presenting more precision than the underlying scope can support. An estimate that reports many decimal places may still rest on unresolved assumptions; clarity about maturity matters more than a false appearance of precision.
- Needs and feasibility: define the service need, compare high-level alternatives, identify site and approval questions, and produce a planning range with major assumptions.
- Program and concept: establish space and performance requirements, test site fit, identify major systems, and update the estimate against the selected concept.
- Design development: refine building systems and materials, close open scope questions, incorporate investigation results, and review risk and escalation assumptions.
- Procurement readiness: confirm documents and responsibilities, review the current market basis, reconcile allowances and exclusions, and decide how bids or proposals will be evaluated.
- After selection and during delivery: track commitments, approved changes, remaining risks, contingency use, and forecast-to-complete against the authorized baseline.
At every stage, show the difference between the current estimate and the prior approved baseline. Explain whether movement comes from changed scope, new information, market updates, schedule, or a correction. A short reconciliation is often more useful than a revised total on its own. If categories have moved or been renamed, map them back to the earlier version so decision-makers do not mistake a reporting change for a real cost change.
Use decision gates to control when an assumption becomes a commitment. Before advancing from concept into detailed design, for example, the owner may want approved room requirements, an agreed site, and a clear list of outstanding investigations. Before issuing procurement documents, the owner may need a current scope, a documented risk position, and a decision on the form of price or proposal sought. The required evidence depends on local rules and the project, but it should be defined before the gate arrives.
Which cost categories belong in a useful comparison?
Construction cost is important, but it is not the whole public decision. Officials should compare options on a consistent basis and identify the costs that fall inside and outside each figure. A delivery proposal may package some responsibilities differently from another, so comparable scope matters more than identical labels. The municipality should make its chosen comparison period and treatment of financing, operations, and retained owner costs clear.
Building and site scope
Questions for the public owner: Are the same functions, site work, systems, and performance requirements included?
How to document it: Use a common scope statement and list exclusions.
Owner-side costs
Questions for the public owner: What services, approvals, relocation, equipment, or internal resources remain with the municipality?
How to document it: Identify the responsible party and estimate basis for each item.
Schedule and escalation
Questions for the public owner: What dates and procurement assumptions underlie the forecast?
How to document it: Show the pricing date, schedule basis, and escalation treatment.
Contingency and risk
Questions for the public owner: Which uncertainties are covered, by whom, and under what conditions?
How to document it: Maintain a risk register and explain allowances and contingency.
Financing and payments
Questions for the public owner: How do financing costs and payment timing affect total contractual obligations?
How to document it: Review project-specific terms and compare over a consistent period.
Operations and maintenance
Questions for the public owner: Which operating tasks, maintenance obligations, and lifecycle replacements are included or retained?
How to document it: Set out responsibility, service standards, duration, and exclusions.
End of term
Questions for the public owner: What happens when the agreement ends, and what condition or title obligations apply?
How to document it: Review the actual contract's expiry, transfer, or continuation provisions.
For options with long-term payments, compare the payment schedule and total obligations over the relevant term, not just the initial capital requirement. Potentially limited upfront capital is not the same as avoiding payment. Lease payments may cover development, construction, financing, and applicable fees, and cumulative payments can exceed traditional financing. The agreement's actual economics and responsibilities should be reviewed by the municipality's finance and legal professionals.
Be precise about what “project cost” means in each presentation. One figure might describe the construction contract; another might include design and owner costs; a third might include long-term payment obligations. None is inherently misleading if it is labeled and supported. The comparison becomes confusing when figures with different boundaries are placed side by side without explanation.
How can officials test a cost estimate before relying on it?
A review should test the logic behind the estimate, not just whether a total appears plausible. Start with the basis-of-estimate document and ask whether the scope matches the current program, whether the design documents are identified by date and version, and whether assumptions are consistent with the schedule. Confirm that each material allowance has an owner and a reason. If a major cost is carried as a placeholder, request the next action needed to replace it with better information.
Then perform a line-by-line completeness check at the level the project has reached. Does the estimate account for the building, site, utilities, access, temporary work, equipment, technology, testing, and commissioning as applicable? Are professional services, approvals, relocation, and owner-side resources presented separately where they are not in the construction scope? A checklist should not imply that every project needs every item. It should make omissions intentional rather than accidental.
Ask for a reconciliation to the preceding version. A practical change log might state: “The program added a required support room; the site investigation changed the utility assumption; the schedule now uses a later procurement date; and the current estimate separates owner equipment from construction.” Each statement should be linked to a decision, document, or evidence source where possible. This gives the council and project team a way to discuss causes rather than speculate about them.
Where appropriate, invite a qualified independent reviewer to examine the estimate or key assumptions. The reviewer needs the same scope basis, project documents, pricing date, and exclusions as the preparing team. An unaligned second estimate can create another competing total without resolving uncertainty. The purpose of a review is to identify gaps, test reasonableness, and explain differences, not to manufacture agreement between two numbers.
Federal cost-estimating resources are available through the U.S. Government Accountability Office at GAO.gov. Public owners can use government guidance as a reference point, then adapt the review to the project's scale, procurement, jurisdiction, and professional advice. A federal resource does not replace applicable local requirements or project-specific review.
How should a municipality respond when the estimate exceeds its planning limit?
A gap between an estimate and an available planning limit is a decision point, not a reason to quietly remove contingency or omit owner costs. First confirm that the two figures use the same scope boundary, pricing date, schedule, and treatment of owner costs. A mismatch in definitions can make a gap appear larger or smaller than it is. If the comparison is sound, identify what is driving it before selecting a response.
Sort possible responses into distinct choices. The municipality may revisit requirements that are preferences rather than essential service functions; examine phasing; test a different site or building concept; investigate whether existing assets can meet part of the need; adjust the schedule; or reconsider the funding and delivery path. Each option should be tested for its effect on service, approvals, operating needs, and future costs. A reduction in initial scope can create a later project need, so record what has been deferred and how it would be addressed.
Use a transparent decision record. For each alternative, state the change, its expected effect on scope, the information still needed, and the official or governing body authorized to decide. Avoid presenting a design reduction as a confirmed saving until its cost effect has been evaluated. Likewise, do not treat a different financing structure as a reduction in total project obligations merely because the payment timing changes.
If the gap remains after scope and assumptions are tested, the responsible choice may be to pause, gather more information, revise the project, or seek further approvals. The estimate should inform that choice without predetermining it. A clear explanation protects public trust better than a budget number that appears to fit only because important costs and risks have been left outside it.
How can officials make risk visible?
A risk register turns uncertainty into items the team can investigate and manage. It should name each material risk, its potential cost or schedule effect, its status as understood at that time, the mitigation action, the responsible party, and the evidence or decision that would close it. Avoid assigning a level of precision that the available information cannot support. The register should be updated as the project learns more, not filed away after an initial workshop.
For a building project, the register may cover site information, utility capacity, permitting, scope approval, procurement, price validity, schedule dependencies, construction interfaces, and owner decisions. The team should distinguish a risk that is merely identified from one that is contractually allocated. Naming a risk in a presentation does not establish who bears its cost under an agreement. Review the contract language and the practical steps that would apply if the event occurred.
Ask the team to state what remains with the municipality even if another party takes on part of delivery. The public owner may retain approvals, policy choices, property responsibilities, user coordination, or other obligations depending on project terms. For each proposed allocation, request the relevant contract provision or a clear description of how the responsibility works in practice. Do not assume that every design, construction, financing, maintenance, or operating risk moves together.
Contingency management also needs governance. Set out who may authorize its use, what documentation is required, how unused amounts are handled, and how the forecast is reported. Track commitments and pending changes separately from unassigned contingency. These details help maintain trust when a project changes and prevent a contingency number from becoming a substitute for a decision.
How should delivery options be compared?
Compare delivery approaches against the same public need, scope, schedule assumptions, and evaluation criteria. The label alone does not establish cost, risk transfer, approval requirements, or schedule performance. Traditional public procurement, progressive design-build, design-build, construction manager as general contractor (CMGC), and a public-private partnership may organize work and responsibilities differently. The appropriate path depends on jurisdiction, project conditions, procurement rules, financing, and the public owner's objectives.
A public-private partnership is not automatically faster or cheaper than bonds, and it does not bypass competitive procurement or required voter or legal approvals. Accounting and debt treatment depend on local standards and project structure. Seek jurisdiction-specific advice from counsel and finance professionals before relying on a proposed treatment or approval path.
When assessing an approach, ask:
- What is the complete scope and what is excluded?
- When will the public owner have a price, and what conditions can change it?
- How are design changes, unforeseen conditions, and schedule impacts handled?
- What procurement, public approvals, and competitive processes apply?
- Which party is responsible for design, construction, financing, operations, and maintenance?
- How are long-term payments, lifecycle obligations, and end-of-term choices described?
- What financial, legal, technical, and independent review does the municipality need?
Civic Six Partners describes a model in which it finances and develops public facilities and leases completed assets back to public entities under long-term agreements. A build-lease-transfer arrangement is one possible educational model, not a description of every project. Responsibilities and terms must be established for the particular agreement. Municipal teams can review the firm's public facility services and its guide to evaluating design-build-finance as background, then assess any proposal on its documented scope and terms.
What does a practical estimate workflow look like?
Cost management is a repeatable workflow, not a single consultant deliverable. The municipality should decide who owns the estimate, who supplies inputs, who reviews assumptions, and who approves a baseline. This matters when several departments, designers, contractors, or financing partners contribute information. Without a clear process, teams may use different versions of the scope or treat preliminary numbers as if they had the same status as approved commitments.
Begin by naming an owner-side lead who maintains the project record and coordinates updates. That person does not need to prepare every estimate. The role is to ensure that inputs are timely, assumptions are documented, questions have owners, and decision-makers receive a consistent account. Establish a version date and identify the estimate stage on every report. If a figure is copied into a council presentation, preserve its stage and caveats rather than carrying forward only the total.
Next, create a common cost breakdown that can be carried from planning through procurement and delivery. Categories should fit the facility and chosen process, but the structure should make it possible to reconcile estimates over time. If category definitions change, explain the mapping. Otherwise, a shift between categories may look like a cost increase or decrease when it is only a reporting change. Use the same naming conventions in staff reports, project schedules, and estimate updates where possible.
Use a decision log alongside the cost record. For each open decision, capture the question, available options, responsible decision-maker, deadline, and known estimate effect. Examples include whether to retain an existing structure, how much flexibility to provide for future use, or which equipment belongs in the initial project. Evaluate these choices against service needs and lifecycle implications, not as isolated line items. Record a decision even when the answer is to defer it, including the date by which it must be revisited.
Finally, set triggers for an estimate refresh. A completed site investigation, major program change, material schedule shift, receipt of market feedback, or change in procurement strategy may justify a new estimate. Agree on triggers in advance so that a revised forecast is not viewed as an unexplained surprise. Keep the prior baseline for accountability while clearly distinguishing it from the current forecast.
What should a cost review meeting produce?
A meeting that only presents a total leaves important questions unanswered. Require a short decision record that connects the estimate to the project's current stage and identifies the work needed to improve it. A useful record lets someone who did not attend understand what has been approved, what remains uncertain, and what the next decision requires.
- The current estimate and its date, basis, and level of design.
- A reconciliation against the prior estimate or authorized budget.
- Scope changes and assumptions that account for movement.
- Major exclusions, allowances, contingency, and unresolved risks.
- Schedule assumptions and any pricing validity period.
- Actions, owners, and due dates for investigations or decisions.
- The next approval gate and the information needed to reach it.
Set a reporting cadence appropriate to the project stage. Early updates may follow programming and design decisions. Near procurement and during construction, reporting may need to be more frequent because decisions and commitments can move quickly. The municipality should define who receives reports, who may approve changes, and how the public record will reflect important decisions.
Where an estimate is prepared by a delivery partner, the owner should understand the method and assumptions well enough to challenge or test them. Depending on the procurement and project, independent estimating or peer review may help identify gaps. Reviewers need the same scope basis and should disclose exclusions; a second number without a common basis can create confusion instead of confidence.
What questions should a municipality ask before advancing?
Use these questions to identify unresolved work, not as a checklist that guarantees a particular outcome:
- What public service need does this facility address, and who has approved the requirements?
- Which scope items are fixed, and which remain options or assumptions?
- What site investigations are complete, and what material questions remain?
- What exactly is included in the current estimate, and what is excluded?
- What changed since the last estimate, and what evidence supports the change?
- How are contingency and escalation calculated and governed?
- What costs and responsibilities remain with the municipality?
- How do financing, payment timing, operations, maintenance, and end-of-term provisions affect the comparison?
- What procurement, public approval, legal, and accounting review is required in this jurisdiction?
- What information would justify moving to the next planning or procurement stage?
For practical context on how public facilities and project roles may be approached, review the public-private partnership FAQs. Treat general educational information as a starting point, not a substitute for a project's solicitation, agreement, or professional advice.
Frequently asked questions
Can a municipality guarantee the final construction cost early?
An early estimate is based on incomplete scope and information, so it should not be represented as a guaranteed final amount. A later contract may establish defined pricing obligations, but the agreement's scope, allowances, exclusions, change terms, and conditions matter. Public officials should describe the certainty available at each stage accurately.
Does a contingency make an estimate more certain?
Contingency can provide for identified uncertainty, but it does not make unknown scope disappear or guarantee that every cost is covered. The estimate should explain what risks it addresses, who controls its use, and how it changes as information improves.
Does a P3 remove cost or approval risk from the municipality?
No. A public-private partnership may allocate certain responsibilities differently, but allocation is specific to the project and agreement. Procurement, voter, legal, accounting, and other approvals may still apply. The municipality should review obligations with its own legal and finance professionals.
Should the lowest initial amount decide the delivery method?
Not by itself. Compare scope, owner-retained costs, financing and payment timing, lifecycle responsibilities, risk terms, and end-of-term provisions on a consistent basis. A lower initial capital requirement can coexist with contractual payments over time and different total obligations.
When should officials seek outside feasibility input?
Consider project-specific input when the municipality has a defined need but material questions remain about site, scope, delivery structure, financing, responsibilities, or approvals. A useful conversation should clarify open issues and next steps without promising a price, schedule, or approval outcome before review.
Make the next estimate more useful
Cost confidence grows when a public owner can trace an estimate to defined scope, evidence, assumptions, and accountable decisions. Start with the facility need, investigate site and program questions, use comparable cost boundaries, maintain a risk register, and explain changes at each approval gate. Then compare delivery options across both upfront requirements and long-term obligations. The result is not a promise that uncertainty has vanished; it is a clearer basis for deciding what the municipality should do next.
Request a project-specific feasibility conversation
To discuss a public facility's planning questions, use the Civic Six Partners contact form or call 888-222-1882 to start a project-specific feasibility conversation.
