Skip to content

Handbook 3Chapter 3 of 8

Proposal Format, Structure and Compliance

How to organize, format and package a proposal so evaluators can find every answer, and so it is never rejected on a technicality.

16 min readUpdated All levels

Key takeaways

  • Organize the proposal exactly as the solicitation's instructions require, with its numbering and headings, even if you would have chosen a different order.
  • Treat page limits, fonts, margins and file rules as pass/fail. Agencies may refuse to read pages past the limit.
  • Write to the evaluation criteria: echo their language, spend pages in proportion to their weight and make strengths easy to find.
  • Use headings, short paragraphs and graphics with action captions so a skimming evaluator still gets your message.
  • Run a final compliance review before you submit. A compliant, plain proposal beats a brilliant one that breaks the rules.

Proposal format and structure decide whether evaluators can find your answers, and sometimes whether they read your proposal at all. A strong solution in the wrong order, over the page limit or missing a signed form can be marked noncompliant before anyone scores it. This chapter shows you how to structure an RFP response that mirrors the solicitation, follows every formatting rule, includes every required form and passes a final compliance review.

It builds on the compliance matrix from How to Read and Shred an RFP. If you have not shredded the solicitation yet, start there: every outline decision below comes from it.

Proposal structure: build an outline that mirrors the solicitation

Evaluators score against a checklist built from the evaluation criteria, often across many proposals. Make their job easy: use the solicitation's structure, numbering and words. If the instructions list five items for the technical volume in a set order, your technical volume has five sections, in that order, with those names.

