All articlesPublic-private partnerships

Municipal Building Procurement Risk Allocation: A Public Owner Brief

Learn how municipal teams can map procurement risks across planning, design, construction, financing, and operations to compare delivery options clearly.

Portrait of Marc Lofman

Marc Lofman

Managing Director

Municipal officials reviewing building project plans and a responsibility matrix

Municipal building procurement risk allocation is not simply a decision about which party carries a risk. A public owner first needs to identify what could affect scope, approvals, cost, schedule, financing, operations, and long-term value. Then the team can decide who can manage each exposure, what responsibilities remain public, and how the agreement will respond if assumptions change. The appropriate answer depends on the facility, jurisdiction, delivery method, and contract terms.

Request a consultation

What does risk allocation mean in a municipal project?

Risk allocation is the process of identifying project risks and deciding how, and to what extent, they should be shared. In procurement, this shapes who must act when assumptions change, approvals take longer than expected, design requirements evolve, or an asset needs attention after opening. A contract may assign a duty to one party, share it, or establish a process for handling uncertainty.

Allocation does not eliminate risk. Assigning a duty to a private partner does not guarantee that a problem will not occur, nor does it make the public owner immune from consequences. The public team still needs to assess affordability, continuity of public service, legal authority, oversight, and the terms that apply if performance falls short. Academic discussion describes risk allocation as identifying risks and determining how and to what extent they should be shared; that is a useful starting point, not a substitute for project-specific review. See Purdue's discussion of risk allocation.

Which risks should a public owner identify first?

Begin with the facility's purpose and the decisions that could materially change delivery or use. A fire station, courthouse, community center, and public-works building have different operating needs. Civic Six Partners lists public-safety, civic, and specialized facilities among its public facility services. The municipality should still define its specific requirements rather than assume one template fits every building.

  • Scope and requirements: Are room functions, capacity, equipment, security, accessibility, and future flexibility defined? Who approves changes, and how are cost and schedule effects reviewed?
  • Site and existing conditions: Who investigates utilities, access, environmental conditions, title, and other constraints? What happens if actual conditions differ from available records?
  • Approvals and procurement: Which public approvals, permits, procurement steps, or voter decisions may be required? Who prepares submissions, and who retains authority to approve them?
  • Design and construction: Who coordinates design, reviews quality, manages interfaces, and responds to defects or delay? What standards and acceptance tests apply?
  • Financing and payment: What payment obligations arise, when do they begin, and what conditions affect them? How are assumptions and fees disclosed?
  • Operations and maintenance: Who maintains each system, responds to failures, and funds lifecycle renewal? What service levels and reporting are required?
  • End of term: What happens at lease expiry? Does the agreement contemplate expiry, transfer, or negotiated continuation, and what condition must the facility meet?

A practical first exercise is a cross-functional workshop. Facilities staff can describe operational needs; procurement staff can identify the solicitation path; finance staff can map payment constraints; counsel can flag authority and approval questions. Record differing assumptions rather than resolving them by default. A disagreement about who supplies utility records, for example, is itself a risk to assign and manage.

How can a team connect each risk to a capable party?

For every risk, ask which party can prevent it, reduce its likelihood, detect it early, or manage its consequences at a reasonable cost. The party best able to control an event may not be best able to absorb every financial consequence. Some risks are shared because both sides influence them; others remain with the public owner because they involve public authority or policy choices.

Make the discussion concrete. Instead of writing “the partner assumes construction risk,” identify the event, required response, evidence of completion, and remedy if obligations are not met. Likewise, “the city handles approvals” should specify which approvals, who prepares materials, what cooperation is needed, and what happens if a decision is delayed. A broad label can conceal a gap: the contractor may prepare an application, for example, while the public agency remains responsible for a decision only it can make.

Use a working register before drafting contract language. For each item, record a description, cause, potential impact, likelihood or uncertainty, existing controls, proposed responsible party, dependencies, evidence needed, and next review date. Assign an individual to update it. The register supports negotiation and review; it does not replace the executed agreement.

What should a responsibility matrix include?

A matrix makes gaps and overlaps easier to spot. Build it early and reconcile it with procurement documents and the final contract. The examples below are prompts, not a claim that any allocation is standard.

