RFP Shredder v1

Paste solicitation text (Sections L/M, the PWS/SOW, or the whole document). The shredder extracts every requirement statement — shall, must, is required to, no later than — classifies it by section, and builds an editable compliance matrix you can export to CSV.

Nothing leaves your browser. This page has no backend and makes no network calls — paste text from controlled documents with confidence. (Still: follow your own handling rules.)

1. Paste solicitation text

Copy text straight out of the PDF/Word solicitation (Ctrl+A, Ctrl+C works fine — messy line breaks, page headers, and TOC junk are handled). For a first pass, Sections C, L, and M are where the action is.

Options

Include “will” statements (often describe Government actions — flagged so you can triage) Include “should” statements (advisory)

2. Compliance matrix

Filter by source section

Filter by keyword

Req ID	Source §	Requirement	Type	Maps to proposal §	Status

Your edits (mapping, status) are included in the export. Data lives only on this page — export before closing.

How this works

Cleanup: line endings are normalized, repeated page headers/footers and lone page numbers are stripped, and hard-wrapped PDF lines are re-flowed into paragraphs.
Section tracking: the parser watches for Uniform Contract Format headings (“SECTION L”, “L.4.2”, “M-2”), the standard UCF part structure, and PWS/SOW/SOO headings, and tags every paragraph with the section in force at that point. The UCF itself comes from FAR 15.204-1 (Section L = instructions, Section M = evaluation factors, Section C = description/specifications/PWS).
Extraction: paragraphs are split into sentences, and any sentence containing a binding construction — shall, shall not, must, must not, is/are required to, is responsible for, will, no later than / NLT — becomes a row. Shall/must/required are tagged Mandatory, deadline language Deadline, and will statements Expected — many “will” sentences describe what the Government will do, so sentences that start with a Government actor are additionally flagged Gov’t actor? for quick triage rather than silently dropped.
Why a compliance matrix: evaluators score what they can find. Proposals are commonly rejected or downgraded for missing Section L instructions, and GAO routinely denies protests where the proposal simply failed to follow them. A matrix that maps every extracted requirement to the proposal section that answers it is the standard defense.

v1 limits, stated honestly: sentence-splitting on legal prose is imperfect (expect a few merged or split rows); tables and images don’t survive copy/paste from PDFs; incorporated-by-reference clauses (Section I) surface only if their text is pasted; and section detection depends on the document actually using UCF-style headings — commercial-format (FAR 12/8.4) solicitations get classified as “General” unless headed. Always review against the source document; this is a head start, not a substitute for reading the RFP.

Disclaimer. FedCite is a private publication and is not affiliated with, endorsed by, or connected to the U.S. Government or any federal agency. This tool is informational only — not legal advice, and not a guarantee that every requirement in your solicitation has been captured. The solicitation document itself (and its amendments) is the only authoritative source of requirements. Verify the matrix line-by-line before relying on it in a proposal.