All articlesPublic-private partnerships

Design-Build-Finance for Public Facilities: What to Evaluate

Design-build-finance for public facilities combines coordinated design and construction with financing arranged by a private party. For a municipality, the key question is not simply whether a private party can arrange c...

Portrait of Marc Lofman

Marc Lofman

Managing Director

Design-Build-Finance for Public Facilities: What to Evaluate

Design-build-finance for public facilities combines coordinated design and construction with financing arranged by a private party. For a municipality, the key question is not simply whether a private party can arrange capital. It is whether the full delivery and payment structure fits the public need, approval path, affordability limits, contract capacity and long-term responsibilities. This guide explains what the model can mean, how to compare it with other delivery paths, and what officials should test before advancing a proposal.

Request a consultation

What does design-build-finance mean for a public facility?

Design-build-finance, often shortened to DBF, brings together two decisions that agencies sometimes examine separately. Design-build describes a delivery approach in which design and construction are coordinated under an integrated arrangement. Finance describes how some or all of the capital needed for development and construction is arranged and then repaid. In a public project, the public entity generally makes payments according to the agreement, which may spread payments over time.

The name does not tell an agency everything it needs to know. It does not by itself establish who owns or controls the site, who obtains permits, whether a public contribution is required, who operates or maintains the finished facility, or what happens to title at the end. Nor does it establish the procurement process, payment triggers, performance standards, remedies, or approval requirements. Those details depend on the proposal, contract and applicable law.

DBF can be one form of public-private partnership (P3). AIAI’s operations and maintenance toolkit notes that the term “public-private partnership” is often used for structures that include private financing, such as design-build-finance. That is a useful description of one common use of the term, not a universal definition for every jurisdiction or an explanation of any particular contract.

Some projects combine private financing with a long-term lease or availability payments. Some include operations or maintenance; others do not. Build-lease-transfer is one possible structure, not a synonym for every DBF project. Civic Six Partners describes a model of financing and developing public facilities and leasing completed assets back to public entities under long-term agreements. A municipality considering any proposal should confirm the actual contracting parties and obligations rather than infer them from a model name.

How does DBF compare with other public delivery paths?

A fair comparison starts with the same facility scope and service requirements. Traditional public delivery may use public capital, bonds, grants or public loans, subject to eligibility and local decisions, and may procure design and construction separately or through an allowed integrated approach. Under DBF, a private party may arrange capital and coordinate delivery, while the agency agrees to contract payments. The sources and timing of money differ; public responsibility for affordability and oversight does not disappear.

How the paths differ

Capital arrangement. Publicly financed delivery: The public entity evaluates available public funding options and their conditions. Design-build-finance: A private party may arrange project financing, with repayment addressed through the contract.

Design and construction. Publicly financed delivery: May be procured separately or using an integrated method permitted by law. Design-build-finance: Design and construction are often coordinated by a delivery team under the agreement.

Payment profile. Publicly financed delivery: Public cash needs may follow funding availability, appropriations and construction milestones. Design-build-finance: Payments may be made over an agreed period; timing and triggers must be defined.

Operations and maintenance. Publicly financed delivery: The public owner sets and funds its own arrangements unless separately contracted. Design-build-finance: May be included or excluded; responsibility is not automatic.

Title and end state. Publicly financed delivery: The public entity's ownership and future choices depend on its project structure. Design-build-finance: Title, transfer, lease expiry and continuation rights depend on the agreement.

Risk and oversight. Publicly financed delivery: Risk is assigned through public contracts, law and internal management. Design-build-finance: Only specifically assigned and enforceable duties shift; public oversight remains essential.

Do not compare only the initial cash requirement or an annual payment. A DBF proposal can shift when capital is needed, but financing has a cost. Depending on the terms, cumulative contract payments can exceed the cost of a traditional financing path. The comparison should account for financing charges and fees, public staff and adviser costs, construction, operating and maintenance obligations, likely renewal work, changes in scope, and the value or condition of the facility at the end.

