A federal RFP response is not a sales document. It is an evaluation instrument. Every section, every word, and every formatting decision is read by a team of evaluators against a pre-established scoring rubric. Firms that understand this write proposals that score points. Firms that do not write proposals that explain why they are good at their jobs, which is not the same thing.

This framework covers the structure of a compliant federal proposal response, what belongs in each section, and the formatting and compliance requirements that evaluators use as a first screen before reading a word of substance.

Read the RFP before you write anything

This sounds obvious. It is not universally practiced. The RFP contains your instructions. Section L tells you what to submit. Section M tells you how it will be evaluated. The Statement of Work or Performance Work Statement tells you what the government actually wants to buy. Sections H and I contain clauses and requirements that impose additional obligations.

Before writing, create a compliance matrix. List every requirement from Sections L and M in a spreadsheet. Note the page limit, font size, file format, submission method, and evaluation weight for each section. This matrix becomes your checklist and your writing outline simultaneously.

As described in the companion article on how to read an RFP in 30 minutes, the hidden disqualifiers are often outside Sections L and M. Review the entire document before concluding that you understand the full requirement.

Executive summary

The executive summary is not a cover letter. It is a condensed version of your entire proposal, written for a reader who may not read anything else. Many source selection officials read the executive summary before the detailed sections. In some acquisitions, a summary-level review determines which firms advance to full technical evaluation.

An effective executive summary covers four things. First, it restates the government's requirement in your words, demonstrating that you understand what is being bought. Second, it states clearly who your team is and why you are the right choice. Third, it identifies two or three specific differentiators that distinguish your approach from alternatives. Fourth, it confirms your compliance with all material requirements.

Keep the executive summary to one page if the RFP does not specify a limit. It is a summary, not a prologue.

Technical approach

The technical approach is where you explain how you will do the work. This is typically the highest-weighted evaluation factor in competitive proposals, and it is where most firms write the weakest material.

The mistake is writing about capability rather than approach. "Our team has extensive experience in program management" is a capability statement. "We will use an integrated master schedule updated weekly and distributed to the COR every Friday by 5 PM" is a technical approach. Evaluators are scoring your approach. Give them something to score.

Structure your technical approach to mirror the RFP's structure exactly. If the RFP organizes the requirements into five functional areas, your technical approach should have five corresponding sections, numbered identically to the RFP. Evaluators working through your proposal section by section should never have to search for your response to a specific requirement.

For each task or functional area, address: your understanding of the requirement, your specific approach to performing it, your methodology and tools, your timeline and milestones, your quality control process, and any risks you have identified and how you will mitigate them.

Management approach and staffing

This section describes how your team is organized and how you will manage the contract. Include an organizational chart that shows the reporting structure clearly. Identify key personnel by name when the RFP requires it, and provide credentials that directly support the evaluation criteria.

For key personnel sections, do not provide generic resumes. Tailor each resume to address the specific qualifications listed in the RFP. If the RFP requires a program manager with 10 years of federal IT experience and a PMP certification, your program manager's resume should prominently feature those qualifications within the first half-page.

If you are using subcontractors, identify them by name, describe their role and qualifications, and explain how the teaming arrangement enhances your ability to perform the work. An effective teaming narrative explains why this team was assembled for this opportunity, not just that you have partners.

Past performance

Past performance is evaluated on two dimensions: relevance and quality. Relevance means similarity to the current requirement in scope, complexity, dollar value, and technical area. Quality means the assessment your prior clients gave you, typically through CPARS ratings or references.

For each past performance example, provide the contract name, contracting agency, contract number, contract type, dollar value, period of performance, your role (prime or subcontractor), a description of the work performed, and the name and contact information for a program-level reference. Do not list just the contracting officer. List the person who actually worked with your team.

Select examples based on their relevance to the current requirement, not their size or prestige. A $500,000 task order that closely parallels the current work is more compelling to evaluators than a $50 million contract in an unrelated area.

Pricing volume

The pricing volume is evaluated separately from the technical volume in most acquisitions. For cost-plus contracts, the government will audit your cost estimates and compare them to forward pricing rate agreements or cost analysis benchmarks. For fixed-price contracts, your total price is compared to other offerors and to the government's independent cost estimate.

Build your pricing from the ground up using a work breakdown structure. Price every deliverable, every labor category, every period of performance. Do not pad the estimate to protect margin and do not cut the estimate to win if you cannot perform at the proposed price. Both errors create problems during performance.

Present your pricing in the format the RFP specifies. If the RFP includes a pricing spreadsheet template, use it exactly. Do not modify the template or substitute a different format. Non-compliant pricing volumes are returned without evaluation in many acquisitions.

Compliance and representations

The representations and certifications required in federal proposals cover a wide range of legal and regulatory obligations. These include your business size certification, your SDVOSB status, your SAM.gov registration, your compliance with labor laws, your compliance with cybersecurity requirements, and various other regulatory certifications.

Most representations and certifications are submitted through SAM.gov during registration and updated annually. However, some proposal-specific certifications must be included in the proposal itself. Review Section K of the RFP carefully for any certifications that require a specific response within the proposal document.

Formatting and compliance requirements

Formatting requirements in federal RFPs are not suggestions. They are compliance criteria. Proposals that exceed page limits may be truncated at the specified page. Proposals submitted in the wrong file format may be rejected. Proposals with fonts or margins that differ from specifications may be returned.

Common formatting specifications include page limits per section, minimum font size (typically 11 or 12 point), minimum margin size (typically 1 inch), single or double spacing requirements, specific file formats for electronic submission, and specific naming conventions for submitted files.

Create a formatting compliance checklist from the RFP instructions and verify your proposal against it before submission. Have a second person conduct this check independently.

Submission and confirmation

Federal proposals are submitted electronically through specified portals, most commonly SAM.gov or a designated agency portal. Submit at least 24 hours before the deadline, not in the final hour. Portal congestion, system outages, and user errors are common near deadlines. Late proposals are generally rejected without consideration, regardless of cause.

After submission, obtain and retain written confirmation. Most portals generate a submission confirmation email or a confirmation number. Keep this as your proof of timely submission.

After submission

Once your proposal is submitted, the government's evaluation process begins. Oral presentations, discussions, and best and final offers are all possible next steps depending on the acquisition type. If discussions are opened, the contracting officer will provide written questions or concerns. Respond to every point raised in discussions, completely and directly.

Whether you win or lose, request a debrief. As described in the companion article on post-award debriefs, a debrief is the only structured opportunity to get evaluator feedback on your proposal. Use it.