Risk areaQuestions for the public ownerPossible allocation approach
Requirements and scope changesWho defines needs, approves changes, and assesses impacts?Owner retains authority over public requirements; change effects and approval steps are explicit.
Site conditionsWhat information exists, and who can investigate?Assign investigation and response duties based on access, knowledge, and control; state how unknown conditions are handled.
Permits and public approvalsWhich decisions are governmental, and what cooperation is needed?Keep public decision authority with the agency; identify submission, coordination, and schedule assumptions.
Design and constructionWho coordinates delivery, and how is acceptance tested?Define requirements, review rights, quality evidence, correction duties, and remedies.
Financing and paymentWhat triggers payment, and how are long-term obligations assessed?Specify payment terms, conditions, fees, and review responsibilities; obtain jurisdiction-specific finance advice.
Operations and maintenanceWho maintains systems and funds renewals?Set duties, service measures, reporting, lifecycle assumptions, and handback condition in the agreement.

To use the matrix, add a column for the municipality's retained action and another for the contract mechanism. That distinction matters: a private party may be accountable for a deliverable, while the public owner must still provide timely access, decisions, records, or payments. Mark an item “unresolved” when the parties do not yet have enough information. Do not disguise unknowns as an agreed transfer.

How does delivery method affect allocation?

Traditional procurement, design-build, progressive design-build, construction manager as general contractor (CMGC), and public-private partnership (P3) approaches can organize duties differently. The label alone does not settle who bears a risk. Solicitation documents, contract terms, applicable law, and the municipality's retained responsibilities determine the actual arrangement.

For example, design-build may place design and construction coordination under one contract, but the owner still defines public needs, reviews compliance, manages approvals, and funds the project as agreed. A P3 may combine development and financing with delivery and a long-term lease, but the exact allocation of permitting, acquisition, design, construction, operations, and maintenance is agreement-specific. Build-lease-transfer is one possible educational model, not a universal structure.

Compare alternatives against the same scope and assumptions. Civic Six's P3 101 guide provides general background, while its design-build-finance evaluation guide can help frame a separate delivery-method review. Neither substitutes for a procurement plan or agreement review.

How should officials compare lifecycle cost and retained risk?

Look beyond the initial project estimate. A comparison should state what is included, when payments occur, which costs remain with the public owner, and what maintenance or renewal obligations continue after opening. Long-term lease payments may cover development, construction, financing, and applicable fees; cumulative payments can exceed traditional financing. Potentially limited upfront capital is not the same as avoiding payment.

Ask finance staff and counsel to review the full payment schedule, funding assumptions, treatment of contingencies, appropriation or approval requirements, and end-of-term options. Do not assume a project is off-balance-sheet, outside public debt rules, exempt from competitive procurement, or guaranteed to finish at a fixed cost or date. Those questions depend on jurisdiction and contract structure.

Compare retained responsibilities as well as dollars. If the municipality keeps responsibility for approvals, utility coordination, changes to public requirements, or some maintenance tasks, those duties carry staffing and budget implications. A contract that assigns a task elsewhere should state measurable obligations, monitoring rights, and what happens when performance does not meet the agreement.

Use a common comparison horizon and label each assumption. Separate the public owner's expected payments from costs it may still incur for staffing, insurance, utilities, retained maintenance, transaction advice, or changes in scope. These categories may not all apply to each procurement path, so identify them rather than inserting estimates without evidence. Show timing as well as totals: payment timing and the point at which maintenance begins can affect budget planning even when two options appear similar in aggregate.

How can a team test an allocation before it becomes contract language?

Walk through plausible scenarios with the people who would have to respond. The point is not to forecast every event but to test whether duties and remedies are understandable when conditions depart from the baseline.

  • Delayed approval: Identify who prepares the submission, who tracks status, what information the agency must provide, and how schedule effects are treated if a decision takes longer than assumed.
  • Unexpected site condition: Check what investigations are complete, who can access the site, how a condition is documented, who evaluates options, and which party authorizes a change.
  • Changed operational requirement: Determine who can request the change, who evaluates design and cost effects, and whether the public owner has final approval over the service requirement.
  • Defect found at acceptance: Specify the inspection record, correction process, retest, deadline, and consequences if the item remains unresolved.
  • System failure after opening: Define response times, escalation contacts, temporary service arrangements, reporting, and how responsibility is established.

For each scenario, ask the team to locate the contract provision that governs it. If staff cannot explain who acts first, what evidence is needed, or how disagreement is resolved, the draft may need clarification. This exercise also exposes dependencies: a partner's schedule obligation may rely on timely owner decisions, while an owner's approval may depend on complete technical materials.

