Proposal outline: the structure evaluators expect
Short answer: The best proposal outline is the one the buyer prescribes. If the RFP gives a response format, mirror it exactly: same section order, numbering and headings. If it doesn't, build your outline from the RFP's evaluation criteria, in order of weight, wrapped in a standard frame: cover letter, executive summary, understanding of need, solution and approach, implementation, team, proof, pricing, and terms. Unsolicited proposals use a shorter problem-solution-price-next-step structure.
In Iris: question extraction detects a prescribed response outline in an RFP, keeps its hierarchy, and makes every numbered sub-item its own row, so your response mirrors it.
Who this is for: proposal managers and sales teams deciding how to structure an RFP response or a proposal.
On this page
- Which outline should you use?
- How do RFP components map to response sections?
- Outline A: RFP with a prescribed format
- Outline B: RFP without a prescribed format
- Outline C: US federal multi-volume proposal
- Outline D: unsolicited or informal proposal
- Worked example: building an outline from a fictional RFP
- FAQ
Which outline should you use?
| Situation | Use | Why |
|---|---|---|
| RFP specifies a response format or template | A: mirror it | Evaluators score against their own structure |
| RFP lists evaluation criteria but no format | B: criteria-driven | Puts the highest-weighted content where it's found fastest |
| Federal solicitation with Sections L and M | C: volumes per Section L | Format is part of compliance |
| No RFP; you're proposing after discovery | D: short sales structure | Approvers need the decision on page one |
How do RFP components map to response sections?
A typical RFP has these components. Each one tells you something about your outline:
| RFP component | What it tells you | Where it goes in your response |
|---|---|---|
| Background / introduction | The buyer's context and drivers | Understanding of need |
| Scope of work / requirements | What must be delivered | Solution and approach; compliance matrix |
| Submission instructions | Format, order, page limits, volumes | Your outline itself |
| Evaluation criteria and weights | How you'll be scored | Section order and page allocation |
| Questionnaire / response forms | Specific questions to answer | Answered in place, in order |
| Pricing instructions / price form | How to present price | Price volume or section |
| Terms and conditions | Contract terms | Exceptions / assumptions section |
| Timeline | Deadlines, Q&A, orals | Your project plan, not the response |
| Required forms | Certifications, signatures | Forms section or appendix |
Outline A: RFP with a prescribed format
- Use the buyer's template file if provided; don't retype it.
- Copy headings and numbering exactly, including sub-items such as 3.2.1(a).
- Answer in place. Don't move content to "where it fits better."
- Add only what the instructions allow: often a cover letter, executive summary and appendices.
- Include a compliance matrix if allowed, even when not required, to show where each requirement is answered.
Outline B: RFP without a prescribed format
| # | Section | Contents | Page share (guide) |
|---|---|---|---|
| — | Cover page and cover letter | Identification; formal submission | — |
| — | Table of contents | Mirrors the RFP's requirement numbers where possible | — |
| 1 | Executive summary | Needs, solution, win themes, value | 1–2 pages |
| 2 | Understanding of requirements | The buyer's goals and constraints in their words | ~5% |
| 3 | Solution and approach | Organized by the highest-weighted criterion first | ~35–45% |
| 4 | Implementation and timeline | Phases, milestones, dependencies | ~10–15% |
| 5 | Team and management | Key people, governance, communication | ~10–15% |
| 6 | Experience and references | Comparable projects, references | ~10% |
| 7 | Pricing | Per instructions; often separate | As required |
| 8 | Assumptions and exceptions | Clear list | ~2–5% |
| — | Appendices | Résumés, certificates, sample reports, compliance matrix | — |
Page shares are a starting guide; re-weight to the RFP's criteria.
Outline C: US federal multi-volume proposal
Federal solicitations using the uniform contract format put proposal instructions in Section L and evaluation factors in Section M (FAR 15.204-1). A common volume structure, which Section L will define precisely:
| Volume | Typical contents |
|---|---|
| I. Technical | Technical approach, management approach, key personnel (sometimes separate volumes) |
| II. Past performance | Recent, relevant contracts; references; questionnaires |
| III. Price / cost | Price schedule (Section B), cost breakdown, assumptions |
| IV. Contract documentation | Signed SF forms, representations and certifications, small business plan, exceptions |
Each volume follows Section L's order and page limits; cross-reference Section M factors in a compliance matrix. See our technical proposal guide.
Outline D: unsolicited or informal proposal
- Cover page (outcome headline)
- Executive summary (the decision on one page)
- The problem (their words)
- Proposed solution
- Scope and deliverables
- Timeline
- Pricing
- Why us (proof)
- Next step
Full guidance and a worked example: how to write a business proposal.
Worked example: building an outline from a fictional RFP
RFP: Ashcombe City (fictional) issues RFP 26-118 for a 311 citizen-request system. It has no response template but states evaluation criteria: Technical solution 35%, Implementation 25%, Experience 20%, Price 20% (separate envelope). Page limit: 30 pages excluding appendices.
| Response section | Driven by | Pages |
|---|---|---|
| Cover letter | Submission instructions | 1 (excluded from limit, per RFP) |
| 1. Executive summary | All criteria | 2 |
| 2. Understanding of Ashcombe's needs | RFP background | 2 |
| 3. Technical solution (sub-sections mirror requirements 4.1–4.9) | Criterion 1, 35% | 11 |
| 4. Implementation plan | Criterion 2, 25% | 7 |
| 5. Experience and references | Criterion 3, 20% | 6 |
| 6. Assumptions and exceptions | Terms | 2 |
| Appendix A: compliance matrix | Requirements 4.1–4.9 | Excluded |
| Appendix B: résumés | Key personnel | Excluded |
| Price proposal | Criterion 4; separate envelope | Separate |
Total: 30 pages. Why it works: page allocation follows weights (11 of 30 pages ≈ 37% for a 35% criterion), section 3 mirrors the RFP's requirement numbers, and price stays separate as instructed.
How Iris helps
Iris is AI software for RFPs, security questionnaires and proposals.
- Outline detected and kept. Question extraction pulls every question and requirement from the full RFP, detects a prescribed outline, keeps the hierarchy and makes each numbered sub-item its own row, checked word for word against the source.
- Criteria up front. The RFP Analyzer lists scoring criteria and requirements, cited to the source, before you start writing.
- Exported in structure. Answers go back into the original file or your branded Word template.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is the best structure for a proposal?
The buyer's prescribed format, if there is one. Otherwise, a structure ordered by the evaluation criteria and their weights, inside a standard frame of cover letter, executive summary and appendices.
What are the main components of a request for proposal?
Background, scope of work, submission instructions, evaluation criteria, questionnaire or response forms, pricing instructions, terms and conditions, timeline and required forms.
Should I change the RFP's order to tell a better story?
No. Tell your story inside their structure, through the executive summary and win themes.
How many pages should each section get?
Roughly in proportion to its evaluation weight, within the page limit.
What goes in the appendices?
Supporting material the instructions allow outside the page limit: résumés, certificates, sample deliverables and the compliance matrix.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
