Goal
Make sure every requirement in the RFP is answered, in the order and format the buyer asked for, before anyone starts writing.
Inputs
- RFP text: [paste the full document or the requirements and instructions sections]
- Submission deadline and format: [date, time, portal or email, page limits, file types]
- Our offer in brief: [service or product, relevant experience, team]
- Team available: [names or roles who can own sections]
Steps
- Extract every requirement, marking each as mandatory or desirable, with its clause number.
- Note the evaluation criteria and their weights, if given.
- Map each requirement to a section of the response and an owner.
- List gaps where we cannot meet a mandatory requirement.
- Draft questions for the buyer's clarification window.
Output format
- Go or no-go summary: fit, gaps, effort, and a recommendation.
- Compliance matrix: | Clause | Requirement | Mandatory or desirable | Response section | Owner | Status |
- Response outline following the buyer's required structure, with page budgets.
- Clarification questions, numbered, each quoting the clause.
- A writing timeline working back from the deadline, with an internal review day.
Check before answering
- No requirement in the text is left out of the matrix.
- Clause numbers match the RFP exactly.
- Gaps against mandatory requirements are shown at the top, not buried.
- No experience or certificates are claimed that the inputs do not state.






