Module 11

Proposal Writing Basics

Learn how to write a proposal that is compliant, specific, and easy to evaluate.

2 lessons3 min read

Beginner Summary

This topic matters because proposals are evaluated against instructions and criteria, not general marketing appeal.

Module Overview

This topic matters because proposals are evaluated against instructions and criteria, not general marketing appeal.

By the end of this module, learners should be able to explain the topic in plain English and apply it to a real opportunity or business decision.

Lesson 1

A Proposal Is a Structured Proof Package

A government proposal is not just a sales pitch. It is a structured proof package. It should show that the contractor understands the requirement, followed the instructions, can perform the work, offers a fair price, and reduces government risk.

A proposal should be organized according to the solicitation instructions and written to the evaluation criteria. The evaluator should be able to find and score every required answer.

Why This Matters

A proposal does not need to sound fancy. It needs to be compliant, specific, credible, and easy for evaluators to score.

How This Works in Practice

Weak: “We are committed to quality.” Strong: “The site supervisor completes a daily inspection checklist, the project manager performs weekly random inspections, and deficiencies are logged with corrective action due within 24 hours.”

Reality Check

A proposal does not win because it sounds impressive. It wins when evaluators can easily find proof that the offer is compliant, low-risk, aligned to the evaluation factors, and fairly priced.

Key Takeaways

Write to be evaluated, not to sound impressive.
Use the solicitation as the outline source.
Evidence beats adjectives.
Compliance comes before creativity.

Common Mistakes

Starting with a company brochure.
Using vague claims like “excellent service.”
Ignoring page limits or file instructions.
Failing to clearly answer evaluation factors.

Practical Checklist

Build a compliance matrix.
Build a proposal outline from Section L.
Map content to Section M evaluation criteria.
Use specific processes, resources, proof, and risk controls.
Perform a final compliance check.
Write to the solicitation’s structure.
Use evidence instead of adjectives.
Make evaluator scoring easy.
Perform a final compliance review before submission.

Mini Quiz

Why is evidence better than adjectives?

Because evaluators can score evidence; vague adjectives do not prove performance capability.

Lesson 2

Technical, Management, Past Performance, and Price Volumes

A technical volume explains how the contractor will perform the work. A management volume explains how the contractor will control staffing, schedule, quality, communication, risk, and subcontractors. A past performance volume proves similar work. A price volume shows what the government will pay and how price is structured.

The technical approach and price must match. If the proposal promises a full-time project manager, quality inspections, reports, and backup coverage, the price should include the resources needed to do those things.

Why This Matters

A proposal does not need to sound fancy. It needs to be compliant, specific, credible, and easy for evaluators to score.

How This Works in Practice

Example: A contractor proposes 24/7 response, backup staff, weekly reporting, and quality inspections. The price includes only one worker and no supervision. The government may question realism and understanding.

Reality Check

If the technical volume promises resources the price does not support, the government may see risk. If the price is low because you forgot supervision, reporting, travel, or fringe, the win can become a loss.

Key Takeaways

Technical approach explains how the work will be done.
Management approach explains how performance will be controlled.
Past performance proves credibility.
Price must support the proposed approach.

Common Mistakes

Promising resources not included in price.
Using generic management language.
Submitting weak or unrelated past performance.
Ignoring final forms and signatures.

Practical Checklist

Use the formula: Requirement, approach, resources, proof, risk control, result.
Describe staffing and communication clearly.
Use relevant past performance examples.
Check price/technical consistency.
Submit exactly as instructed.
Write to the solicitation’s structure.
Use evidence instead of adjectives.
Make evaluator scoring easy.
Perform a final compliance review before submission.

Mini Quiz

What happens if technical promises and price do not match?

The government may doubt that the contractor understands the work or can perform the promised approach.

Key Terms

Compliance matrixRequirement matrixTechnical volumeManagement volumePast performance volumePrice volumeWin themeQuality control plan

Action Steps

Build a compliance matrix.
Build a proposal outline from Section L.
Map content to Section M evaluation criteria.
Use specific processes, resources, proof, and risk controls.
Perform a final compliance check.
Write to the solicitation’s structure.
Use evidence instead of adjectives.
Make evaluator scoring easy.

Important Cautions

Starting with a company brochure.
Using vague claims like “excellent service.”
Ignoring page limits or file instructions.
Failing to clearly answer evaluation factors.
Promising resources not included in price.
Using generic management language.
Submitting weak or unrelated past performance.
Ignoring final forms and signatures.