How to Write a Government Proposal (The Complete Guide)

Writing a government proposal is a discipline, not a writing exercise. The best-written narrative loses if it misses a Section L instruction or fails to address a Section M evaluation factor. This guide walks the full lifecycle of responding to a federal, state, or local solicitation — from deciding whether to bid through submission and debrief — so a small team can compete on quality against firms many times its size.

If your framing is more “RFP response” than “proposal from scratch,” the companion guide on how to respond to a government RFP covers the same ground from the solicitation-in-hand angle.

1. Decide whether to bid

Every hour spent on a proposal you can’t win is an hour stolen from one you can. Before writing a word, make a deliberate bid/no-bid decision.

• Read the cover sheet first: agency, contract vehicle, NAICS code, set-aside type, and period of performance tell you in minutes whether you’re even eligible.
• Use Sections L and M as a go/no-go signal. If Section M’s evaluation factors reward past performance you don’t have, that’s a strong no-bid signal. See what Section L and Section M are for how to read them.
• Weigh fit, competition, incumbency, and cost-to-pursue against your realistic win probability.

A structured bid/no-bid decision protects your calendar and your win rate at the same time.

2. Build the compliance matrix

Once you commit to bidding, your first artifact is a compliance matrix — a table listing every requirement in the solicitation and where your response addresses it. This is the backbone of a compliant proposal.

1. Extract every instruction from Section L (how to prepare and submit).
2. Extract every evaluation factor from Section M (how you’ll be scored).
3. Extract the technical requirements from the Section C statement of work.
4. List each as a row with a source reference, an owner, and a status.

This decomposition step is called RFP shredding, and it’s the single best defense against a “non-responsive” rejection. You can build one in seconds with the free compliance matrix generator, or read the deeper explainer on what a compliance matrix is.

3. Draft the technical response

With the matrix in hand, draft to the evaluation — not to your solution.

• Structure around evaluation factors, not around how your product happens to work. Evaluators score against Section M; make it trivial for them to find each factor.
• Write to a technical evaluator, not a marketer. Government evaluators reward evidence and specificity over adjectives. Show how, not just that.
• Avoid the common failure modes: telling instead of showing, burying the evidence, and answering the requirement you wish you’d been asked instead of the one on the page.

This is where an AI proposal generator earns its keep: it removes the blank-page problem by drafting each section against the requirements, so your experts spend their time refining substance instead of generating boilerplate.

4. Past performance and personnel

Past performance is frequently the highest-weighted non-price factor in Section M.

• Select relevant references under the FAR 15.305 factors — relevance, recency, and quality of prior work of similar size and scope.
• Write past-performance narratives that map to the evaluation, drawing an explicit line from what you did before to what this agency needs now.
• Format resumes to survive page limits. Lead with the qualifications the solicitation asks for; cut everything that doesn’t map to a requirement.

For architect-engineer work, this is captured on the SF330 form — see how to fill out an SF330.

5. Pricing and the cost narrative

Your price volume has to be defensible and internally consistent with the technical volume.

• Build the price around your technical assumptions — the labor mix and level of effort in the cost volume must match the approach you described.
• Write a clear basis of estimate. Evaluators and auditors need to trace every number to a rationale.
• Watch the realism trap: a price that’s too low reads as a misunderstanding of scope; too high reads as poor value. Both cost points on Section M.

6. Review cycles: pink, red, and gold teams

Government proposals are refined through color-team reviews, each with a distinct job.

• Pink team reviews an early draft for approach and structure — are you answering the right questions?
• Red team reviews a near-final draft as an evaluator would, scoring against Section M.
• Gold team is the final executive sign-off before production.

Running these well — even on a compressed timeline — is what separates a compliant proposal from a winning one. See the full breakdown of pink, red, and gold team reviews. A technical writer review pass catches compliance drift between color teams.

7. Production and submission

Formatting is a compliance requirement, not a cosmetic one.

• Enforce the format rules from Section L: page counts, fonts, margins, and section numbering. Exceeding a page limit can get pages discarded unread.
• Meet Section 508 accessibility requirements for federal submissions.
• Deliver correctly: SAM.gov, an agency portal, or physical delivery — each with its own deadline mechanics. A submission that’s one minute late is simply not evaluated.

8. After submission

The work isn’t done at submission.

• Request a debrief, win or lose. Agencies are often required to provide one, and it’s the cheapest market research you’ll ever get.
• Turn losses into lessons. Feed debrief findings back into your next bid/no-bid decision and your reusable content library.

Understanding why government proposals get rejected closes the loop — most rejections trace back to a compliance gap that a matrix and a disciplined review would have caught.

The through-line: compliance is the game. A matrix keeps you responsive, evaluation-focused drafting keeps you competitive, and disciplined reviews keep you winning. GovHub is built to run this entire workflow — from shredding the solicitation to a submission-ready package. See how it works or start a free trial.