Parses RFP, ITT, and tender documents to extract every requirement, evaluation criterion, and submission instruction into a structured compliance matrix. Use this skill when a user uploads an RFP and needs a compliance matrix, requirements register, or evaluation criteria breakdown. Also trigger when users say "build a compliance matrix", "extract requirements from this RFP", "what are the mandatory requirements", "parse this tender", "requirements register", "evaluation criteria", "submission checklist", or upload an RFP and need to understand what is being asked. This is the first step in any organized bid response.
Parses RFP and tender documents to extract every requirement, evaluation criterion, and submission instruction into a structured, actionable compliance matrix. This is the foundation of an organized bid response -- you cannot respond to what you have not catalogued.
Most bid teams start responding to RFPs by reading through the document and dividing up sections. This leads to missed requirements, duplicated effort, and last-minute discovery of mandatory criteria buried in appendices. A compliance matrix forces you to catalogue everything upfront, before a single word of response is written.
Accepted formats:
.pdf - RFP documents, annexes, schedules.xlsx / .csv - Requirements tables, evaluation scorecards.docx - Tender narratives, terms and conditionsAccept all documents the user provides. Tender packages typically include a main RFP document plus annexes, schedules, terms and conditions, evaluation methodology, and submission instructions as separate files.
Read every provided document. For each document, note:
Present a summary of what was received: "I've ingested [X] documents totaling approximately [Y] pages. Here's what each contains: [brief summary]. Shall I proceed with extraction?"
Scan every document for requirements. Look for:
Language signals:
Structural signals:
Commonly overlooked locations:
For each requirement found, extract:
Separately catalogue the evaluation methodology:
Catalogue every submission requirement:
Organize everything into a structured matrix:
## Compliance Matrix: [RFP Name / Reference]
### Overview
- Issuing organization: [X]
- Submission deadline: [Date, Time, Timezone]
- Total requirements extracted: [X]
- Mandatory: [X]
- Desirable: [X]
- Informational: [X]
- Evaluation criteria: [X] categories
### Submission Checklist
Every submission instruction as a checklist item, ordered by deadline.
### Requirements Matrix
| Req ID | Source | Requirement | Category | Priority | Weight | Response Type | Owner | Status | Notes |
Owner and Status columns left blank for the bid team to fill in.
### Evaluation Criteria
| Criterion | Weight | Scoring Method | Source |
### Key Dates
| Date | Event | Source |
All dates from submission deadline to project start, chronologically.
### Observations
- Requirements that are ambiguous and may need clarification
- Requirements that appear duplicated across documents
- Requirements that seem to contradict each other
- Any gaps where you would expect requirements but none were stated
Present the matrix to the user. Highlight:
Ask: "Would you like me to export this as a spreadsheet (.xlsx) so your team can assign owners and track progress? Or would you prefer to keep it as a document?"
.xlsx (preferred for team use) or .md.docxThe .xlsx format is recommended because bid teams need to filter, sort, assign owners, and track completion status -- spreadsheets are the natural format for this.