What an RFP shred actually is, and why most small contractors skip it

An RFP shred is the working document a proposal team builds before anyone writes a single sentence of response. It is the place where a solicitation stops being a 200-page PDF and becomes a structured set of requirements, evaluation criteria, submission instructions, and unanswered questions. Teams that skip this step end up writing toward a vibe of the RFP instead of the RFP itself, and that gap is what evaluators score against.

We have watched small contractors lose otherwise winnable bids because the shred never happened or happened in someone's head. The fix is not glamorous. It is a discipline.

What a shred actually contains

A useful shred has five sections, in this order.

Section L instructions, line by line. Every submission requirement, parsed and numbered. Page limits, font sizes, margins, file naming conventions, volume structure, ordering, the works. If Section L says the Technical Volume cannot exceed 30 pages and must use 12-point Times New Roman, that becomes row 1 of the shred. Every "shall" and "must" in the instructions becomes its own row.

Section M evaluation criteria, weighted. The factors and subfactors the government will use to score. If past performance is rated "Substantial Confidence / Satisfactory Confidence / Limited Confidence / No Confidence," that scale goes in the shred. If the trade-off language says technical is significantly more important than price, that weighting goes in the shred and drives every later writing decision.

The PWS or SOW requirements, decomposed. Every task, every deliverable, every performance standard. Numbered. Mapped to the section of the technical volume that will respond to it. This is the spine of the compliance matrix.

The clause matrix. Section I clauses and their flow-down implications. Especially the ones that touch CMMC level, EVMS, organizational conflict of interest, key personnel substitution, and any agency-specific supplements. The clauses are where compliance risk hides.

The questions list. Every ambiguity, every contradiction between sections, every undefined acronym, every place where the government said one thing in the PWS and a different thing in Section L. These become the formal questions you submit by the deadline, plus the internal data calls to your SMEs.

Where teams get it wrong

The most common failure pattern we see is treating the shred as a one-time event. The Section L row that said "Volume II must include a Subcontracting Plan if the offeror is a large business" gets added on day one, then never revisited when the team realizes the prime is a small business with a large-business teaming partner. The shred is a living document until proposal lock.

Second failure pattern. Teams copy the PWS verbatim into the compliance matrix and call it done. That is not decomposition. That is transcription. A real shred breaks "The Contractor shall provide help desk support during normal business hours, holidays excepted, and shall respond to Severity 1 incidents within 30 minutes" into three rows. Help desk coverage hours. Holiday exclusion. Severity 1 response SLA. Each row gets its own response section, its own evidence, its own win-theme alignment.

Third failure pattern. The shred lives in someone's local Excel file and never reaches the writers. By the time the technical lead is drafting Volume II, they are responding to their memory of the RFP instead of the actual decomposed requirements.

The minimum workflow

If you do nothing else, do this.

1. Open the solicitation and read it twice. The first read is for the structure, the second is for the surprises.
2. Build the Section L row list before you build anything else. Submission compliance is the first cut. A non-compliant proposal does not get scored.
3. Build the Section M weighting next. This determines how much page real estate each evaluation factor deserves.
4. Decompose the PWS into the compliance matrix. Every "shall" gets a row.
5. Map every PWS requirement back to where in your proposal it will be addressed. If a requirement does not have a clear home, you have a gap.
6. List the questions. Submit them. Then re-shred against the amendment.

Why this matters more for small businesses

A large prime can absorb the cost of a sloppy shred because they have proposal infrastructure that catches the gaps later. A small business with two people writing and one person reviewing cannot. The shred is where the small business compensates for the absence of a 30-person proposal shop. It forces the rigor that overhead would otherwise provide.

We built RFP Shred as the first stage of PursuitWorks because every other stage downstream is reading from it. Compliance matrix, capture analysis, win themes, past performance selection, pricing strategy. They all assume someone, somewhere, has actually decomposed the solicitation. When that assumption is wrong, the rest of the pipeline produces work that looks finished and reads as non-responsive. There is no shortcut for this step. There is only doing it well or paying for it at the evaluation board.