How to Write a Winning Government Proposal: Step-by-Step Guide

TL;DR: Government proposals are scored against strict criteria — miss a requirement and you're eliminated before anyone reads your approach. This guide covers the fundamentals for Canada and the US. Browse open tenders to find opportunities worth bidding on.

Writing a government proposal is different from responding to private-sector RFPs. Government evaluators follow strict scoring criteria. If you miss a requirement, your proposal can be eliminated before anyone reads your technical approach.

This guide covers the fundamentals of responding to government RFPs in Canada and the United States.

Step 1: Read the Entire Solicitation First

Government RFPs often run 50-200+ pages. Before you start writing, read the entire document. Look for:

• Evaluation criteria and weights — This tells you exactly what the evaluator cares about. If technical approach is worth 40% and price is 30%, spend proportionally more effort on your technical narrative.
• Mandatory requirements — These are pass/fail. If you can't meet a mandatory requirement, don't bid. You'll waste time and money on a proposal that will be disqualified.
• Submission format instructions — Page limits, font size, file format, naming conventions. Ignoring these is the fastest way to get disqualified.
• Questions deadline — Most solicitations have a Q&A period. Ask questions to clarify ambiguous requirements. The answers (published to all bidders) often reveal what the agency actually wants.

Step 2: Build a Compliance Matrix

A compliance matrix maps every requirement in the RFP to where you address it in your proposal. This is the single most important tool for government proposal writing.

Create a spreadsheet with columns:

If any row shows "No" or "Partial," you need to address it before submitting — either by finding a solution, partnering with someone who has the capability, or deciding not to bid.

Step 3: Write the Technical Approach

Your technical approach should:

1. Restate the problem. Show you understand what the agency needs, not just what they asked for. This demonstrates insight.

2. Describe your solution specifically. Don't write generic marketing copy. Describe exactly how you'll deliver the work, with timelines, milestones, and resource allocation.

3. Address every evaluation criterion. Use the same language the RFP uses. If they say "demonstrate experience with cloud migration," use the phrase "cloud migration" in your response — don't just say "we move systems to AWS."

4. Include past performance. Reference specific projects with measurable outcomes. "Migrated 3 federal agencies to AWS GovCloud, reducing hosting costs by 40% over 18 months" is better than "extensive cloud experience."

5. Name your team. Government evaluators want to know who will actually do the work. Include resumes or bios of key personnel with relevant experience.

Step 4: Pricing Strategy

Government pricing follows specific rules depending on the contract type:

• Firm Fixed Price (FFP) — You quote a total price. If it costs more, you absorb the loss. Price to win, but don't lowball — agencies are wary of unrealistically low bids.
• Time and Materials (T&M) — You quote hourly rates. The agency pays actual hours worked. Common for IT services and consulting.
• Cost Reimbursement — Used for R&D and complex projects. You're reimbursed for allowable costs plus a fee.

For most small business IT contracts, you'll see FFP or T&M. Research the agency's historical spending (available on USAspending.gov for US contracts) to calibrate your pricing.

Step 5: Review and Submit

Before submitting:

• Every mandatory requirement is addressed
• Page limits are respected
• Pricing is complete and formatted correctly
• All required forms are included (e.g., SF-330 for US A&E services)
• File names match the required convention
• Someone who didn't write the proposal has reviewed it for clarity
• You're submitting before the deadline (not at the deadline)

Common Mistakes That Kill Government Proposals

1. Missing mandatory requirements. An otherwise excellent proposal gets rejected because you forgot to include proof of insurance.

2. Generic responses. Saying "we have 20 years of experience" without specifics. Evaluators want concrete examples with measurable results.

3. Ignoring page limits. If the RFP says 25 pages, evaluators may literally not read page 26.

4. Late submission. There is no grace period. If the portal closes at 2:00 PM and you submit at 2:01 PM, your proposal is rejected. Plan to submit 24-48 hours early.

5. Not asking questions. If something is ambiguous, ask during the Q&A period. Guessing wrong is worse than asking.

Further Reading

• Browse government tenders — Find contracts worth bidding on
• How to Find Government Contracts in Canada — Complete guide to procurement sources