# Seven Proposal Sections That Always Need Project Examples **By Dan Cumberland** · Published April 23, 2026 · Categories: AI Strategy > Architecture proposals in competitive public and institutional markets are evaluated through Qualifications-Based Selection (QBS)— a procurement model used in... ## Why Project Examples Are Non\-Negotiable in Competitive Proposals Architecture proposals in competitive public and institutional markets are evaluated through Qualifications\-Based Selection \(QBS\)— a procurement model used in most U\.S\. public AEC projects that evaluates qualifications before fee\. Evaluators aren't reading for inspiration\. They're looking for proof\. Their actual job is risk reduction, not vendor selection\. A selection committee member who recommends your firm is putting their own credibility on the line\. What they need to see, per Neumann Monson Architects' analysis of standard evaluation criteria[4](/blog/blog-architecture-sections#ref-4), falls into six categories: - Project experience — which projects, what scope, what outcomes - Methodology and approach — how you've applied your process, not just what it is - Project understanding — proof you've navigated analogous complexity before - Staff qualifications — which team members have done this type of work - Consultant team — relevant prior experience with subs and partners - Cost — fee relative to scope Five of those six criteria require project\-specific evidence to answer\. Generic proposals signal low investment in understanding the client's situation\. Evaluators identify them immediately[3](/blog/blog-architecture-sections#ref-3)\. Per Flowcase research, firms that applied selective pursuit strategies— submitting 38% fewer proposals with richer, more targeted evidence— saw awarded work rise 52%[2](/blog/blog-architecture-sections#ref-2)\. That correlation isn't accidental— it's the return on building [better proposal evidence systems](/blog/ai-automation-guide) into your BD operations\. Now, the seven sections— and exactly what each one needs\. ## 1\. The Executive Summary The executive summary is where evaluators decide whether to keep reading\. Without a specific project reference that maps to the client's challenge, the summary reads as marketing copy— and evaluators know the difference immediately\. The executive summary's job is to mirror the RFP evaluation criteria and connect the client's need to your solution\. The Proposal Lab is direct on this: your opening pages must make it immediately clear why your firm is the right fit for this project— not just any project[5](/blog/blog-architecture-sections#ref-5)\. That connection requires evidence, not aspiration\. **What failure looks like:** A summary describing firm history, awards, and philosophy with no project anchor\. You've written a brochure\. **What good looks like:** "On the Riverside Transit Authority's mixed\-use development project, we managed a comparable community input process across 14 stakeholder groups— completing on schedule despite mid\-project scope changes\. That experience applies directly to the engagement challenges you've outlined in Section 3 of your RFP\." Two to three sentences\. Project type, analogous challenge, outcome\. Done\. The summary sets the tone\. The next section is where firms most often lose evaluators— because it requires demonstrating understanding of the client's project, not just showcasing the firm's\. ## 2\. Project Understanding The project understanding section is not a place to restate the RFP\. Evaluators already know what they want to build\. They're reading this section to find out if you understand why it's hard— and whether you've navigated similar complexity before\. Here's the problem most firms run into: you can't read the label from inside the bottle\. Firms write this section from inside their own experience— describing what they plan to do, using their own process language, showing the evaluator how capable they are\. But the evaluator is sitting on the other side of the table asking a different question: "Have they been here before?" As OpenAsset puts it, telling the client what their specific issue is and addressing it directly is crucial[12](/blog/blog-architecture-sections#ref-12)\. Crucial— but not sufficient\. The firms that win this section don't describe the future project\. They reference a past one\. **What failure looks like:** Restating the RFP scope in different words\. Two hundred words that add nothing new\. **What good looks like:** "On the Millbrook Library renovation, we faced a similar constraint— a phased construction schedule that required the building to remain partially operational throughout\. Here's how we managed it, and why the same approach applies to your project\." Identify the 1–2 most challenging aspects of the current project\. Cite a specific past project where you navigated a comparable challenge\. Connect them directly\. ## 3\. Relevant Experience / Past Projects The relevant experience section should include 3–5 handpicked projects— not a full portfolio dump— with quantified outcomes and an explicit connection to the current project for each one\. Most BD managers know to populate this section\. But knowing it needs examples and knowing how to make them work are different things\. Flowcase is clear: "Select projects that mirror RFP requirements"— meaning scope, size, sector, and complexity— and quantify what you delivered[2](/blog/blog-architecture-sections#ref-2)\. The Proposal Lab goes further: "Explicitly connect the dots to the new project\."[5](/blog/blog-architecture-sections#ref-5) A past project without a stated connection is just a list\. ```html-table
Data PointWhy It MattersExample
Client / OwnerEstablishes context similarityCity of Durham, Municipal Library, $18M
Scope summaryRFP scope alignmentGround-up new construction, 45,000 SF
Timeline performanceRisk evidenceDelivered 3 weeks early despite supply chain delays
Budget performanceFinancial stewardship2.1% under budget at closeout
Connection to current projectExplicit relevance"The community input process here would directly apply to..."
``` Per OpenAsset, these sections need "concrete examples of expertise applied and areas of measurable improvement"— not just project names and dates[1](/blog/blog-architecture-sections#ref-1)\. TrebleHook puts the same principle differently: review past projects, articulate your role clearly, use metrics[8](/blog/blog-architecture-sections#ref-8)\. Without the metrics, the example is decorative\. **What failure looks like:** Ten projects listed with a photo and two sentences each\. No selection logic\. No outcomes\. No connection to why any of them are relevant here\. The relevant experience section is expected\. The technical approach section is where firms have a bigger opportunity— and a worse track record\. ## 4\. Technical / Design Approach Every methodology claim in the technical approach section needs a project proof point\. If you describe your sustainable design process, show the project where it produced measurable results\. Without evidence, the approach section reads as theoretical\. This is The Proposal Lab's core principle for proven capabilities: "Demonstrate it, don't just write it\."[6](/blog/blog-architecture-sections#ref-6) And in a visual industry, StoryDoc is right that proposals must show rather than tell through immersive demonstrations of previous work[9](/blog/blog-architecture-sections#ref-9)\. That means drawings AND construction photographs— not just renderings— that demonstrate concept\-to\-completion capability\. The format that works: **Claim → Project example → Quantified outcome → Connection to current project** Instead of: *"Our integrated design process reduces coordination conflicts\."* Write: *"On the Meridian Civic Center, our integrated BIM \(Building Information Modeling\) coordination process reduced RFIs \(requests for information\) by 43% compared to project baseline estimates\. For your project's complex MEP coordination requirements, we'd apply the same methodology\."* **What failure looks like:** Three hundred words of process description with no project anchors\. You've described a philosophy\. Evaluators need a track record\. The approach section earns the "always" in this article's title— there are no exceptions\. Every methodology claim is a promise\. Project proof turns it into evidence\. ## 5\. Team Qualifications / Resumes Evaluators reading the team qualifications section have one question per person: "Has this person done this before?" Credentials and years of service don't answer it\. A two\-sentence project history does\. The Proposal Lab makes this concrete: a project manager described as someone "who has led three library construction projects to success" is more credible than a project manager with fifteen years of general experience[5](/blog/blog-architecture-sections#ref-5)\. Archisoup confirms the structural requirement: team bios should include key team members, their roles in the project, and descriptions of past projects[7](/blog/blog-architecture-sections#ref-7)\. **Credential\-list bio \(ineffective\):** > "Maria Chen, P\.E\. — Principal in Charge\. 18 years of experience in public architecture\. Licensed in 12 states\. Member AIA\." **Narrative bio with project history \(effective\):** > "Maria Chen, P\.E\. — Principal in Charge\. Maria has led three public library projects to successful completion, including Westside Branch \(22,000 SF, $14M\) and Eastport Central \(38,000 SF, $24M\)\. Both delivered on schedule within 1% of construction budget\. She will serve as your primary point of contact from design development through closeout\." And there's a human dimension here that Pinstripe Marketing gets right: authentic bios with genuine enthusiasm work because evaluators respond to people, not org charts[3](/blog/blog-architecture-sections#ref-3)\. Include only team members who will actually work on this project— each one with relevant project history, not generic credentials\. ## 6\. References References in an architecture proposal should be project\-specific— not a general list of contacts\. The best references speak to comparable project types and signal to evaluators that there's a track record worth verifying\. Qualifications\-Based Selection prioritizes demonstrated project experience\. Per Neumann Monson Architects, evaluation criteria consistently score project experience as a distinct category[4](/blog/blog-architecture-sections#ref-4)\. A reference who can speak directly to how you performed on a comparable project is direct evidence for what the committee is evaluating\. Include a brief context annotation with each reference\. Monograph's guidance on architect qualification statements applies directly: previous work examples should note the project owner, scope, and a brief description[10](/blog/blog-architecture-sections#ref-10)\. Apply that same logic to reference context— one sentence identifying the project and its comparability to the current RFP\. **What failure looks like:** Three names, three phone numbers, no project context\. Evaluators who call a reference asking about your library experience and hear "I worked with them on a residential project" have learned nothing useful\. A reference from the right person, on the right project type, does more work than three general references\. It tells the committee: someone who's been through this before would hire them again\. ## 7\. Appendices Appendices aren't a dumping ground for leftover content\. They're where evaluators who want more proof go— and firms that leave them empty are squandering the opportunity\. Per StoryDoc, appendices should contain case studies that highlight your best work[9](/blog/blog-architecture-sections#ref-9)\. That means extended versions of examples you summarized earlier in the proposal\. The evaluator who was intrigued by a two\-paragraph relevant experience summary has somewhere to go for depth\. **What a complete appendix case study includes:** - Full project narrative \(scope, challenge, approach, resolution\) - Architectural drawings and construction photographs - Timeline and budget performance data - Client satisfaction outcomes or testimonials - Risk management documentation for analogous project challenges Critically, reference appendix content from within the body of your proposal: "For the full case study on our work at Millbrook, see Appendix A\." Appendices that aren't referenced don't get read\. **What failure looks like:** An empty appendix\. Or one full of general firm marketing materials that weren't relevant enough to include in the main document either\. Those are the seven sections\. Here's the question most firms ask next: what do you do when you don't have an exact match? ## What to Do When You Don't Have the Perfect Example When your portfolio doesn't include an exact project match, the goal is to find the closest analogy and make the connection explicit— not to pretend the gap doesn't exist\. Partial examples with honest framing are more credible than forced fits[3](/blog/blog-architecture-sections#ref-3)\. Evaluators read proposals for a living\. They know when they're being sold something that doesn't quite fit\. An honest framing of an adjacent project outperforms an overreach every time\. The explicit bridge technique: > "While our firm hasn't built a dedicated transit facility, we've managed comparable infrastructure complexity on the Harborview Civic Center— a phased construction schedule with active occupancy requirements and multiple public\-sector stakeholder groups\. The coordination and communication challenges you're facing are structurally similar, and our approach would adapt directly\." What not to do: stretch an irrelevant project beyond recognition, or leave the section generic because you don't have a perfect example\. An acknowledged analogous example is stronger than an empty section\. The Proposal Lab's win strategy guidance applies here too: address your firm's weaker areas explicitly rather than hoping evaluators won't notice[5](/blog/blog-architecture-sections#ref-5)\. Evaluators always notice\. Honesty builds more confidence than silence\. ## How AI Is Changing Proposal Evidence Management The firms winning more work aren't just writing better proposals— they're building better systems for managing the project evidence those proposals require\. The constraint is retrieval speed\. Per OpenAsset, 63% of AEC marketing teams spend over half their time on proposals[1](/blog/blog-architecture-sections#ref-1)— and only 25% believe they can complete every targeted proposal their firm pursues[1](/blog/blog-architecture-sections#ref-1)\. Much of that time is spent hunting for the right project data, the right team member history, the right outcome metrics\. The evidence exists in your files\. Finding it fast enough to respond to an RFP is the bottleneck\. AI\-powered platforms like OpenAsset, Flowcase, and Monograph are addressing this directly— using AI to tag, retrieve, and surface the most relevant project examples by proposal type, client sector, and scope requirements\. Firms with a structured project evidence library respond faster, with better\-matched examples, and spend more time on the narrative work that actually wins proposals\. If proposal operations is where you want to start with AI— and the evidence in this article suggests it should be— [AI strategy for your firm](/services/ai-strategy/) is exactly where that conversation begins\. Firms building out [AI implementation for professional services](/services/ai-implementation/) are finding that proposal operations often have the clearest, most measurable returns\. ## Quick Reference — What Each Section Needs Here's the full breakdown at a glance\. Each row is a proposal section; each column is what it needs to include project evidence effectively\. ```html-table
SectionProject Example NeededFormat# of ExamplesWhat Failure Looks Like
Executive Summary✓ Yes2-3 sentences1 comparable projectGeneric firm description
Project Understanding✓ Yes1 paragraph1 analogous challengeRestating the RFP
Relevant Experience✓ YesCase study format3–5 projectsPortfolio dump without selection logic
Technical Approach✓ YesClaim + proof point1 per major claimMethodology with no project anchors
Team Qualifications✓ YesNarrative bios2-3 projects per personCredentials list only
References✓ YesAnnotated contacts3–5 project-specificGeneric contact list
Appendices✓ YesFull case studies1-3 extendedEmpty or unrelated materials
``` ## FAQ — Architecture Proposal Sections and Project Examples These are the most common questions about project examples in architecture proposals— with direct answers for teams building or reviewing proposals now\. **What sections of an architecture proposal need project examples?** Seven: executive summary, project understanding, relevant experience, technical approach, team qualifications, references, and appendices\. Each section requires evidence in a different format— from 2\-sentence summary callouts in the executive summary to full case studies in the appendix\. **How many past projects should be in a proposal?** The relevant experience section should contain 3–5 handpicked projects selected for scope, sector, and complexity match[2](/blog/blog-architecture-sections#ref-2)[5](/blog/blog-architecture-sections#ref-5)\. Other sections need 1–2 targeted examples per claim or team member\. **What makes a project example relevant to an architecture proposal?** A relevant example matches the current project's scope, size, and sector— and includes quantified outcomes: timeline performance, budget results, and documented client satisfaction data[2](/blog/blog-architecture-sections#ref-2)[8](/blog/blog-architecture-sections#ref-8)\. **Why do evaluators reject generic architecture proposals?** Generic proposals signal the firm didn't invest in understanding the client's specific situation\. AEC evaluators read proposals for a living and identify boilerplate immediately[3](/blog/blog-architecture-sections#ref-3)[1](/blog/blog-architecture-sections#ref-1)\. **What's the difference between a portfolio and project examples?** A portfolio is a library of past work\. Project examples are curated, connected, and tailored to a specific proposal— each one selected because it answers a specific evaluator question[5](/blog/blog-architecture-sections#ref-5)\. ## Conclusion Winning architecture proposals aren't built section by section\. They're built around a single discipline: making project evidence work in every section that evaluators actually score\. The firms that win consistently aren't necessarily the most experienced ones\. They're the ones who know how to make that experience visible— in all seven places evaluators are looking for it\. That takes both the writing skill to frame evidence compellingly and the systems to find the right evidence quickly\. If building that evidence system is the operational gap between your current BD pipeline and the win rate you're after, [Dan Cumberland Labs works with architecture and professional services firms on exactly this kind of implementation](/blog/measuring-ai-success)\. ## References 1. OpenAsset, "How to Create Winning AEC Proposals" \(2024\) — [https://openasset\.com/blog/how\-to\-create\-winning\-proposals/](https://openasset.com/blog/how-to-create-winning-proposals/) 2. Flowcase, "How to Write Winning AEC Proposals: Expert Tips for Higher Success Rates" \(2024\) — [https://www\.flowcase\.com/blog/how\-to\-write\-winning\-aec\-proposals\-expert\-tips\-for\-higher\-success\-rates](https://www.flowcase.com/blog/how-to-write-winning-aec-proposals-expert-tips-for-higher-success-rates) 3. Pinstripe Marketing, "Writing A/E/C Proposals That Win: What Clients Really Want to See" \(2024\) — [https://pinstripemarketing\.com/aec\-proposals/](https://pinstripemarketing.com/aec-proposals/) 4. Neumann Monson Architects, "Architectural Fee Proposals: What They Include and How to Compare" \(2024\) — [https://neumannmonson\.com/blog/architectural\-fee\-proposals\-what\-they\-include\-how\-to\-compare](https://neumannmonson.com/blog/architectural-fee-proposals-what-they-include-how-to-compare) 5. The Proposal Lab, "The Seven Hallmarks of Successful Architecture Proposals" \(2024\) — [https://theproposallab\.com/blog/seven\-hallmarks\-successful\-architecture\-proposals/](https://theproposallab.com/blog/seven-hallmarks-successful-architecture-proposals/) 6. The Proposal Lab, "Expert Tips for Writing an Architectural Proposal" \(2024\) — [https://theproposallab\.com/blog/how\-to\-win\-your\-next\-architectural\-proposal/](https://theproposallab.com/blog/how-to-win-your-next-architectural-proposal/) 7. Archisoup, "A Guide to Architectural Proposals" \(2024\) — [https://www\.archisoup\.com/architectural\-proposal](https://www.archisoup.com/architectural-proposal) 8. TrebleHook, "8 Tips for Crafting Winning AEC Proposals" \(2024\) — [https://treblehook\.com/blog/8\-tips\-for\-crafting\-winning\-aec\-proposals/](https://treblehook.com/blog/8-tips-for-crafting-winning-aec-proposals/) 9. StoryDoc, "How to Write an Architecture Project Proposal \(\+Examples\)" \(2024\) — [https://www\.storydoc\.com/blog/how\-to\-write\-an\-architecture\-project\-proposal](https://www.storydoc.com/blog/how-to-write-an-architecture-project-proposal) 10. Monograph, "Guide to Architectural Proposals" \(2024\) — [https://monograph\.com/blog/guide\-to\-architectural\-proposals](https://monograph.com/blog/guide-to-architectural-proposals) 11. OpenAsset, "10 Tips for Writing a Compelling Architecture Proposal" \(2024\) — [https://openasset\.com/resources/10\-tips\-for\-writing\-a\-compelling\-architecture\-proposal/](https://openasset.com/resources/10-tips-for-writing-a-compelling-architecture-proposal/) --- Source: https://dancumberlandlabs.com/blog/architecture-sections/