Loading page content…
Loading page content…
Winning federal proposals is a skill you can learn and sharpen with practice. These 15 tips are drawn from offerors who consistently win competitive awards across federal agencies. They cover everything from reading the RFP to final compliance review — and address the most common mistakes that cost companies points under Section M, or trigger a weakness or deficiency from the evaluation board.
Read the full solicitation — Sections L and M, the SOW or PWS, the FAR/DFARS clauses, and every attachment — at least twice before drafting. Understand the evaluation factors, page limits, mandatory requirements, and submission format. Attempting to write without fully understanding the RFP is the most common and costly mistake offerors make.
Every page should be written to address what the evaluation board is scoring you against. If Section M weighs technical approach, management plan, and past performance, your proposal must give the board a clear strength to find under each. Write for the evaluator, not for your marketing department — and never make them hunt for compliance.
"We are experts in digital transformation" is an assertion. "We delivered a $2.4M cloud migration for the Department of Veterans Affairs in 2023, cutting processing time by 41% and reaching a 93% user adoption rate — rated Exceptional in CPARS" is evidence. Always replace assertions with specific, quantified, verifiable evidence that an evaluator can score as a strength.
For past performance, lead with contracts that match this opportunity in scope, size, and complexity. For each, give the agency, contract number, value, period of performance, and quantified outcomes — and tie back to your CPARS ratings. Recent, highly relevant past performance is what lets the evaluation board rate your confidence high; old or marginally relevant work does not.
Page limits, font size, and margins are strictly enforced — anything past the limit may be removed unread or render your proposal non-responsive. Aim to use 90–100% of the allowance; coming in well under suggests you have not fully addressed the requirement. Every page should earn its place in your evaluation.
Dense walls of text are hard to evaluate and easy to score low. Use clear headings and subheadings that map directly to the Section L instructions and the SOW structure. A compliance matrix that cross-references each requirement to your page numbers makes it effortless for the board to confirm you addressed everything — and that protects your score.
On large or unrestricted procurements, your subcontracting plan and small business participation are evaluated — and weak ones cost real points. Build a genuine plan with specific, measurable commitments tied to the agency's socioeconomic goals: named small business, SDVOSB, WOSB, and HUBZone subcontractors and the percentage of value each will perform under FAR 52.219-9.
Evaluators immediately spot boilerplate recycled from previous proposals. Reference the specific agency, the specific mission, the specific requirement and end users. Show you understand the contracting officer's problem. Generic responses that could fit any solicitation rarely earn more than an Acceptable rating and almost never win a best-value tradeoff.
"Our team will lead transition workshops" is stronger than "Transition workshops will be led by our team." Active language conveys confidence and clarity, and it is more concise — which matters under page limits. Carry consistent win themes through every volume so the board sees a clear, repeated reason to award to you.
Before submission, have colleagues not involved in writing score your volumes against Section M exactly as the evaluation board would — a Red Team review. Anything they would rate below Good, or could flag as a weakness or deficiency, needs to be fixed. A disciplined color-team review is the single most effective quality-assurance step you can take.
Use the questions period. If anything in the RFP is ambiguous — a Section L instruction, an evaluation factor, a technical requirement — submit a written question to the contracting officer. Answers are issued by amendment to all offerors, so you give nothing away, and the response may significantly change how you structure your proposal.
The worst time to write a past performance citation is the night before a deadline on a live proposal. Build your library of past performance write-ups, resumes, capability statements, and reusable technical content continuously. Every contract you finish should add at least one strong, quantified past performance citation to that library.
Keep a compliance checklist: every Section L instruction answered, every required volume and form included, correct format and file naming, all reps and certs current in SAM.gov, and the proposal uploaded before the closing time. Compliance failures after weeks of work are devastating and entirely preventable. Build the checklist before you start writing, not after.
Always request a debrief after the award decision. Under FAR Part 15 you are entitled to one, and the contracting officer's feedback — strengths, weaknesses, and how your proposal was evaluated — is the most valuable input you can get for the next pursuit. Track recurring themes across debriefs to find your systematic weaknesses and invest in fixing them.
AI proposal tools like GovCon can cut the time spent on first drafts by up to 90%, freeing experienced writers to focus on review, win strategy, and quality rather than typing. Use technology to give yourself more time for the things that truly differentiate a winning proposal — the strategy, the evidence, and the final compliance and color-team review.
Write better proposals with AI
GovCon helps federal contractors write stronger proposals, track deadlines, and win more awards. Entry plan available.
Start free →