Design-Build Proposal Narrative Structure

The technical narrative on a design-build response is the document that decides most evaluations. The price evaluation matters, but on best-value source selection (which most federal design-build and a substantial share of state and municipal design-build use), the technical narrative is where the procurement is won or lost. A team with a strong narrative and a slightly higher price commonly beats a team with a weak narrative at a lower price.

The narrative is doing three things at once. It is demonstrating that the team understands the project, that the team has the capability to deliver it, and that the team’s approach is the right approach for this project. The first task is comprehension. The second is qualifications. The third is judgment.

Reading the solicitation carefully and structuring the narrative around what the owner is actually evaluating is the foundation. Most design-build solicitations spell out the evaluation factors (technical approach, management approach, key personnel, past performance, schedule, design quality, sustainability, and others) with assigned weights or relative importance. A narrative organized around the owner’s factors is much easier for the evaluator to score than one organized around the contractor’s preferred presentation.

The section structure of a design-build narrative typically maps to the evaluation factors stated in the solicitation. The owner’s ordering becomes the team’s ordering. Some common section types appear across most procurements.

Project understanding

An opening section that demonstrates the team has read the solicitation, understood the owner’s program, and identified the key challenges and opportunities of this specific project. The section is short but high-leverage; an evaluator who reads project understanding and finds it generic concludes that the rest of the narrative is going to be generic too.

Design approach

The team’s approach to the design phase: the design philosophy, the key design moves the team is proposing, the integration with the owner’s program, the basis-of-design assumptions, and the conceptual diagrams that illustrate the approach. On most design-build evaluations, this is one of the highest-weighted sections. The content has to be substantive (specific, evidence-based, project-relevant) rather than generic design-firm marketing.

Key personnel

The proposed team members, their roles on this project, their experience on similar projects, and their availability for this specific work. Resumes for each key person, structured to support the narrative claims. Personnel that the owner can map to specific Section E projects elsewhere in the response (or to past projects on the contractor’s past-performance list) score better than personnel whose claimed experience is not corroborated by the rest of the response.

Management plan

How the team will manage the design and construction work, how the design and construction sides of the team coordinate, how owner reviews are handled, how decisions are made, how risk is managed, how schedule is controlled. The management plan is where the team demonstrates that the design-build entity is more than a paper construct: that the contractor and the design firm have a working relationship and a defined approach to running the project together.

Schedule

The proposed project schedule, with key milestones, the design phase sequencing, the construction phase sequencing, the overlap (if any), and the basis for the durations. A schedule narrative that explains the logic supports the schedule itself; a schedule submitted without explanation reads as a number on a Gantt chart that may or may not be defensible.

Past performance

Past projects the team has performed that are relevant to this project. Project descriptions, owner contacts, performance summaries, and references that the owner can verify. Past performance on a similar project type is more valuable than past performance on a larger but unrelated project.

Project-specific factors

Some procurements call out specific evaluation factors beyond the standard set: sustainability approach, security requirements, accessibility, historic preservation, community engagement, small-business participation, anything else the owner has flagged as important. Each factor gets its own section, scoped to the depth the procurement’s evaluation criteria suggest is warranted.

The narrative’s job is to make the evaluator’s scoring easy. An evaluator reading dozens of proposals against a defined set of evaluation factors needs to find the relevant content quickly and assess it against the factor’s criteria. A narrative that organizes content along the factor lines does that work for the evaluator.

Section-to-factor alignment

The simplest alignment is one narrative section per evaluation factor. The technical-approach factor maps to the design-approach section; the management-approach factor maps to the management-plan section; the key-personnel factor maps to the personnel section. The evaluator scoring each factor finds the relevant section directly and scores it without having to assemble content from across the document.

Cross-references where content overlaps

Some content is relevant to multiple factors. The team’s proposed key personnel are relevant to both the personnel factor and the management-plan factor; the schedule logic is relevant to both the schedule factor and the management-plan factor. Cross-references in the narrative (“See Section 4.2 for the project manager’s qualifications”) help the evaluator find content the team has already presented elsewhere without forcing the team to repeat it. Repetition is sometimes necessary; cross-reference is preferred where it works.

Page limits and section length

