RFP Response and Compliance Matrix
Four sheets and four documents that build the compliance matrix in their paragraph numbering first, then draft the narrative against it.
Free download · No account needed
Compliance Matrix, at a glance
Brightline Systems, RFP-2026-114, Marrow County Transit Authority
| Requirements found | 142 |
| Mandatory | 96, judged on the verb they wrote |
| No owner yet | 7, four of them mandatory |
| Submission deadline | 14 May 2026, 15:00 Central, per Amendment 0002 |
1. Where the requirements were
| Source | Rows | Mandatory |
|---|---|---|
| Section C, statement of work | 78 | 61 |
| Attachment J-3, requirements matrix | 41 | 41 |
| Section L, instructions to offerors | 14 | 11 |
| Section M, evaluation factors | 5 | 5 |
| Section H, special contract requirements | 4 | 4 |
Twenty-three mandatory requirements are written somewhere other than the statement of work and the requirements matrix. A response built from those two documents alone answers none of them.
2. Blocking now
Four mandatory rows, eleven days out
C.6.2 60 day record migration, no evidence at this volume. C.8.4 Willmar depot presence, no owner and no named engineer. J-3 row 41 availability conflicts with C.3.2.4. L.7.2 Amendment 0002 not acknowledged, which is disqualifying on its own.
3. Not the same thing
Fourteen requirements use should rather than shall. They are answered, briefly, and they are not given the page budget of an obligation.
The requirements are not all in the requirements document. A federal solicitation is issued in a uniform contract format of thirteen lettered sections. The work is described in Section C, the instructions for responding are Section L, and the criteria you are scored against are Section M. Section J lists the attachments and Section H carries special contract requirements. Binding obligations sit in all five. A compliance matrix built from the requirements spreadsheet alone is missing rows, and the missing ones disqualify.
The other failure is administrative. A late proposal is not considered, and the exceptions are narrower than most bidders assume. For electronic submission, the federal rule requires the file to have reached government infrastructure by 5:00 p.m. one working day before the due date, so uploading at the deadline leaves no recovery. Where a solicitation gives a date and no time, receipt is 4:30 p.m. local. Page limits, filename conventions, font minimums and unacknowledged amendments end bids the same way.
So the matrix comes first and the narrative is drafted against it. Every requirement keeps the buyer's own identifier, records which document and section it came from, and carries an owner and a page number before a paragraph exists. The evidence map separates proof you have to fetch from proof you cannot release from proof that does not exist. The security questionnaire that arrives alongside it is its own pack, and what you wrote last time is banked in the answer library. Send River this package, or take the sheets blank.
What's in the pack
Compliance Matrix
One row per requirement in the buyer's own identifier, with the source document and section, the modal verb they used, the compliance position and the response page.
Requirement to Evidence Map
What proves each compliance claim, who holds it, whether it can be released, and which claims have nothing behind them at all.
Pricing Sheet
The build behind whatever number goes into their template, line by line against their own reference numbering, with the assumption each price rests on.
Submission Checklist
Format, filename, page limit, font, volume split, portal, registration and deadline as scored rows, each verified by somebody who did not write the volume.
Clarification Questions
The questions to file before the window closes, each quoting the paragraph it is about and asking something with a single factual answer.
Executive Summary
Structured against the evaluation factors in the buyer's stated order of importance, with the space given to each factor matching the weight they gave it.
Narrative Response
Drafted against the matrix rather than the other way round, following the buyer's required outline heading for heading in their own vocabulary.
Exceptions and Assumptions
Every departure declared with the alternative offered and the price of full compliance, plus every fact the price depends on that the solicitation never confirmed.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and hand it the solicitation, or download the Word documents and CSV sheets and fill them in yourself.
- 2
Send the whole package
Narrative, requirements spreadsheet, pricing template, every attachment, every amendment, the portal instructions. Fourteen unhelpfully named portal downloads is the normal case.
- 3
Build the matrix first
Every requirement from every section, keyed to their numbering, with its source, its verb, its owner and its response location recorded before drafting starts.
- 4
Prove it, then check the packaging
The evidence map finds the claims nothing supports. The checklist catches the page limit, the filename and the unacknowledged amendment before upload.
Frequently asked questions
Is this template free?
Yes, no account and no card. The download is four Word documents and four CSV sheets. Opening it in River is the optional half: the agent reads the package, builds the matrix in their numbering, and fills the checklist from their instructions. Every other pack is listed in the template library, and the one-output jobs live under River's tool index.
What format are the downloaded files?
CSV for the four sheets and .docx for the four documents. The pricing sheet is deliberately not the file you submit: buyers almost always supply their own pricing template, and modifying it is itself a compliance failure, so the sheet here is the build behind whatever number goes into theirs.
Ours is a commercial RFP, not a federal one. Does this still apply?
Yes. The lettered sections are the federal convention, published on SAM.gov, and they make the point visible: obligations live in the instructions and the evaluation criteria as well as the statement of work. A commercial RFP scatters them the same way under different headings, so the matrix records source document and section either way.
What does this matrix capture that a normal one misses?
Three things. Requirements written into the instructions and evaluation sections rather than the statement of work. Requirements with no identifier, which get a derived key recording section, page, paragraph and opening words. And the modal verb, kept as written, so a shall and a should are not given the same page budget. Those same evaluation sections set the word budget for the executive summary.
What happens to a requirement we cannot meet?
It goes to Exceptions and Assumptions the moment the matrix row is set to anything but full compliance, with the alternative stated as a commitment and the price of full compliance stated too. Buried in a paragraph it reads as evasion. Declared it is a trade, and the same discipline carries into the contract review afterwards.
Will it tell us whether to bid at all?
No, and deliberately. This space assumes the decision to bid is made. What it will do is report what it observed in the package: a named product, a requirement only an incumbent could already satisfy, a timeline nobody new could meet. Those observations go to you and the call stays yours. Whether the team has room to write it is a capacity question.
The buyer keeps issuing amendments. How are those handled?
Amendments are read as documents in their own right, and the matrix records which rows they changed. Where one moves the deadline, the checklist row moves with it and the planned upload moves to the new working day before. An unacknowledged amendment is its own failing row on that sheet, and the public sector checklist types that row as unrecoverable rather than as formatting.
Build the matrix before you write the narrative
Take the Word documents and CSV sheets blank, or open this exact pack in River and let it read the whole solicitation first.
Edit with AI