Proposal outline: the structure evaluators expect

RFP Tips

Author:

Chris Mabry

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

  1. Which outline should you use?
  2. How do RFP components map to response sections?
  3. Outline A: RFP with a prescribed format
  4. Outline B: RFP without a prescribed format
  5. Outline C: US federal multi-volume proposal
  6. Outline D: unsolicited or informal proposal
  7. Worked example: building an outline from a fictional RFP
  8. FAQ

Which outline should you use?

SituationUseWhy
RFP specifies a response format or templateA: mirror itEvaluators score against their own structure
RFP lists evaluation criteria but no formatB: criteria-drivenPuts the highest-weighted content where it's found fastest
Federal solicitation with Sections L and MC: volumes per Section LFormat is part of compliance
No RFP; you're proposing after discoveryD: short sales structureApprovers 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 componentWhat it tells youWhere it goes in your response
Background / introductionThe buyer's context and driversUnderstanding of need
Scope of work / requirementsWhat must be deliveredSolution and approach; compliance matrix
Submission instructionsFormat, order, page limits, volumesYour outline itself
Evaluation criteria and weightsHow you'll be scoredSection order and page allocation
Questionnaire / response formsSpecific questions to answerAnswered in place, in order
Pricing instructions / price formHow to present pricePrice volume or section
Terms and conditionsContract termsExceptions / assumptions section
TimelineDeadlines, Q&A, oralsYour project plan, not the response
Required formsCertifications, signaturesForms section or appendix

Outline A: RFP with a prescribed format

  1. Use the buyer's template file if provided; don't retype it.
  2. Copy headings and numbering exactly, including sub-items such as 3.2.1(a).
  3. Answer in place. Don't move content to "where it fits better."
  4. Add only what the instructions allow: often a cover letter, executive summary and appendices.
  5. Include a compliance matrix if allowed, even when not required, to show where each requirement is answered.

Outline B: RFP without a prescribed format

#SectionContentsPage share (guide)
—Cover page and cover letterIdentification; formal submission—
—Table of contentsMirrors the RFP's requirement numbers where possible—
1Executive summaryNeeds, solution, win themes, value1–2 pages
2Understanding of requirementsThe buyer's goals and constraints in their words~5%
3Solution and approachOrganized by the highest-weighted criterion first~35–45%
4Implementation and timelinePhases, milestones, dependencies~10–15%
5Team and managementKey people, governance, communication~10–15%
6Experience and referencesComparable projects, references~10%
7PricingPer instructions; often separateAs required
8Assumptions and exceptionsClear list~2–5%
—AppendicesRé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:

VolumeTypical contents
I. TechnicalTechnical approach, management approach, key personnel (sometimes separate volumes)
II. Past performanceRecent, relevant contracts; references; questionnaires
III. Price / costPrice schedule (Section B), cost breakdown, assumptions
IV. Contract documentationSigned 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

  1. Cover page (outcome headline)
  2. Executive summary (the decision on one page)
  3. The problem (their words)
  4. Proposed solution
  5. Scope and deliverables
  6. Timeline
  7. Pricing
  8. Why us (proof)
  9. 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 sectionDriven byPages
Cover letterSubmission instructions1 (excluded from limit, per RFP)
1. Executive summaryAll criteria2
2. Understanding of Ashcombe's needsRFP background2
3. Technical solution (sub-sections mirror requirements 4.1–4.9)Criterion 1, 35%11
4. Implementation planCriterion 2, 25%7
5. Experience and referencesCriterion 3, 20%6
6. Assumptions and exceptionsTerms2
Appendix A: compliance matrixRequirements 4.1–4.9Excluded
Appendix B: résumésKey personnelExcluded
Price proposalCriterion 4; separate envelopeSeparate

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.