What should be documented before choosing a path?

  1. Define the public need. Describe the service to be housed, required functions, capacity, site constraints, and future operating assumptions.
  2. Confirm authority and process. Identify procurement rules, decision-makers, approvals, public engagement needs, and any required legal or voter review.
  3. Build a risk register. Record each risk, its cause and potential effect, who can influence it, and what information remains missing.
  4. Set comparison assumptions. Use a common scope, schedule basis, financing assumptions, maintenance horizon, and end-of-term scenario across alternatives.
  5. Test the proposed allocation. Ask whether each assigned party has the authority, information, and capacity to manage the risk, and whether the proposed remedy is practical.
  6. Review affordability and agreement terms. Have procurement, legal, finance, facilities, and operations staff evaluate obligations together before the municipality commits.

Keep a decision record explaining why a risk is retained, shared, or assigned. Note unresolved issues, the person responsible for resolving each, and the information needed to close it. This record helps officials communicate the basis for the chosen approach and keeps later negotiations aligned with the public objective.

What should a municipality ask a potential project partner?

  • Which specific risks do you propose to manage, and which remain with the public owner?
  • What assumptions about site conditions, approvals, scope, and public decisions underpin your proposal?
  • How will design changes, unknown conditions, delays, defects, and payment disputes be handled?
  • What maintenance duties, performance measures, reporting, and lifecycle renewals are included?
  • What obligations continue if the agreement ends, and what condition or title arrangements apply?
  • Which terms are negotiable, and what information should the municipality provide for a useful feasibility review?

Request a role matrix and an explanation of relevant contract mechanisms, not just a broad statement that risk is transferred. The public-private partnership FAQs can help identify general questions, but the project agreement and professional advice control actual obligations.

What information makes a comparison useful?

A comparison improves when all options use a shared baseline. Prepare a concise project brief that states the facility purpose, the current condition or capacity problem, intended functions, site status, target decision dates, known approvals, and the level of design information available. Note what is confirmed and what remains an assumption. This prevents a proposal from appearing more complete merely because it leaves uncertain items unstated.

For each alternative, request the same categories of information: scope included and excluded; proposed roles; payment timing and components; public owner tasks; operations and maintenance assumptions; schedule dependencies; change procedures; acceptance criteria; and end-of-term treatment. Ask how each figure or obligation was derived, and whether it is an estimate, a proposal, or a binding term. When details cannot yet be stated, record the next decision point at which they will be resolved.

Keep review proportional to the decision stage. Early feasibility work may identify major constraints and questions without purporting to settle final contract terms. Before procurement or commitment, however, the municipality will need appropriate local legal, financial, technical, operational, and procurement review. A clear record of what is known, unknown, and subject to approval is more useful than false precision.

Frequently asked questions

Does a P3 transfer every project risk away from the municipality?

No. Public owners retain duties tied to public authority and may share or retain other risks. The agreement should specify each party's responsibilities, dependencies, and remedies.

Can a municipality assume a private partner will handle all permits?

No. Permit preparation and coordination can be assigned in different ways, while governmental decisions remain subject to the applicable authority and process. Confirm the precise roles for the project.

Does assigning construction risk guarantee a fixed cost or completion date?

No. Do not treat an allocation label as a guarantee. Review the scope, exclusions, relief events, change process, schedule terms, and remedies in the proposed agreement.

Should maintenance factor into procurement comparisons?

Yes. Maintenance responsibilities and lifecycle costs affect long-term affordability and service continuity. Define performance expectations, reporting, renewals, and end-of-term condition before comparing proposals.

Does risk allocation remove the need for public oversight?

No. The public owner still needs to monitor obligations it retains and verify that assigned responsibilities are performed as agreed. Reporting, inspection, acceptance, and escalation arrangements should be clear in the contract.

Make the next decision project-specific

A useful procurement comparison connects the facility's needs to clear responsibilities, realistic payment assumptions, and risks the assigned parties can actually manage. Civic Six Partners can discuss project-specific feasibility questions with a municipal team, while local legal, financial, operational, and procurement professionals review the applicable requirements.

Request a consultation

To discuss a municipal facility, use the Civic Six Partners contact form or call 888-222-1882.

Talk through your facility with us

Tell us what you need to build and the constraints you're working within. We'll follow up to talk through whether a partnership could fit your project.

On the first call, we'll cover

The facility your community needs
A civic building, a public safety facility or a specialized community facility, and where it will serve.
The timeline and budget you're working within
Constraints shape the partnership, so we tailor the structure to them from the first conversation.
A project summary, if you have one
Plans or a brief help, but they're optional; a short description of the project is enough to start.

Leave your details and we'll follow up to talk it through. You don't need a finished plan.

Contact Civic Six

* Required

Civic Six uses cookies for analytics to improve this site. See our cookie policy.