Keep the assumptions consistent. If one option includes site work, furniture or maintenance and another excludes them, their headline totals are not comparable. If one schedule starts payments at occupancy and another starts earlier, identify that difference. If the public agency retains costs for utilities, insurance, operations or repairs in one proposal, include them in the lifecycle view. An apples-to-apples comparison is a disciplined set of assumptions, not a promise that every uncertain future cost can be predicted precisely.

When might a municipality examine the model?

DBF may merit evaluation when an agency has a defined facility need, wants to consider integrated design and construction, and is willing to examine a payment structure that includes private financing. It can be relevant to the types of public facilities Civic Six lists, including fire stations, police stations, sheriff’s operations, emergency operations centers, civic administration and public-service buildings, community centers, courthouses, service garages, maintenance facilities and public-works buildings. A facility category alone does not show that the model is suitable or available.

The approach may be a poor fit if the agency cannot define the required service and scope, does not have a credible path to meet the payment obligations, cannot obtain needed approvals, or lacks the capacity to oversee a complex contract. It may also be a poor fit if the expected private financing cost is not justified by the project structure, if public control requirements cannot be met, or if the proposed allocation leaves the agency with risks it cannot manage. These are reasons to test the alternatives, not automatic conclusions about a project.

Start with the public outcome. A fire station, for example, has operational needs tied to response functions, equipment and staff routines. A community center has different access, use and operating questions. A public-works facility may depend on site circulation and the functions it must support. In each case, officials should define the service requirement first, then assess whether a delivery and financing approach can support it. Avoid selecting a structure because its label sounds innovative or because it appears to reduce this year’s capital need.

Review Civic Six’s listed public facility services to understand the facility types it describes. A listed category is not a commitment that a particular project qualifies, a statement of standard terms, or a substitute for local legal and financial review.

What should officials establish before comparing proposals?

1. Define the need and the service outcome

Write down the problem the agency is trying to solve. Describe who uses the facility, what functions it must support, what is inadequate about the current arrangement and what happens if the project is delayed. Separate essential requirements from preferences. This makes it easier to test alternatives such as renovation, phased work, replacement or deferral without confusing a preferred building concept with the underlying public need.

Develop a functional program at a level appropriate to the decision. Identify expected capacity, access, safety and resilience needs, major systems, equipment interfaces, operating patterns and likely future changes. Mark what is known, what is an estimate and what still needs investigation. If the program is too vague, competing proposals may price different facilities while appearing to answer the same request.

Choose evaluation criteria before reviewing a preferred solution. Possible criteria include service fit, affordability over time, delivery approach, maintainability, adaptability, public access, construction disruption and the agency’s ability to monitor the agreement. Record why each criterion matters. A transparent set of criteria supports consistent evaluation and gives decision-makers a clear explanation to share with the public.

2. Establish site and scope assumptions

List the candidate site or sites and identify what the agency knows about ownership, access, utilities, environmental or physical constraints, adjacent uses and planning conditions. Do not treat a site as ready simply because it is publicly owned. Determine which studies, surveys, approvals or third-party coordination may be needed, and identify who would obtain and pay for them under each option.

State what the scope includes and excludes. For example, set out whether the comparison includes demolition, site preparation, utility connections, equipment, commissioning, furnishings, technology or temporary services. The list will vary by facility. Include assumptions about phasing and continued public operations if work affects an occupied site. When a proposal depends on the agency supplying land or information, write that dependency down so it is visible in the schedule and risk review.

Keep an assumptions register. For each unresolved item, note the current assumption, its source, the person responsible for confirming it, the date it must be resolved and the potential consequence if it proves wrong. This simple control prevents uncertain details from quietly becoming fixed facts in an early financial comparison.

3. Build an affordability baseline

Work with the agency’s finance staff and qualified advisers to establish what payment obligations could be supported across the likely contract period. The baseline should identify possible public contributions, expected payment sources, budget cycles, contingency needs, escalation assumptions and the effect of other planned capital commitments. A private financing arrangement changes how capital may be provided; it does not eliminate the public entity’s obligation to make payments required by the agreement.

