Write answers that show how
Stop repeating the requirement back to the buyer. Answer first, then show the method, the people, the timing and the proof.
On this page
Many proposals fail for the same reason: they repeat the requirement and promise to do it. "The contractor shall provide help desk support." "We will provide help desk support." That tells the evaluator nothing.
Answer first, then show how
Answer the requirement in your first sentence. Then explain how:
- Method: the steps you will follow.
- People: who does each step, by role.
- Tools: the systems or equipment you will use.
- Timing: what happens first, and when.
- Proof: a similar job, a result or a credential.
- Risk: what could go wrong, and what you will do about it.
Weak: "We will comply with all help desk requirements."
Strong: "Two certified technicians will answer calls from 7:00 a.m. to 6:00 p.m. Central. Each ticket goes into the agency's ticket system within five minutes. We close password resets in under 30 minutes, as we do today for a 400-person clinic network."
Never answer with "we will comply", "we understand" or "we attest".
Improve the offer, not the words
Better adjectives do not win. A better offer can. Look for real improvements: faster delivery, fewer handoffs, a lower-risk method, or a tool that saves the buyer time. Then say why it matters to this buyer.
Plan for what could go wrong
Think about the real risks of the job: a key person leaves, a shipment is late, a system goes down. Write how you will handle each one into your approach. Promise only what you can do, because once you win, what you wrote becomes part of what you owe.
Write as if you already won
Describe day one: who shows up, what happens first and in what order. Use real roles. It helps the evaluator picture you doing the work.
Make it easy to score
- Use the buyer's headings and numbering, in their order.
- Put each answer where the evaluator expects to find it.
- Use short paragraphs, lists and tables.
- Add at least one table or figure to each major section. A schedule, a staffing table or a process diagram can say more than a page of text.
- Keep important facts in text, not only inside images.
- Stop when you have answered. Extra words dilute strong ones.
Truth rules
- Every fact comes from your own records or from the solicitation.
- Every number about your performance must be one you can defend.
- If you will hire for the job, say so as a firm plan with named roles. Never describe people you have not hired as current staff.
- Never hide a limitation that the buyer requires you to state.
About AI tools
AI can help you draft, but it returns text only. A person must check every fact, add the tables and figures, and rewrite it in your own voice. Never paste sensitive or nonpublic information into a public AI tool, and check whether the solicitation limits AI use or asks you to disclose it.
Idea credit: GovKidMethod, "What NOBODY TELLS YOU About Writing Winning Government Proposals" (watch on YouTube(opens in a new tab)). Victavio is not affiliated with this channel.
Idea credit: Melanie Patterson with Maria Cassidy, Inside the Bid, "What Really Gets Your Federal Proposal Rejected?" (watch on YouTube(opens in a new tab)). Victavio is not affiliated with this channel.
Sources
- FAR 15.305: Proposal evaluation(opens in a new tab)
- FAR 52.212-2: Evaluation, commercial products and commercial services(opens in a new tab)
- FAR Part 15: Contracting by negotiation(opens in a new tab)
This lesson is general information, not legal advice. Rules change. Check the official source before you act.
Find bids that fit you
Victavio checks SAM.gov every day, adds Texas state bids from the ESBD, and scores each bid for your business.
Start free