LOCAL RFP SHREDDING · NO DOCUMENT UPLOAD
Turn an RFP package into one source-traceable compliance matrix.
Drop the solicitation, SOW or PWS, instructions, and text-based attachments together. ReqSift extracts obligation language locally and keeps the source file, page, and section on every row.
A repeated page number is ambiguous when a bid package has several PDFs. ReqSift records both the file name and page so reviewers can get back to the actual source.
One matrix across the complete working package
Select up to 20 PDF or TXT files in one pass. ReqSift reads them sequentially in the browser, extracts each file independently, then assigns stable IDs across the combined result. Repeated clauses in different files remain visible because their source context may matter.
| Matrix field | Why it matters in a package |
|---|---|
| Source file | Distinguishes the solicitation, instructions, PWS/SOW, and attachments. |
| Source page | Returns the reviewer to the exact page inside that file. |
| Section | Retains the nearest detected heading for surrounding context. |
| Stable row ID | Keeps assignments and review discussion anchored after filtering. |
From files to a working review queue
- Select the text-based files your organization authorizes for browser software.
- Review the extracted shall, must, required, deadline, and constraint language.
- Assign an owner, response section, status, and evidence or exception note.
- Filter the working set and export the visible rows to quoted UTF-8 CSV.
- Compare the finished matrix against every source file and amendment.
The RFP stays on the device
ReqSift does not send PDF bytes, pasted solicitation text, extracted requirements, or matrix edits to a document API. The editable workspace uses this browser's local storage. License activation is a separate request containing only the license key.
- No document upload bucket
- No AI prompt containing bid text
- No server-side document retention period
- No account required for the free first 25 rows
Limits a reviewer needs to know
ReqSift finds explicit language using deterministic rules; it does not infer unstated obligations or understand an image-only scan. Tables, cross-references, evaluation factors without obligation words, incorporated clauses, and amendments still require deliberate human review.
TRY THE REAL WORKFLOW
Drop the package. Inspect the first 25 rows free.
No signup, no document upload, and no payment required to evaluate the result.
Frequently asked questions
What is RFP shredding?
RFP shredding turns solicitation language into structured, reviewable rows while preserving where each row came from. The resulting compliance matrix helps a proposal team assign, map, review, and close requirements.
Does ReqSift upload the RFP package?
No. PDF and TXT reading, requirement extraction, editing, filtering, and CSV generation happen in the browser. ReqSift does not receive the source files or extracted matrix.
Can it process more than one RFP file?
Yes. One local package can contain up to 20 text-based PDF or TXT files, limited to 25 MB per file and 100 MB total. Every extracted row keeps its source file and page.
Does it work with scanned PDFs?
Not directly. Image-only PDFs need OCR before import. ReqSift intentionally states this limit instead of silently returning an incomplete matrix.
Can an RFP shredder guarantee complete compliance?
No. Automated extraction is a first pass. A qualified reviewer still needs to compare every row with the complete solicitation, attachments, amendments, and official answers.