Compare the proposed payment schedule with appropriate public financing alternatives using the same scope, timing assumptions and evaluation period where possible. Ask for the inputs behind each figure, including financing assumptions, fees, payment triggers, any indexation, and what conditions can change the amount. Where exact costs are not yet known, use scenarios rather than presenting a single early estimate as certain. A scenario should identify its assumptions and show how the conclusion changes if a key input changes.

Include the costs that can be easy to leave out of a headline comparison. These may include agency procurement and oversight time, legal and financial advice, insurance, utilities, operations, maintenance, lifecycle replacements, change management and end-of-term work. Avoid assuming that all of these are assigned to the private party. Read the proposed scope and responsibility matrix to identify which party carries each item and what exceptions apply.

Review delayed occupancy and termination as affordability events, not just legal clauses. Ask when payments start, what happens if the facility is not available when expected, how a dispute affects payments, and what obligations may survive early termination. The answers depend on the contract. The purpose of this review is to expose the public entity’s commitments before it decides whether a structure is financially workable.

4. Map procurement, governance and approvals

Prepare an approval map before committing to a procurement timetable. Identify the public body with authority to define the project, approve a solicitation, select a proposal, execute an agreement and authorize future payments. Determine what public notice, competitive process, governing-body action, budget action, voter approval or other legal requirements may apply. Requirements vary by jurisdiction and structure, so municipal counsel should verify them.

Do not assume that private financing bypasses competition or a required vote. Nor should an agency presume that a particular accounting, debt or budget treatment applies based only on the name of the transaction. Ask counsel and finance professionals to review the proposed structure and its effect under applicable rules. Keep legal advice distinct from general project education; a guide or early conversation cannot determine a municipality’s specific authority.

Put approval points on a decision calendar. Include time for internal review, public meetings, procurement documents, questions from respondents, evaluation, negotiations and authorization. Make clear which steps can occur in parallel and which depend on a prior decision. If an approval is uncertain, show that dependency rather than building a schedule around an assumed outcome.

Public engagement belongs in the plan too. Identify what residents need to understand about the public need, the alternatives considered, the proposed payment obligations, retained responsibilities and end-of-term provisions. Use plain descriptions and distinguish confirmed terms from open issues. Clear communication does not replace formal approvals; it helps the community understand the decision being made.

5. Assign responsibilities and risks

Build a responsibility matrix that covers site control or acquisition, surveys and investigations, design, permitting, financing, construction, commissioning, operations, maintenance and end-of-term handover. For each task, identify who performs it, who approves it, who supplies information, who pays and what happens if the task is late or incomplete. An entry such as “private partner responsible” is not enough if the contract later contains broad exceptions or public dependencies.

Then examine each material risk. Ask which party can control or reduce it, what information is needed to manage it, whether the agreement assigns it clearly and what remedy applies if the risk occurs. Site conditions, utility coordination, changes in public requirements, permit timing, construction completion, cost changes, maintenance performance and future public needs may be addressed differently across agreements. The agency should understand the risk it retains even if a proposal describes broad risk transfer.

Pay close attention to interfaces. A private design-and-construction team may depend on timely agency decisions, access to the site, agency-furnished data or approvals from outside bodies. Define how those dependencies are documented and how a delay or changed assumption is handled. The public entity should also know how it will review design, inspect progress, verify completion and preserve a record of decisions without taking on responsibilities the agreement assigns elsewhere.

Risk allocation is not simply a matter of assigning every uncertainty to one side. A party that cannot control an event may price the exposure, request exclusions or be unable to manage it. A useful contract makes responsibilities understandable, identifies exceptions and establishes a workable process for changes and disputes. Counsel and technical advisers should test whether the written allocation matches the project’s real operating conditions.

6. Decide how operations and maintenance fit

Confirm whether operations and maintenance are included, excluded or divided. If maintenance is part of the agreement, define the assets covered, service standards, inspection and reporting requirements, response expectations, exclusions and remedies for failure. Clarify responsibility for routine work, major repairs and replacement of systems at the end of their useful life. If maintenance stays with the public owner, the agency needs a credible staffing and funding plan alongside any lease or other contractual payments.

