RFP Timeline: A 12-Week Schedule From Requirements to Contract

8 min read ยท 2026-10-25

An RFP timeline is the schedule for a request for proposal, from writing the requirements to signing the contract with the chosen vendor. For a mid-sized purchase, such as a software platform or a managed service, many organizations plan 8 to 16 weeks. That usually breaks down into a few weeks of internal preparation, three to four weeks for vendors to respond, and four to six weeks for evaluation, demos, negotiation and award.

Most RFPs run late for the same reasons: requirements are not agreed before the RFP goes out, the evaluation team has no time booked, and legal review starts only after the winner is chosen. The schedule below covers 12 weeks in six phases, with a milestone you can check at the end of each phase. You also get the dates to publish in the RFP document, a filled-in example, owners for each step, how to shorten or extend the plan and what vendors should plan on their side.

The roadmap at a glance

Goal: Select a vendor through a fair and documented RFP process and sign the contract within 12 weeks of kickoff. Duration: 12 weeks

  1. Requirements and approvals (Weeks 1-2)

    Agree internally on what you are buying, why and who will decide.

    • Hold a kickoff with the business owner, procurement, IT, finance and legal to agree scope and goals.
    • Write the requirements as must-haves and nice-to-haves, with input from the people who will use the solution.
    • Confirm the budget range and approval path with finance.
    • Name the evaluation team and book their time for the evaluation weeks now.

    Milestone: Signed-off requirements, budget approval and an evaluation team with time blocked in their calendars.

  2. Draft the RFP and scoring model (Weeks 2-4)

    Write an RFP that vendors can answer and you can score fairly.

    • Draft the RFP: background, scope, requirements, response format, timeline and contract terms.
    • Build the scoring model with weighted criteria, such as functional fit, implementation approach, support, cost and vendor stability.
    • Have legal review the terms and procurement check that the process follows company policy.
    • Build a long list of vendors from market research, peers and analyst reports, then shortlist those you will invite.

    Milestone: Final RFP document and scoring model approved by the business owner and procurement.

  3. Issue and vendor questions (Weeks 4-5)

    Send the RFP and answer questions so every vendor works from the same information.

    • Send the RFP to the invited vendors with a request to confirm intent to bid within a few days.
    • Hold an optional vendor briefing call to explain the scope and context.
    • Collect written questions until the published deadline.
    • Publish all answers to all vendors at the same time, without naming who asked.

    Milestone: Intent to bid received from enough vendors and the consolidated Q&A sent to all of them.

  4. Proposal period (Weeks 5-7)

    Give vendors enough time to write good proposals while your team prepares to evaluate.

    • Keep the proposal window open for a set period, often three to four weeks from issue.
    • Prepare demo scripts based on your top use cases, so every vendor shows the same scenarios.
    • Brief evaluators on the scoring model and how to record their scores and comments.
    • Check proposals on arrival for completeness against the required format.

    Milestone: All proposals received by the deadline and checked for completeness.

  5. Evaluation, demos and shortlist (Weeks 8-10)

    Score proposals independently, see the top vendors in action and pick a preferred vendor.

    • Have each evaluator score the proposals independently before any group discussion.
    • Hold a consensus meeting to agree scores and shortlist two or three vendors.
    • Run scripted demos with the shortlisted vendors and score them with the same model.
    • Call two or three references for each finalist and run any security or financial checks.

    Milestone: A documented evaluation summary recommending a preferred vendor and a backup, approved by the business owner.

  6. Negotiation and award (Weeks 10-12)

    Agree final terms, sign the contract and close the process properly.

    • Negotiate scope, pricing, service levels and contract terms with the preferred vendor.
    • Run the final legal and finance review and get signatures through the approval path.
    • Notify the vendors who were not selected and offer a short debrief.
    • Hand over to the implementation team with the proposal, the contract and the evaluation notes.

    Milestone: Contract signed, unsuccessful vendors notified and implementation kickoff scheduled.

The dates to publish in your RFP

The timeline section of the RFP document tells vendors what to expect and when. Vendors plan their writing team around it, so publish dates you can keep. Moving a deadline after issue is possible, but every change must go to all vendors at once and in writing.

Put the dates in a simple list near the top of the RFP, with the time zone for every deadline. Keep the internal steps, such as legal review or the consensus meeting, in your own plan. Vendors only need the dates that involve them.

  • RFP issue date.
  • Intent to bid deadline: a few days after issue.
  • Vendor briefing call: optional, in the first week.
  • Question deadline: usually one to two weeks after issue.
  • Answers published: a few days after the question deadline.
  • Proposal due date and time.
  • Shortlist notification and demo window.
  • Expected award date and planned contract start.

Example: a filled-in RFP timeline

Picture a 900-person company replacing its IT service management tool. The IT operations manager owns the project, procurement runs the process and the contract with the current tool ends in five months. Here is how the 12 weeks could look.