How to build a mirrored outline
  1. Step 1: Start from the instructions

    Use Section L (or the RFP's submission requirements) as the skeleton: volumes, tabs, sections and their order. If the instructions say 'Tab 3: Staffing Plan', your third tab is 'Staffing Plan'.

  2. Step 2: Layer in the evaluation criteria

    Give every evaluation factor and subfactor a heading. If a factor is scored but missing from the instructions, add a subsection where an evaluator would look for it.

  3. Step 3: Slot in the scope requirements

    Place each scope row from your compliance matrix under the heading where it fits. Rows with no home reveal a missing subsection.

  4. Step 4: Number like the solicitation

    Reuse the RFP's numbering or show it in the heading, for example '2.1 Preventive Maintenance Program (RFP §4.2.1)'.

  5. Step 5: Assign page budgets and owners

    Give each section a page allowance and one writer before drafting (see the page budget example).

Weak exampleWeak outline

1. About Us. 2. Our Services. 3. Why Choose Us. 4. Our Team. 5. Pricing. The order follows the company brochure, so evaluators must hunt for the transition plan and quality control approach the RFP asked for, and may not find them.

Strong exampleStrong outline

Volume I, Technical. 1. Understanding of Requirements (RFP §4.1). 2. Technical Approach (§4.2): 2.1 Preventive Maintenance; 2.2 Emergency Response; 2.3 Reporting. 3. Transition Plan (§4.3). 4. Quality Control Plan (§4.4). 5. Key Personnel (§4.5). Every heading matches an instruction and an evaluation factor.

Proposal format rules: what font, margins and page limits should you use?

Formatting rules are requirements, not style suggestions; agencies set them so proposals compete on equal terms. Federal bid protest decisions have upheld agencies that declined to evaluate pages beyond a limit and that found proposals noncompliant for using smaller type than allowed. Whether the whole proposal can be rejected, rather than just the excess pages, depends on the solicitation's wording.

Formatting rules to find and follow (what solicitations commonly specify)
Formatting rules to find and follow (what solicitations commonly specify)
RuleCommon wordingWatch out for
Page limitA maximum per volume or section, such as 25 or 50 pagesWhat counts: covers, contents pages, résumés, tabs and letters may or may not be excluded
Page size8.5 x 11 inches; 11 x 17 foldouts sometimes allowedFoldouts often count as two pages
Font12-point body text, sometimes a named typefaceSmaller type allowed only in tables, graphics and captions, with a stated minimum
Margins and spacing1-inch margins, single spacingHeaders and footers that intrude into the margin
VolumesSeparate technical and price volumesPrice details in the technical volume when forbidden
Copies and mediaOriginals and copies, or one searchable PDF per volumeSigned originals, size limits, password-protected files

Required forms, certifications and signatures

Forms are where good proposals die quietly. A missing signature, an unacknowledged amendment or an unnotarized affidavit can make an offer nonresponsive however strong the technical volume is. Put every form in your compliance matrix with an owner, and start first on those that need third parties: insurers, notaries, sureties and subcontractors.

Forms you are likely to meet (examples only; each solicitation lists its exact set)
Forms you are likely to meet (examples only; each solicitation lists its exact set)
IssuerCommon forms and certifications
FederalThe cover form (SF 33, or SF 1449 for commercial buys) signed by an authorized person; amendment acknowledgments (often on SF 30); representations and certifications in Section K or confirmed through your federal entity registration; a small business subcontracting plan when required
New York StateVendor Responsibility Questionnaire; procurement lobbying affirmation and disclosure forms; MWBE utilization plan and EEO staffing plan where goals apply; Form ST-220-CA sales tax certification, notarized, for covered contracts over $100,000
New York CityQuestionnaires and documents completed in PASSPort, plus agency forms such as addenda acknowledgments and M/WBE participation documents
New Jersey (state)Offer and Acceptance Page, Ownership Disclosure, Disclosure of Investment Activities in Iran, Disclosure of Investigations, Source Disclosure (services) and a Subcontractor Utilization Plan if you use subcontractors; a Business Registration Certificate before award
ConnecticutNondiscrimination, ethics and campaign contribution certifications named in the solicitation
Most issuersSigned cover letter, insurance certificates, bid bond for many construction bids, W-9, licenses and certification letters
Signature and forms check0 of 8 done

The cross-reference matrix: show evaluators where everything is

A cross-reference matrix is a table, usually right after the table of contents, that maps solicitation requirements to the pages where you answer them. Some RFPs require one. If yours does not, include it when space allows, or ask whether it counts toward the page limit. Evaluators who can find your answers can score them.

Sample cross-reference matrix (illustrative)
Sample cross-reference matrix (illustrative)
Solicitation referenceRequirementEvaluation factorProposal sectionPage
§4.2.1; Exh. A §3.1Preventive maintenance programM.2 Technical approachVol. I, 2.16
§4.2.2; Exh. A §3.4Emergency response within 2 hours, 24/7M.2 Technical approachVol. I, 2.29
§4.3Transition plan for the first 30 daysM.3 ManagementVol. I, 313
§4.5Key personnel résumésM.3 ManagementVol. I, App. AA-1
§4.6Three past performance referencesM.4 Past performanceVol. II, 11
§6.1; Amendment 2Price form, Attachment F (revised)M.5 PriceVol. III, Tab 24

Keep the internal compliance matrix and this submitted matrix in sync. The internal one holds owners, status and notes; the submitted one holds only what helps the evaluator. Fill in page numbers after final layout, not before.

Write to the evaluation criteria

In a best-value procurement, evaluators read your proposal against each factor and record strengths, weaknesses and deficiencies. Your job is to make strengths easy to find and hard to miss. Three habits help:

  • Echo the criteria's language. If the factor is 'feasibility of the transition approach', use the word feasibility and show it: tasks, dates, named people, risks and mitigations.
  • Spend pages where the points are. After reserving space for anything mandatory, split your page budget roughly in proportion to the factor weights.
  • State the benefit and prove it. Do not make evaluators infer why a feature matters (see feature, benefit, proof).
Example page budget: 25-page technical volume (price, worth 10 more points, is scored separately)
Example page budget: 25-page technical volume (price, worth 10 more points, is scored separately)
SectionWeightPagesNotes
Executive summaryNot scored separately1Keep it inside the limit unless the RFP excludes it
Understanding of requirements10 points2Show the agency's problem; do not restate the scope
Technical approach40 points11The heart of the volume and home of the key graphics
Management and transition25 points7Org chart, transition timeline, quality control
Key personnel15 points4Summaries here; full résumés in an appendix if excluded from the limit
Answering a requirement (illustrative)

Strong: shows how, with proof

  • Do: 'We meet the 2-hour emergency standard by dispatching from our Yonkers depot, 15 minutes from the county center, with an on-call technician for each zone (Figure 2-2).'
  • Do: 'Quality control has three checks: technician self-inspection, a supervisor spot-check of 10% of work orders, and a monthly report to the County (Section 4.1).'

Weak: restates the requirement

  • Don't: 'We will respond to all emergencies within 2 hours as required.'
  • Don't: 'We are committed to quality and will implement a robust quality control plan.'

Readability, headings and graphics with action captions

Some evaluators read every word; senior decision makers often skim. Write for both. Use headings that echo the requirement, open each section with a short theme statement, keep paragraphs to two to four sentences and put the main point first. Plain language is not dumbing down: short sentences, active voice and common words make a proposal faster to evaluate.

Graphics earn their space when they show something faster than text: a transition timeline, an org chart with named people, a process flow, a map of response zones. Give every graphic a number, a title and an action caption: one or two sentences telling the reader what to conclude and why it matters to them.

Weak exampleWeak caption

'Figure 3. Organizational chart.' It labels the picture but tells the evaluator nothing.

Strong exampleStrong action caption

'Figure 3-1. One accountable manager and three zone supervisors: every County building has a named supervisor reachable directly, 24/7, so issues never wait in a general queue.'

  • Mention each graphic in the text before it appears, and place it close by.
  • One idea per graphic; if it needs a paragraph of explanation, simplify it.
  • Keep text inside graphics at or above the solicitation's minimum type size.
  • Number figures by section (Figure 2-1, 2-2) so cross-references stay stable.
  • Use real names, numbers and places; stock images add nothing.
  • Check that charts read clearly in black and white and do not rely on color alone.

For graphics inside the technical volume, such as work plans, staffing charts and transition timelines, see graphics and action captions.

File naming, file formats and portal submission

Most public proposals are now submitted electronically, through an agency portal or by email, and electronic submission has its own compliance rules: file names, formats, size limits, file counts and proof of receipt. Upload-day timing and the late-is-late rule are covered in submission logistics.

Portal and file rules to confirm
Portal and file rules to confirm
ItemWhat to check
File namesAny required convention; otherwise include the solicitation number, volume and company name
File formatUsually searchable PDF for narrative and spreadsheet files for price workbooks
Size and count limitsMaximum size per upload or email; split volumes only as instructed
SignaturesWhether electronic signatures are accepted or wet-ink originals are needed
Portal setupAccount roles and any prequalification needed before you can submit
ConfirmationWhat receipt the portal gives and whether you can revise after submitting

Two tri-state examples. New York City's PASSPort guidance suggests naming uploads with the section and question number, document name and legal business name (such as S2Q3_OrgChart_YourLegalName), and a submitted response cannot be edited; while the RFx is still open, you can duplicate it, revise and resubmit, then withdraw the original. New Jersey's state purchasing division expects quotes in NJSTART with all required forms attached. Read each solicitation's own instructions, because rules vary and change.

Submission-day routine
  1. Step 1: Rehearse the upload

    Log in days ahead, confirm your account roles and try a test upload if the portal allows drafts.

  2. Step 2: Finish a day early

    Federal rules generally treat a late electronic proposal as late unless it reached the government by 5:00 p.m. one working day before the due date (among narrow exceptions), and many state and local issuers allow no exceptions.

  3. Step 3: Open what you upload

    Open each final file from the submission folder: page counts, embedded fonts, signatures.

  4. Step 4: Keep the receipt

    Save the confirmation, screenshot or receipt number with its time stamp.

Final proposal compliance checklist

Run this review after final layout, with someone who did not write the proposal holding the compliance matrix. It is separate from the quality reviews known as color teams: those ask whether the proposal persuades; this asks whether it is complete and compliant. Delivery itself is covered in submission logistics.

Final compliance review (print and initial each line)0 of 13 done

Printable versions of this and other bid checklists are in bid management templates and checklists.

Why compliant-but-dull beats brilliant-but-noncompliant

Evaluators are bound by the solicitation. They generally cannot credit an answer that is not where they were told to look, read pages past the limit or accept an unsigned offer, however strong the content. A noncompliant proposal may be rejected or marked down; a compliant one at least gets read, scored and compared.

Dull is not the goal, though. Compliance is the floor and persuasion is the ceiling, and the order of work matters:

Compliant, then responsive, then persuasive
  1. Stage 1: Compliant

    Follows every instruction: structure, format, forms, deadline.

  2. Stage 2: Responsive

    Answers every requirement with a specific how.

  3. Stage 3: Persuasive

    Shows the customer benefit, proves it and stands apart from competitors.

A proposal that skips the first step rarely gets the chance to benefit from the third. For the persuasive layer, continue with the executive summary and technical and management approach chapters.

Frequently asked questions

How should I format a proposal for an RFP?

Follow the solicitation's instructions exactly: its volumes, section order, headings, page limits, font, margins and file rules. Where the RFP is silent, use a clean, readable layout: 8.5 x 11 pages, a standard 11- or 12-point font, one-inch margins, numbered headings that echo the requirements, a table of contents, a cross-reference matrix and numbered figures with action captions.

What font and size should a government proposal use?

Use whatever the solicitation specifies; many federal and state RFPs require 12-point type for body text and allow smaller type only in tables and graphics, down to a stated minimum. If no font is named, choose a common, readable typeface and stay at 11 or 12 points. Never shrink type to fit a page limit.

Do cover pages and tables of contents count toward the page limit?

Only if the solicitation says so, or fails to exclude them. Many RFPs exclude covers, tables of contents, tabs and résumés, but some count everything. If the instructions are unclear, ask during the question period, and until you get an answer, assume they count.

What happens if my proposal goes over the page limit?

Usually the evaluators stop reading at the limit, so anything after it is not evaluated, and some solicitations allow the whole proposal to be rejected. Federal bid protest decisions have generally upheld agencies that refused to evaluate excess pages when the solicitation warned they would. Cut content until you are inside the limit.

What is a cross-reference matrix in a proposal?

A cross-reference matrix is a table, usually placed after the table of contents, mapping each solicitation requirement and evaluation factor to the section and page where your proposal answers it. It helps evaluators find and score your answers. Some RFPs require it; it is built from your internal compliance matrix without the owners and notes.

Can I submit my proposal after the deadline if the portal fails?

Don't count on it. Federal rules allow late proposals only in narrow cases, such as an electronic proposal that reached the government's initial point of entry by 5:00 p.m. one working day before the due date, and many state and local issuers allow no exceptions. Submit at least a day early and keep your receipt.

Should I include brochures or marketing material?

Generally no, unless the solicitation asks for product literature. Glossy brochures count toward page limits, rarely answer the stated requirements and can make a proposal look generic. Put the specific facts evaluators need into the sections that ask for them.

Complete handbook

Download the complete handbook (PDF)

All 8 chapters, templates and checklists, ready to print or share.

Put it into practice

Search open RFPs from federal, state, local, education, private and non-profit issuers, each with the RFP Detector Score.

Find RFPs

Free handbooks

Keep learning

All guides and templates