Consider the whole operating environment. Building systems, equipment, accessibility updates, energy use, security, cleaning, grounds and changing service needs can all affect the owner’s experience, depending on the facility and contract scope. State which items are relevant to the project rather than relying on a generic promise that a facility will be maintained. Ask how performance evidence will be collected and who has the right to inspect or request correction.

Separate maintenance standards from desired outcomes. A written requirement to inspect a system at a set interval may be verifiable, while a broad phrase such as “high quality” may not say what happens if performance falls short. Where standards are needed, specify the expected result, how it will be measured, who verifies it, what cure period applies and what remedy is available. The detail should match the public service and the agreement’s term.

7. Review title, handback and exit choices

Read the end-of-term provisions before comparing proposals. An arrangement may end with lease expiry, a transfer of ownership or a negotiated continuation. The agency should know who holds title during the term, what rights it has to occupy and use the facility, and what conditions govern a transfer or extension. Do not assume ownership automatically transfers because a structure is described as a partnership or lease.

Ask what condition the facility must be in at handback and how that condition will be assessed. Identify required records, outstanding repairs, remaining useful life expectations, unresolved claims and the process for addressing defects. Clarify who pays if a condition assessment finds that required work is incomplete. These provisions matter because the building will still need to support public services after the original agreement ends.

Also examine exit options if public needs change before the scheduled end. The contract may set conditions and payment consequences for termination, assignment, refinancing, extension or a change in use. The exact options depend on negotiated terms and applicable law. Officials should consider whether they can manage the consequences in realistic scenarios, not just whether the agreement works under an unchanged, best-case plan.

How can an agency evaluate proposals consistently?

Use a written evaluation framework and apply it to every option. Start by checking whether each proposal meets the functional program and mandatory requirements. Then compare affordability, schedule assumptions, responsibilities, risk treatment, maintenance, public control, end-of-term conditions and the agency’s oversight needs. Keep the evaluation record tied to the criteria rather than relying on a persuasive presentation or a single payment figure.

Require comparable information. Ask every respondent to describe the proposed delivery team and the entity that would contract with the public owner, the financing arrangement, included and excluded scope, payment triggers, assumptions, dependencies, risk allocation, maintenance obligations and proposed end state. If the responses use different assumptions, identify those differences and request clarification through the procurement process permitted by the agency’s rules.

Separate facts, estimates and commitments. A design concept is not a final scope. An estimated schedule is not a contractual completion obligation. A general statement about risk is not a detailed allocation. A proposed financing approach is not proof that the agency has obtained all required approvals. The evaluation team should label what is supported by documentation, what is still being negotiated and what requires an independent adviser’s review.

Consider value as a combination of public service and lifecycle obligations. A proposal that appears attractive at the start may have exclusions, retained responsibilities or end-of-term conditions that matter later. Conversely, an option with a higher apparent payment may include scope or services that are excluded elsewhere. The agency’s analysis should explain the tradeoffs and show which assumptions drive the result. It should not present uncertain comparisons as guaranteed savings or guaranteed performance.

For a process overview, officials can review Civic Six’s public-private partnership FAQs alongside jurisdiction-specific advice. FAQs are a starting point for questions, not a substitute for an agency’s procurement documents, counsel or financial analysis.

What should a project-specific feasibility review cover?

A practical feasibility review turns general interest into decisions and questions that can be answered. It should not declare a project approved or imply that a particular financing structure is available before the relevant review. At a minimum, organize the work around the following areas:

Public need: service gap, facility condition, users, required functions, urgency and alternatives.

Site and scope: site control, access, known constraints, utilities, functional program, phasing and unresolved investigations.

Affordability: potential funding sources for evaluation, payment capacity, contract cash flows, lifecycle costs, assumptions and scenarios.

Authority and process: procurement method, approvals, governing-body decisions, public engagement and legal review.

Delivery capability: design, construction, financing, project controls, agency oversight and responsibility interfaces.

Operations: operating model, maintenance scope, renewal needs, staffing and performance monitoring.

End state: title, handback condition, extension or continuation choices, and exit implications.