The five-month contract end date sets the deadline. Working backward, the team needs the contract signed by week 12 to leave enough time for implementation and data migration before the old tool switches off.

  • Weeks 1-2: workshops with service desk agents and team leads, 60 requirements agreed, five evaluators booked. Owner: IT operations manager. Milestone: requirements signed off.
  • Weeks 2-4: RFP drafted, scoring weights agreed (functional fit 40, implementation 20, support 15, cost 15, vendor stability 10), seven vendors invited. Owner: procurement lead. Milestone: RFP approved.
  • Weeks 4-7: RFP issued, 34 questions answered in one document, six proposals received on time. Owner: procurement lead. Milestone: proposals checked for completeness.
  • Weeks 8-10: independent scoring, three vendors shortlisted, half-day scripted demos, reference calls. Owner: evaluation team. Milestone: preferred vendor and backup approved.
  • Weeks 10-12: negotiation, legal review, contract signed, debriefs offered to the others. Owner: procurement lead with legal. Milestone: implementation kickoff booked.

Who owns what

An RFP needs one person who owns the schedule and the vendor communication, usually from procurement. That keeps the process fair, because vendors talk to one contact and get the same answers. The business owner owns the requirements and the final recommendation.

Write the owners and their deadlines in a RACI at kickoff. RFPs often slip in the evaluation weeks because evaluators have day jobs. Booking their time in week one is the cheapest way to protect the schedule.

  • Business owner: defines the need, approves requirements, signs off the recommendation.
  • Procurement lead: owns the timeline, the RFP document, vendor contact and the negotiation.
  • Evaluation team: scores proposals and demos independently, joins the consensus meeting.
  • IT and security: technical requirements, integration and security review.
  • Legal: contract terms, review of vendor redlines, final contract.
  • Finance: budget, approval path, total cost review.

How to shorten or extend the timeline

A simple purchase with a few vendors can run in six to eight weeks. Shorten the internal steps first, not the vendor window. Cutting the proposal period to one week gets you rushed, generic answers or fewer bids. Reuse requirements and terms from a previous RFP, keep the vendor list short and run demos in a single week.

Complex, high-value or regulated purchases often need longer. Public sector bodies may have required notice periods and formal steps set by procurement rules, so confirm them with your procurement or legal team before you set dates. Large IT projects may add a proof of concept, which can add several weeks. Add time for holidays and for vendors in other time zones.

  • Speed it up: reuse templates, pre-qualify vendors, book evaluators early, run legal review of terms before issue.
  • Add time for: proofs of concept, formal public procurement steps, many evaluators, multiple business units.

If you are the vendor: plan your response timeline

When you receive an RFP, the buyer's dates set your schedule. Work backward from the due date. Decide quickly whether to bid, because a late decision cuts into writing time. A common approach is a bid or no-bid meeting within two days of receipt, based on fit, competition and your chance of winning.

Assign a bid manager who owns the response plan, the content library and the final review. Send your questions before the deadline, since they shape your answer and sometimes the buyer's thinking.

  • Days 1-2: read the RFP, hold the bid or no-bid meeting, confirm intent to bid.
  • Days 3-7: build the response outline, assign sections to subject experts, send questions.
  • Middle of the window: write drafts, build pricing, gather case studies and references.
  • Last week: executive review, compliance check against every requirement, final formatting and submission a day early.

How to present it to stakeholders

At kickoff, show a one-slide timeline with the six phases as bars across 12 weeks and the key dates as milestones: RFP issue, proposal due, shortlist, demos, award and contract signature. Under the timeline, list the decisions you need from the sponsor and the time you need from each evaluator.

At the award stage, present the evaluation summary on one slide: the scoring weights, each vendor's total score, the main strengths and risks of the preferred vendor, and the backup option. Keep individual score sheets and the full proposals in the appendix for audit.

Common mistakes to avoid

  • Issuing the RFP before requirements are agreed leads to change after change, so get written sign-off on requirements before drafting.
  • Giving vendors too little time produces weak or missing bids, so leave a proposal window of three to four weeks for most purchases.
  • Answering vendor questions one by one gives some bidders an advantage, so publish all answers to all vendors at the same time.
  • Scoring proposals together in a meeting lets the loudest voice decide, so have evaluators score independently first and then hold a consensus meeting.
  • Starting legal review only after picking the winner adds weeks at the end, so have legal review the contract terms before the RFP goes out.
  • Forgetting to notify unsuccessful vendors damages your reputation with the market, so send notices and offer a short debrief after the award.

Frequently asked questions

How long does an RFP process take?

It depends on the size and complexity of the purchase. Many mid-sized purchases take 8 to 16 weeks from requirements to signed contract. Simple purchases can be faster, while public sector or highly regulated purchases often take longer.

How much time should vendors get to respond to an RFP?

Three to four weeks is a common window for a moderately complex RFP. Simple requests may need only two weeks, while complex ones may need more. Too short a window leads to fewer and weaker proposals.

What are the key dates in an RFP timeline?

The main dates are the RFP issue date, the intent to bid deadline, the question deadline, the date answers are published, the proposal due date, the shortlist and demo window, and the expected award date. Publish them in the RFP with a time zone for each deadline.

Can you change the RFP timeline after it is issued?

Yes, but send the change to all vendors at the same time in writing, usually as an addendum. Extend deadlines rather than shorten them, and give a reason if you can. Frequent changes signal a poorly planned process and can reduce the number of bids.

Generate this roadmap with AI