An RFP response is scored against a sheet neither side wrote — the buyer's own questionnaire — and an answer out of that sheet's order costs marks before its content is even weighed.
Response to RFP 2025-17 — Case management platform
We meet every mandatory requirement and propose a phased rollout that has the first office live within ninety days.
A fixed implementation fee, then a per-office subscription; year one is itemised in section 7 and capped.
A buyer works down their own questionnaire and expects each answer in that order, so a response organised on its own logic loses marks before an evaluator reaches the substance. Compliance has to be stated requirement group by requirement group, not claimed once for the whole bid, and a due date left only in an email gets lost inside a list of attachments. The evaluator scoring a stack of these against one sheet needs this, not the person who decided to bid.
Every answer under the question it answers, in the sheet's own order
Each question gets its own heading, following the order the questionnaire listed it, so an evaluator working down their sheet finds the matching answer without hunting through a document organised on different logic.
Compliance answered by requirement group, not claimed once for the whole bid
Every requirement group gets its own cell, and what sits inside it is the specific list of what you comply with for that group — not one line claiming compliance for the whole response, and not a tick against a box.
A deadline written into the document itself, not only in an email
The date a response is due is written beside the question it governs, right on the page, and where more is needed a share link can carry its own expiry date, so the response itself stops opening after the day you choose.
Which question held an evaluator longest, by its own heading
You see how long each question's heading stayed in front of an evaluator, and whether they doubled back to one once they had already gone on to the next — a sign of which part of the sheet is still being weighed, question by question rather than the response as a whole.
An example — not your document. Sections are the document’s own headings.
Most of their attention went to “Matrix” — 2m 09s of 4m 00s.
Time each section spent on screen, counted only while the tab was in front and the reader was active. It shows what was in front of them, not what they read.
This page is about what a rfp response has to do. For the blocks the editor is built from — see the editor.
No — it is a grid of cells, one per requirement group. Each cell holds a plain list of what you comply with; there is no checkbox or tick built into it.
Not on the page itself — write the due date in the document the way you would any date. If you want the response to stop being reachable after that day, set an expiry on the share link; the document has no expiry logic of its own.
Not yet — start from a blank document; requirement-group headings and a compliance grid both work from the first answer you write.