Sales · Intermediate
Turn a long RFP into a requirements checklist
Pull every requirement, deadline and format rule out of a tender document into a table you can assign.
The task
Requests for proposal bury requirements across forty pages: mandatory criteria, scoring weights, formatting rules, submission deadlines. Missing one can disqualify you. Ask the assistant to extract them into a single table, then check it against the document.
A prompt to start from
Paste it into your AI assistant, then fill in the bits in [square brackets].
The attached document is a request for proposal. Extract every requirement into a table with these columns:
| Ref | Requirement (verbatim or close) | Mandatory or scored | Weighting if stated | Section/page | Suggested owner |
Then list separately: - Every deadline, including clarification-question deadlines - Formatting and submission rules (page limits, file types, portals) - Anything ambiguous we should ask a clarification question about
Don't summarise or merge requirements. If unsure whether something is mandatory, say so.
What to check in the output
- Spot-check at least ten rows against the page references.
- Search the document yourself for "must", "shall" and "mandatory" and confirm each one made it in.
- Deadlines: verify every one against the original. This is the column that costs you the bid if it's wrong.
Before you paste anything in
Tenders from public bodies are usually fine to process. Some private RFPs are confidential; check the document's terms and your AI policy first.
Your organisation's AI policy wins over anything here.
More for Sales
Prepare for a discovery call from public information
Turn a prospect's website, annual report and job ads into a one-page brief and five questions worth asking.
Summarise a sales call into CRM notes
Turn a call transcript into the fields your CRM actually asks for, with next steps and owners.
Draft a follow-up email after a demo
A short, specific follow-up that recaps what the prospect cared about, not what you showed.