Decision gates: the evidence required to continue, revise the scope, compare another route or stop work.

Assign an owner to each information gap and set a date for resolving it. A brief may note, for example, that site utility capacity is unknown, finance staff must test payment scenarios, and counsel must confirm the procurement pathway. That is more useful than presenting those matters as settled simply to keep an early schedule moving.

Set decision gates that preserve alternatives. An agency may first confirm the need and site, then authorize a feasibility assessment, then determine whether a competitive procurement is appropriate, and later consider a specific proposal. At each gate, list the decision-maker, evidence needed, unresolved risks and conditions for proceeding. This helps prevent early interest in a delivery model from becoming an assumption that the project must use it.

Keep the record understandable to people who were not in the initial discussions. Document the options considered, the reasons for eliminating or advancing them, the assumptions used in comparisons, adviser input and public decisions. A clear record supports later oversight and helps explain why an agency selected a path even when reasonable alternatives existed.

Questions officials should ask a potential project partner

Questions should reveal the actual transaction rather than invite broad assurances. Officials can ask:

Which legal entity would sign the agreement, and what specific obligations would it accept?

Who arranges financing, what assumptions and fees affect payments, and when do payment obligations begin?

What work is included in the scope, and what public contributions, exclusions or dependencies are assumed?

Which party handles design, construction, permits, commissioning, operations and maintenance?

What supports the schedule and cost assumptions, and what events can change them?

How will the agency review design, monitor construction, confirm completion and address deficiencies?

Which risks are assigned to each party, what exceptions apply and what remedies are available?

What approvals does the public owner need, and which legal or accounting conclusions require its own advisers?

What happens at the end of the agreement, including title, facility condition, continued service and possible extension?

What project experience is attributable to the proposed contracting entity, and what can be independently verified?

Request supporting material that fits the procurement stage. A responsibility matrix, scope narrative, payment schedule, assumptions register, draft performance standards and end-of-term outline can help reviewers find gaps. If an item is not ready, record that it is unresolved and define when it must be provided. Do not treat a missing detail as favorable simply because it has not yet been priced.

When reviewing experience, distinguish the experience of a company from that of individuals, partners or a broader project team. Ask for the entity’s role, the owner, the stage reached and permission to verify the description. Participation by an individual on a project does not by itself establish that the current firm financed or contracted for that project. Clear attribution protects the agency’s evaluation and gives the public an accurate account of the evidence considered.

Request a consultation

Frequently asked questions

Does design-build-finance mean a public facility is free?

No. A private financing arrangement changes the source or timing of capital, not the public entity’s payment obligation. Contract payments may support development, construction, financing and applicable fees, and total payments can exceed traditional financing.

Does private financing remove procurement or voter approval requirements?

No. Applicable procurement, governing-body, voter, budget and other legal approvals depend on the jurisdiction and transaction. Municipal counsel should confirm the process before the agency relies on a proposed schedule or structure.

Does a private party take every project risk?

No. The contract allocates specific responsibilities and risks, often with exceptions and public dependencies. Officials should review each duty, who controls it, what information is needed and what remedy applies if performance falls short.

Does design-build-finance always include maintenance?

No. Maintenance may be included, excluded or divided. The agreement should define covered assets, standards, inspections, exclusions, repairs and remedies. If the public owner retains maintenance, it needs a funding and operating plan.

Does ownership always transfer to the municipality at the end?

No. The agreement may provide for lease expiry, a transfer or a negotiated continuation. Review title, handback condition, extension rights and exit consequences instead of assuming a particular end state.

Make the decision about the project, not the label

Design-build-finance is one possible way to coordinate design and construction and arrange project capital, but the model name cannot establish affordability, approval, value or risk transfer. A sound municipal decision begins with a defined public need and ends with a documented understanding of payments, retained responsibilities, oversight, maintenance and end-of-term choices. Compare the complete structure with realistic alternatives and obtain project-specific legal, financial and technical review before proceeding.

Talk with Civic Six about this facility

A design-build-finance conversation should stay specific to the facility, the approvals, and the payment structure. Request a consultation 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.