Most design-build solicitations impose page limits, sometimes total and sometimes per-section. The team’s allocation of pages across sections should reflect the relative weight of each evaluation factor. A factor weighted at 30% deserves more pages than a factor weighted at 5%. The team’s page allocation is the team’s implicit answer to the question of which sections are most important; the answer should match the owner’s evaluation weighting.

Headers and navigation

Clear section headers, consistent formatting, and navigational aids (table of contents, section markers, cross-reference markers) make the document usable. An evaluator scoring a 200-page proposal needs to navigate it quickly; a proposal where finding the relevant content for a specific factor takes minutes rather than seconds is going to score worse than a comparable proposal that is easier to navigate.

The design-approach section and the design-related elements throughout the narrative are the parts of the response that come from the design partners on the team. The contractor’s preconstruction team writes the construction-side narrative; the design firm writes the design-side narrative; both come together into a coherent document.

The design-firm contribution

The design firm typically provides the design philosophy, the key design moves, the conceptual diagrams or schematic-level drawings the response includes, the design-team key personnel, the design-side past performance, and the design portion of the management plan. The depth of the contribution depends on the procurement’s evaluation criteria; some procurements weight design quality heavily and require extensive design-side content, while others treat design as one of several factors and require less.

Coordination with the construction-side content

The design-side content has to coordinate with the construction-side content. A design narrative that proposes a structural approach the construction team has not priced into the bid produces an inconsistent response. A construction narrative that promises a schedule the design team cannot support is the same problem in the opposite direction. The integration is the team’s job, and the integration work has to happen during the bid period, not after submission.

Voice and tone

The voice of the proposal should read as a single team’s voice, not as two voices stapled together. Practical patterns include having a single proposal manager who edits the entire document for voice consistency, building a style guide before the writing starts, and pairing a contractor writer and a design-firm writer on each section that draws content from both sides. The end product should read as a coordinated response from a working team, which is what the evaluator is being asked to assess.

Bid-stage design effort

Producing the design-side content commits the design firm to substantial bid-stage hours. The schematic-level drawings, the design narrative, the conceptual diagrams, and the technical analysis that underpins all of it are real design work performed before any contract exists. Teams that under-resource the bid-stage design work submit responses with shallow design content that score accordingly. Teams that over-resource the bid-stage design work spend on procurement that may not be won. The right resourcing level is a judgment that varies by the win probability the team assesses for the procurement.

The design-build proposal effort is one of the most resource-intensive activities a contractor undertakes. Running the effort with discipline is the difference between submitting a response on time at the quality the team intended and submitting a response under deadline pressure with content the team would have wanted to revise.

Designated proposal manager

A single proposal manager owns the document and the schedule. The proposal manager coordinates contributors across the contractor and the design firms, edits for voice and structure, manages page allocation, runs the internal review cycle, and gets the document to submission on time. Without a single owner, the document fragments and the integration suffers.

Section-level outline before writing

The team builds a section-level outline of the response against the solicitation’s evaluation factors before any writing starts. The outline shows what each section will cover, who is writing it, what the page allocation is, and where the cross-references will land. Sections written without an outline tend to drift, miss evaluation criteria, and produce content that other sections also produce.

Internal review against the solicitation

Before submission, the team reviews the response against the solicitation’s evaluation criteria as if the team is the evaluator. Each evaluation factor gets read; each section gets checked for compliance with the page limits, formatting rules, and section ordering the solicitation specifies. Gaps that the team’s own internal review identifies are gaps that the evaluator will find. Filling them before submission is faster than responding to a non-responsive finding after the fact.

The submission-package connection

The proposal narrative is one component of the larger design-build submission. The compliance matrix tracks every solicitation requirement and shows where each is addressed in the response. The drawing index organizes the conceptual drawings the response includes. The action checklist captures the contractor-supplied items that have to land before submission: bid bonds, certifications, signatures, registrations, the SF-330s for the design partners, and anything else the procurement requires. The ScalaBid Submission Packageon a design-build procurement is built to the procurement’s actual structure, with the proposal narrative organized around the owner’s evaluation factors, the compliance matrix mapping the FAR clauses and agency supplements that flowed into the solicitation, and the action checklist surfacing the items the contractor and the design partners have to deliver alongside the narrative. The contractor’s preconstruction team and the design partners work the substantive content; the package keeps the requirements visible across the response so the work has somewhere structured to land.