A practical working method
RFP shredding: turn source clauses into a usable compliance matrix
RFP shredding means breaking a request for proposal into individual requirements that a proposal team can assign, answer and verify. A useful matrix connects each obligation to its source, response owner and proposal evidence. It is more than a list of sentences containing “shall”.
RFPAI product team · Updated 2026-11-03
The essential review rule
Keep the exact source wording and its location. Separate obligations that need different evidence, preserve every condition and exception, and leave compliance pending until a person checks the actual response.
Open free matrix tool →How to carry out the review
1. Freeze the source set
Record the RFP title, issue date and version. List appendices, pricing forms, schedules and issued amendments. Keep a copy of each source. A matrix extracted from the main document cannot establish coverage of attachments that were never supplied.
2. Find obligations, not just keywords
Review instructions, eligibility, deliverables, service levels, submission rules and evaluation criteria. “Must” and “shall” are useful signals, but table cells, checkboxes and headings may also contain obligations. Distinguish mandatory conditions from preferences; ask the buyer about ambiguity rather than inventing a rule.
3. Split carefully and preserve context
One clause can contain several obligations. Separate them when they have different owners or evidence, but carry over shared deadlines, triggers and exceptions. Keep the full original quote beside the working interpretation. Do not shorten “within 30 calendar days after contract signature” to an unqualified “30 days”.
4. Assign evidence and ownership
Use a stable internal ID, source section, actual PDF page, exact quote, owner, response location, evidence and review status. Word pages vary by rendering, so use source sections when actual pages are unavailable. The blank Excel templates include source, status, owner and notes columns; keep version details in your working copy.
5. Review the extraction against the original
Read the source in order and check every extracted row, especially tables, negations, numbers, cross-references and conditional clauses. Look for missing requirements as well as incorrect ones. Assign a reviewer before moving a row from pending to confirmed. A generated response is not proof that the bidder meets it.
6. Reconcile amendments before reuse
Compare the old and new source wording, including revised attachments. Record added, removed and changed clauses. Link the change to affected response evidence and reopen the review. Generated row numbers can change between runs; match the original clause and its source instead.
Worked exercise: one clause, two obligations, one shared deadline
This is an original fictional teaching exercise, prepared for this guide. It is not an AI extraction result or a test of model accuracy. Fictional source: section 3.2, PDF page 4: “The supplier shall deliver and install the system within 30 calendar days after contract signature, and shall provide two training sessions within the same period. Remote training is permitted if the buyer agrees in writing.”
| Working requirement | Context to preserve | Evidence to request | Initial status |
|---|---|---|---|
| Deliver and install the system | §3.2 · p.4; within 30 calendar days after contract signature | Delivery and installation schedule tied to the contract date | Pending review |
| Provide two training sessions | §3.2 · p.4; same 30-day window; remote only with written buyer agreement | Training plan with two sessions; written agreement if remote delivery is proposed | Pending review |
Amendment example: do not carry forward an old confirmation
Suppose amendment 1 changes section 3.2 to 20 calendar days and requires on-site training. Both rows need review. Update the schedule, remove the remote-delivery assumption and ask the owners for new evidence. Retain the previous wording and the amendment reference in your working record. RFPAI does not automatically reconcile amendments or manage owners across versions; export the matrix and maintain that review yourself.
Frequently asked questions
How is RFP shredding different from a compliance matrix?
Shredding is the extraction and interpretation work. The compliance matrix is the working record that connects the resulting requirements to owners, responses, evidence and review status.
Can I create a compliance matrix automatically from an RFP?
RFPAI can extract mandatory requirements from public or fictional PDF and Word files and export Excel. Review the output against every relevant source. It does not guarantee that every obligation has been found, and it cannot confirm compliance without actual proposal evidence.
Can I upload confidential tenders or scanned PDFs?
The free version accepts public or fictional material only, without confidential or personal information. Providers may retain it and use it for training; explicit acknowledgement is required. Files are limited to 4MB, 50 PDF pages and 60,000 characters. Scanned PDFs need OCR first.