One caveat up front: the RFP's own instructions always win. If the buyer prescribes an order, a format, or specific forms, follow theirs exactly. Use this template to organize your thinking and your reusable content — not to override the structure the evaluator will score against. With that said, here are the sections almost every response needs.
1. Cover letter
One page, signed by a decision-maker. Thank the buyer, name the project, and state in two or three sentences why you're the right fit — in their terms, not yours. Confirm you've read and can meet the requirements. This is a business letter, not a sales pitch; keep it warm and brief.
2. Executive summary
The most-read section and often the only one a busy evaluator reads closely. In half a page to a page, state the buyer's problem as you understand it, your proposed solution, and the two or three reasons you win — your discriminators. Write it last, once the body exists, and lead with the buyer's outcome rather than your company history.
3. Understanding & approach
Show that you understand the problem, then lay out how you'll solve it. Restate the scope in your own words to prove comprehension, then walk through your methodology, phases, deliverables, and timeline. Specifics are what earn points here — a named process, a realistic schedule, the roles who'll do the work. Vague approaches read as risk.
4. Project plan & timeline
A concrete plan with phases, milestones, and dates. Map your timeline to the buyer's deadline and call out dependencies and assumptions. A simple table or milestone list beats a wall of prose; evaluators want to see that you've thought through sequencing and can deliver on time.
5. Team & qualifications
Introduce the people who'll actually do the work, with short bios focused on relevant experience — not full résumés. Include an org chart if the project is large. Tie each key person to the part of the scope they own. Buyers hire teams, not logos.
6. Past performance & case studies
Proof that you've done this before. Two or three relevant projects, each with the client (named if permitted), the challenge, what you did, and the measurable result. Add references the buyer can call. This is the single most persuasive section in most proposals — concrete outcomes outperform adjectives every time. For a standalone version buyers often request, see our capability statement guide.
7. Pricing
Follow the buyer's pricing format precisely — if they give a table or a worksheet, use it. Be clear about what's included, what's optional, and what assumptions the price depends on. Never invent a number to fill a cell; an unexplained or padded price invites scrutiny. Where the RFP asks for a fixed fee, make sure your scope statement and your price agree.
8. Compliance & required forms
Certifications, insurance, licenses, signed attestations, and any mandatory forms or exhibits. Build a compliance matrix that maps every RFP requirement to the page where you address it — this doubles as your final checklist. Missing a required form is one of the most common reasons an otherwise strong bid is thrown out before it's even scored.
9. Appendices
Supporting material the evaluator may want but shouldn't have to wade through: full résumés, certificates, detailed technical specs, sample deliverables. Keep the main body tight and push depth here.
Make the template reusable
The real payoff is not writing any single proposal — it's never writing the same answer twice. Keep a library of your best past responses: your standard approach language, your strongest case studies, your team bios, your compliance boilerplate. For each new RFP you then adapt rather than start over, and your answers get sharper every cycle.
- Store answers by question type, not by client, so they're easy to reuse.
- Keep metrics and references current — stale numbers undercut credibility.
- Always re-tailor reused text to this buyer's language and goals.
That last point matters most. A template gives you a fast, complete first draft; the win comes from adapting it to the specific request. Pelican works this way by design — it breaks a request into its questions, drafts each one from your own documents, and remembers your best answers for next time. For the full process around this template, read how to respond to an RFP.