The RFP Timeline: Questions, Amendments, and Award

This is Part 6 of The Solicitation Author’s Handbook, a vendor-neutral series for people in offices of government who write solicitations. Part 5 built the evaluation machinery. This part is about the clock, the most commonly abused instrument in procurement. Educational information, not legal advice.

Build the calendar backward

Start from the date the service must be live, then walk left: implementation and transition time (ask your market research, not your optimism), contract negotiation and signature, award and any mandatory protest window, evaluation including demonstrations and references, the response window, the question-and-answer period, and drafting with reviews. Add the buffer you already know one of these will need. If the walk lands before today, the honest conclusions are to shorten the implementation ambition, extend the deadline upstream, or use a faster vehicle your code allows, not to compress the response window and hope.

The response window deserves particular protection because it is the one interval you impose entirely on other people. A window that gives serious vendors too little time to do serious work does not speed your project up; it filters your respondent pool down to whoever had a proposal already written, and Part 4 explained who that tends to be. Match the window to the effort your document demands, and remember that windows spanning major holidays are shorter than they look.

Publish the full calendar in the solicitation, question deadline, answer publication date, close, evaluation period, anticipated award, so vendors can plan people against it. Then keep it, or amend it visibly.

The Q&A period is free consulting

Vendor questions are the best free review your document will ever receive. Dozens of professionals who respond to solicitations for a living are reading your document closely and telling you, in writing, where it is ambiguous, contradictory, or impossible. Treat the questions as data, not as annoyance.

Mechanics that keep the period fair and useful:

• One channel, in writing, to a deadline. No side conversations, no phone answers to whoever thought to call; anything answered anywhere gets answered for everyone.
• Publish all questions with all answers to all holders of the document, anonymized as your code prefers.
• Answer the question asked. Where a question exposes a genuine flaw, fix the document by amendment rather than lawyering the answer around it.
• Watch for the question that is really an argument, a vendor establishing a protest record about a requirement they believe steers to a competitor. That question deserves your most careful, most documented answer, and sometimes deserves the amendment it is fishing for.

A cluster of questions on the same section is a verdict on the section. If five vendors independently misread your scope boundary, the boundary is unclear, whatever you meant by it.

Amendments without accidental scope changes

Amendments are the honest instrument for changing anything after publication: requirements, dates, evaluation criteria before close. The discipline is procedural sameness: numbered amendments, published to every holder through the same channel as the original, with acknowledgment required in responses so no vendor can later claim to have priced version one. Two cautions from the pattern file: an answer in the Q&A document that quietly enlarges or shrinks scope is an amendment wearing a disguise, and will be treated as one by anyone aggrieved; and an amendment issued close to the deadline without extending it is arithmetic vendors notice, if the change is material, the window moves with it.

Extension requests are signal, not weakness. One vendor asking is scheduling; three vendors asking means the market is telling you the window and the workload disagree, and granting a visible, uniform extension costs days while refusing may cost your best respondents.

From close to award without drama

At close, log what arrived and when, and apply the lateness rule your solicitation stated, uniformly, without exceptions for the well-connected or the almost-on-time. Evaluation then runs on Part 5’s machinery. Two clock disciplines remain. First, tell vendors where things stand if the published award date slips; silence reads as trouble and generates records requests that cost more than the sentence “evaluation is continuing, we expect award by the 15th.” Second, respect the quiet period your code imposes between recommendation and award, and make sure everyone who talks to vendors knows it exists; a hallway assurance to a bidder during the window is how clean evaluations acquire dirty endings.

Award notices go to everyone who responded, not only the winner, with the debrief offer from Part 5 attached. Then keep the file: solicitation, amendments, questions and answers, submissions log, scoring sheets, reconciliation memo, award memo, notices. That file is the project’s birth certificate, and in most jurisdictions much of it is public record; write every page as if the request has already arrived, because eventually it will.

The timeline checklist

• The calendar was built backward from the live date, with the buffer written in.
• The response window matches the demanded effort and avoids holiday arithmetic.
• Questions flow through one written channel and answers publish to everyone.
• Material changes travel as numbered amendments, with the deadline moved when the change warrants it.
• Late responses are handled by the published rule, uniformly.
• The complete file exists as the process runs, not as a reconstruction afterward.

Part 7 opens the door most templates quietly lock: pricing structures beyond firm-fixed line items, and how to write a solicitation that can accept a cost-neutral answer without losing comparability between bids.

The Solicitation Author’s Handbook is published by GovSoft as a public resource for offices of government. It is educational information, not legal advice.