The short version: decide whether to bid, read the whole document before you write a word, build a compliance checklist, draft against it, back every claim with evidence, then leave real time for review and submission. Most losing proposals don't lose on writing quality — they lose because they skipped a step below.
1. Make the bid / no-bid decision first
Before anyone drafts anything, decide honestly whether this is worth your time. A good response takes real hours; spending them on a bid you can't win is the most expensive mistake in the process. Weigh a few things:
- Fit. Do you meet the mandatory requirements (certifications, insurance, past performance, location)? A single missed "must" can disqualify you no matter how good the rest is.
- Relationship. Do you know the buyer, or is there an incumbent who does? Cold bids against an entrenched vendor rarely pay off.
- Effort vs. value. Estimate the hours against the contract size and your win odds. Skipping a weak fit frees you to win a strong one.
If you're unsure, a fast structured read of the document — every requirement, the real question count, the red flags — makes the call obvious. That go/no-go read is exactly what Pelican's free check gives you.
2. Read the entire RFP before you write
Read all of it — the scope of work, the instructions, the evaluation criteria, the terms, and every appendix. The evaluation section is the most important page in the document: it tells you how points are awarded, which is how you decide where to spend your effort. Note the submission deadline, the format rules (page limits, fonts, file types), the question deadline, and any mandatory forms.
3. Build a compliance checklist
Turn the RFP into a list of every requirement and every question, including the ones buried mid-paragraph. This compliance matrix is your single source of truth: each row is something you must address, mapped to where you'll address it. Evaluators often score with a checklist of their own — if a requirement has no matching answer, you simply lose those points. Nothing should slip through.
4. Ask questions before the deadline
Most RFPs allow a written question period. Use it. Ambiguity in the scope, contradictory requirements, or an unrealistic timeline are all worth raising — the buyer's answers are shared with every bidder and become part of the official record. Missing this window means guessing.
5. Draft against the checklist, in their order
Answer questions in the order the RFP asks them, using the buyer's own language and numbering. Evaluators move fast; make it effortless to find each answer and check the box. For each question:
- Answer the actual question first, directly, in the first sentence.
- Then support it with specifics — a method, a number, an example.
- Tie it back to the buyer's stated goal, not your capabilities.
Lead the whole proposal with a short executive summary that states why you're the right choice in the buyer's terms — write it last, once the body exists.
6. Back every claim with evidence
"We have deep experience" is worth nothing; "We ran the same program for the City of Harborlight, cutting response time 32% over 18 months" is worth a lot. Past performance, named references, concrete metrics, and relevant case studies are what separate a credible bid from a generic one. If you can't substantiate a claim, soften it or cut it — an unbacked promise reads as risk.
7. Leave real time for review and submission
Reserve the last stretch for a compliance review against your checklist: is every requirement addressed, every form signed, every page limit respected, every question answered? Then submit early. Portals crash, uploads fail, and "received at 2:01 for a 2:00 deadline" is a rejection in most procurement rules. Early submission is free insurance.
The mistakes that cost the most
- Answering the questions you wish they'd asked, not the ones they did.
- Talking about yourself instead of the buyer's outcome.
- Missing a mandatory requirement or an unsigned form.
- Reusing an old proposal without re-checking it against this RFP.
- Running out of time and skipping the compliance pass.
Done well, responding to an RFP is a process you can repeat and improve every time. The teams that win treat it that way. For more on structure, see our RFP response template and, for the one-pager buyers ask for up front, our guide to writing a capability statement.