How to Shred an RFP: Turn a 200-Page Solicitation into a Requirements List
Shredding an RFP means breaking the solicitation into individual, numbered requirements — every “shall,” deliverable, deadline, and formatting rule — each tied to its source page. It is the first real work on any proposal, and everything that follows depends on getting it right.
Ask any proposal manager where the hours go on a new bid, and reading the solicitation comes up first. A 150-page federal RFP with a PWS and a dozen attachments can take an experienced person two to three full days to shred properly. Do it badly and the cost shows up later: a missed requirement in the final compliance check, or worse, a proposal found non-responsive before anyone reads your technical approach.
The good news is that shredding is a method, not an art. Teams that shred well follow the same seven steps every time.
What a good shred looks like
The output of a shred is a table — usually a spreadsheet — with one row per requirement and these columns:
| Column | Example |
|---|---|
| ID | REQ-014 |
| Requirement (verbatim) | "The contractor shall deliver a monthly status report no later than the 5th business day." |
| Source | Section C.4.2, p. 37 |
| Type | Mandatory |
| Proposal section | Vol. I, 3.2 Management Approach |
| Owner | Program Manager |
| Status | Drafted |
The seven-step shred
Assemble the complete solicitation package
Before you shred a single sentence, collect everything: the base RFP, every attachment (Statement of Work or PWS, CDRLs, pricing templates, clauses incorporated by reference), and every amendment issued so far. Teams that shred only the base document routinely miss requirements that live in Attachment J or in Amendment 0002. Record the amendment number you shredded against so you know what to re-check when the next one drops.
Split the document by function, not by page
A federal RFP has three sections that matter most: Section C (what you will do), Section L (how to write the proposal), and Section M (how you will be scored). State, local, and commercial RFPs use different labels but the same three functions exist — scope, instructions, and evaluation. Shred each function into its own tab or list. Mixing them is the most common reason teams end up writing to the scope while ignoring the formatting rules that get proposals rejected.
Pull every requirement sentence verbatim
Go sentence by sentence and copy out anything containing an obligation: shall, must, will, is required to, should, may, is encouraged to. Copy the exact wording — never paraphrase at this stage. Paraphrasing is where meaning drifts, and a requirement you have reworded is a requirement you can no longer prove you answered. One sentence often contains several requirements ("The contractor shall provide monthly reports and quarterly briefings") — split them into separate rows.
Give every requirement an ID and a source reference
Number each requirement (REQ-001, REQ-002…) and record the section number and page it came from. This reference is what lets a reviewer, a teammate, or an evaluator trace your answer back to the solicitation in seconds. When a requirement appears in two places with slightly different wording — common between Section C and the PWS — log both and flag the conflict for a question during the Q&A period.
Classify each requirement
Tag each row as mandatory (shall, must, will), desirable (should, preferred, encouraged), or informational (background the evaluator expects you to understand but not to answer directly). Mandatory items are pass/fail — missing one can make your proposal non-responsive. Desirable items are usually where scoring differentiation happens. This classification drives where you spend writing effort.
Capture the hidden requirements
Not every requirement looks like one. Page limits, font size, margin rules, file naming conventions, required forms, signature authority, submission portal rules, and deadlines are all requirements — and they are the ones most often missed because they sit in Section L prose or in a cover letter rather than in a numbered list. Shred them into their own "format & submission" list.
Map each requirement to an owner and a proposal section
Your shred becomes your compliance matrix the moment you add two columns: which section of your proposal answers this requirement, and who on your team owns writing it. From here, the shred is the backbone of the whole effort — the outline, the writing assignments, and the final compliance check all come from it.
The mistakes that cost bids
- Shredding before the amendments are in. Re-shred or diff every amendment; requirements, page limits, and due dates change.
- Paraphrasing instead of quoting. Evaluators score against the solicitation's words, not yours.
- Ignoring Section L. Formatting and submission rules cause more rejections than weak technical writing.
- Not splitting compound sentences. One sentence with three obligations is three requirements.
- Skipping page references. Without them, nobody can verify your compliance matrix in the final review.
- Trusting copy-paste on scanned PDFs. Image-based solicitations copy as garbage or nothing at all, and requirements silently drop out.
How long should a shred take?
Done manually, a careful shred takes roughly one to two hours per 20 pages of dense solicitation text, and longer for scanned documents that must be retyped. That is why many small BD teams skip it or do it partially — and why missed requirements are so common.
Software can now do the first pass. Parseo, for example, reads the full solicitation — including scanned and image-only PDFs — and returns every requirement classified as mandatory, desirable, or informational, with a verbatim quote and a page citation for each. A human still reviews the output, but reviewing a shred is far faster than building one from scratch. You can inspect a real one: our sample report on a 46-page municipal RFP lists 83 requirements, each tied to its page.
From shred to compliance matrix
Once every requirement has an owner and a proposal section, your shred is a compliance matrix. Keep it as the single source of truth for the rest of the effort, update it with every amendment, and run it one last time before submission. For the next step, see how to build a compliance matrix and the field guide to Sections L, M, and C.
Get your first-pass shred in minutes
Upload a solicitation and Parseo returns every requirement — classified, quoted verbatim, and cited to its page. The preview is free; no account or card needed.
Get a free preview →