The RFP Process Timeline: a team reviewing charts on laptops in a meeting room

RFP Process Timeline: 10 Steps and How Long Each Takes

Last updated:
October 31, 2026

The RFP process is the sequence of steps an organization follows to buy through a request for proposal. It runs from defining the need and issuing the RFP to evaluating proposals, negotiating and signing the contract. Plan in months. The University of Arkansas tells its departments to allow three to twelve months, and Kennesaw State reports a seven-month average.

This guide covers the ten steps, the time each one takes, a sample week-by-week schedule and what makes an RFP run long.

How long does an RFP process take?

Two public universities' procurement guides put an RFP at three to twelve months, and seven months on average, from scoping the work to awarding the contract. Public bodies follow posting and approval rules that add time, so a private company can usually move faster. Here is what the guides say, along with the federal minimums:

  • University of Arkansas. Its procurement office says "three (3) to twelve (12) months is the typical timeline" for an RFP where the award is based on selection criteria. A price-only invitation for bid typically takes one to two months. The same guide calls a 30-day solicitation period typical for most RFPs (RFP/IFB Procurement Lead Time, revised May 2023).
  • Kennesaw State University. Its procurement office told departments that "the average processing time for RFP scope development to contract award is seven months." RFPs for university-wide services, or used by several departments, can take up to a year (notice to departments, December 2023).
  • US federal agencies. The Federal Acquisition Regulation requires a public notice at least 15 days before a solicitation is issued. Agencies must then allow at least 30 days for bids or proposals on non-commercial purchases above the simplified acquisition threshold (FAR 5.203, as of FAC 2026-01).

Online guides often quote a month or two. That can work for a private company with a small decision team, no public posting rules and contract terms agreed in advance. Even then, the supplier response window and the negotiation each take weeks.

RFP timeline at a glance

The table maps the ten steps below to the planning ranges in the University of Arkansas guide. They are one public university's figures, not a standard, but they show where the time goes.

StepWhat happensPlanning time at one public university
1. Draft your business caseNeed, budget, spend baseline, scoring criteria7 to 14 days
2. Create your RFP templateScope of work, pricing template, contract terms14 to 60 days, plus 7 to 14 days for contract requirements
3. Confirm NDA with interested suppliersInvite list and confidentialityRuns alongside step 2
4. Distribute RFP documentsIssue, pre-proposal meeting, questions and answers14 to 30 days (30 is typical)
5. Collect proposalsDeadline, opening, completeness check3 to 5 days
6 to 8. Shortlist, research, selectScoring, presentations, references, best and final offers, intent to award14 to 30 days in total
9. Communicate your selectionNotify bidders, negotiate final terms30 to 60 days
10. Tie up legal endsLegal review, signatures, approvals7 to 30 days for legal review and 7 to 30 for signatures, plus 30 to 60 days of legislative review for services contracts in Arkansas

Source: University of Arkansas Procurement, RFP/IFB Procurement Lead Time (revised May 1, 2023). That guide groups steps 6 to 8 into one evaluation window.

RFP process steps

The ten steps below make up one full RFP cycle, from the first planning meeting to a signed contract. Times are the planning ranges from the table above. A private company can often move faster.

Diagram of the ten RFP process steps, from drafting the business case to tying up legal ends

1. Draft your business case

Agree on what the new contract must do before anyone writes the RFP. Bring together the people who use the product or service, the people who pay for it and whoever approves the award.

  • Write down the need, the budget and the date the current contract ends.
  • Pull 12 months of invoices so you know what you pay today. That baseline is how you'll judge the bids.
  • List must-haves and deal-breakers, so suppliers can be ruled out on facts rather than preferences.
  • Agree on the evaluation criteria and their weights now, before any proposal arrives.
  • Find out who must approve the award, and at what spending level.

Our list of questions to ask before you start an RFP helps at this stage.

Time: 7 to 14 days. Result: an approved business case and scoring criteria.

2. Create your RFP template

The RFP is the document every bidder works from, so any gap in it becomes a gap between the bids. Start from a template your organization has used before and adapt it. Include:

  • background on your organization and the current contract
  • the scope of work and the RFP requirements, split into must-haves and nice-to-haves
  • a pricing template every supplier must fill in, with your volumes, so bids can be compared line by line
  • the evaluation criteria and how much each one counts
  • the main contract terms, or the draft contract itself
  • the schedule: issue date, pre-proposal meeting, question deadline and due date
  • submission instructions and one named contact

Putting the contract terms in the RFP shortens the negotiation later. Suppliers raise their objections in the proposal instead of after you've chosen them.

Time: 14 to 60 days, plus 7 to 14 days for the contract requirements. Result: an RFP ready to issue.

3. Confirm NDA with interested suppliers

Decide who to invite. If you don't know the market well, a short request for information (RFI) first will show who can actually serve you. Then confirm which suppliers intend to bid.

If the RFP shares confidential data, such as volumes, prices or system details, ask suppliers to sign a non-disclosure agreement before you send it. A public RFP is a public document. Keep sensitive detail out of it, and share that detail later, under confidentiality terms, with the suppliers who need it.

Time: runs alongside step 2. Result: an invite list and signed NDAs where needed.

4. Distribute RFP documents

Issue the RFP to every supplier on the same day, with the same documents. Public bodies also post a public notice. The federal rules for grant-funded purchases require one for a request for proposals (2 CFR 200.320).

Most RFP schedules then include:

  • a pre-proposal meeting, sometimes called the RFP meeting or bidders' conference, about a week after issue
  • a deadline for supplier questions
  • written answers sent to every bidder as an addendum, so no supplier gets an advantage

Give suppliers enough time to price properly. The Arkansas guide calls a 30-day solicitation period typical for most RFPs. Federal agencies must allow at least 30 days on larger non-commercial purchases. Complex services with detailed pricing may need longer.

Time: 14 to 30 days. Result: an issued RFP and a log of questions, answers and addenda.

5. Collect proposals

Set a firm due date and time, and hold to it. Public RFPs usually reject late proposals, and accepting one in a private RFP is unfair to the suppliers who met the deadline. Open the proposals together, log what arrived and check each one for missing documents or pricing.

Time: 3 to 5 days. Result: a set of complete proposals.

6. Shortlist submissions

Ask each evaluator to score the proposals alone, against the published criteria, before the group meets. Then compare the scores and discuss the gaps.

Price needs its own work. Put every bid into the same pricing template, apply your real volumes and add every fee, so you compare total cost rather than headline rates. A shortlist of two to four finalists keeps the competition real without overloading the team. Tell the suppliers who didn't make the cut.

Time: steps 6 to 8 share one 14- to 30-day evaluation window. Result: a scored comparison and a shortlist.

7. Conduct deeper research

Use the finalist round to test what the proposals claim.

  • Ask each finalist to present, or to demonstrate the product using your own scenarios.
  • Call references. Ask how the switchover went and whether invoices matched the contract.
  • For large or long contracts, visit a site or check the supplier's financial stability.
  • If your rules allow it, ask for a best and final offer (BAFO) on price and terms.

Time: part of the shared evaluation window (see step 6). Result: checked information on each finalist, and their final offers.

8. Select your new supplier or vendor

Score the finalists again with everything you now know, using the same weights. Then get the approval your policy requires.

Write down why the winner won. Organizations spending federal awards must have written procedures for evaluating proposals and making selections (2 CFR 200.320(b)(2)). For any buyer, the written record is the defense if a losing bidder challenges the award.

Time: the end of the shared evaluation window, plus however long your approvals take. Result: an approved selection with a written rationale.

9. Communicate your selection

Tell the chosen supplier, then the others. Offer unsuccessful bidders a short debrief, which helps them bid better next time. Public bodies often issue a notice of intent to award first. Their rules may give losing bidders a short period to protest before the contract is signed.

Then finish the negotiation. Settle the final pricing and how prices can change during the term. Agree on the service levels, the KPIs you'll use to measure the supplier, and who does what during the switchover.

Time: 30 to 60 days, though the Arkansas guide notes that this stage varies widely. Result: agreed pricing and terms.

10. Tie up legal ends

Turn the agreement into a contract. Besides price and service levels, check that it covers:

  • claims and losses (liability and indemnity)
  • rights of access to facilities, vehicles or systems
  • confidentiality and data protection
  • insurance
  • compliance with laws, regulations and your own policies
  • price protection, such as a cap on annual increases
  • service-level credits and termination rights

Both sides' lawyers review the draft before it is signed, and some contracts also need board or legislative approval. Our post on common contract issues covers clauses worth a second look.

Time: 7 to 30 days for legal review and 7 to 30 days for signatures, plus any board or legislative review. Result: a signed contract.

After the contract is signed

The RFP cycle doesn't end at signature. The savings in the winning bid only count once they show up on your invoices.

  • Plan the switchover: start dates, ordering changes and who tells the users.
  • Check that the new prices are loaded in the supplier's system and in yours.
  • Compare the first invoices with the contract, line by line.
  • Track the agreed service levels, and review them with the supplier at set intervals.

Dryden's RFP management service runs the whole RFP for one category or a few, and this post-award check is part of it. For ongoing oversight of a key supplier, see supplier performance management.

Sample RFP schedule, working back from the contract end date

Start with the date your current contract ends and count back. Leave time for a switchover in case a new supplier wins, and a buffer for approvals. The example below is a services RFP whose stages sit inside the ranges in the table above. Use it as a starting point, not a benchmark.

WeekMilestone
1-2Business case, stakeholders, spend baseline, scoring criteria
3-6RFP document, pricing template and contract terms; invite list and NDAs
7RFP issued
8Pre-proposal meeting
9Supplier questions due; answers sent to every bidder
11Proposals due, 30 days after issue; opening and completeness check
12-14Scoring, shortlist, finalist presentations, references, best and final offers
15Selection approved; all bidders notified
16-21Negotiation and legal review
22Contract signed
23 onwardSwitchover, then post-award checks

In this example the contract is signed about five months after kickoff. Suppose the current contract ends on June 30 and the switchover needs eight weeks. The new contract must then be signed by early May, so the RFP has to start in early December.

What slows an RFP down, and how to avoid it

Many delays trace back to decisions that weren't made at the start.

What slows it downHow to avoid it
Requirements change after the RFP is issuedAgree on requirements and must-haves in step 1 and get sign-off before writing
Bids that can't be comparedMake every supplier use your pricing template and your volumes
Evaluators who can't find timeBook the scoring and presentation dates when you set the schedule
Legal review that starts after selectionPut your contract terms in the RFP and ask bidders to list their exceptions
An approval nobody planned forCheck board, committee and legislative thresholds at the start
Too many proposals or finalistsInvite suppliers who can serve you, and shortlist two to four
A rebid because too few suppliers respondedConfirm interest before issuing, and give enough time to respond

You may not need an RFP at all. If the supplier serves you well and only the price has drifted, renegotiating with the incumbent is usually faster, where your rules allow it. If you don't know whether your pricing is out of line, benchmark it first.

RFP timelines in universities and other public institutions

Public institutions add steps that a private company can skip, and each one takes time.

  • Federal award rules. Universities, hospitals and other organizations spending federal awards follow 2 CFR 200.320. For a request for proposals, the rule requires public notice and proposals from multiple qualified entities. Every evaluation factor and its relative importance must be stated up front, and the buyer needs written procedures for evaluating and selecting. States follow their own procurement policies instead (2 CFR 200.317), and so may public universities that state law treats as state agencies.
  • Federal agencies. Agencies follow the FAR, which sets the minimum notice and response periods described above.
  • State law and institutional policy. These add their own posting periods, bid thresholds, protest procedures and approvals. The University of Arkansas guide, for example, allows 30 to 60 days for legislative review of services contracts.
  • Boards and committees. They meet on fixed calendars. If a board meets monthly, missing one meeting adds a month.

Kennesaw State's note to its departments makes the same point: RFPs for university-wide services, or used by several departments, need extra time. Start early, and ask your purchasing office which rules apply to the money you're spending. A purchase funded by a federal grant can follow different rules from one paid from the operating budget. See how we work with higher education and the public sector.

RFP process FAQ

What is the RFP process in procurement?

The RFP process in procurement is the formal way an organization asks suppliers to propose how they would meet a need. The buyer compares the proposals on service, capability and total cost, not price alone. The steps are to set requirements, issue the RFP, answer questions, score the proposals, negotiate with finalists and award the contract.

Which comes first, an RFI, an RFP or an RFQ?

An RFI (request for information) comes first when you don't yet know who can supply what you need. An RFP follows when you know the outcome you want but need suppliers to propose the solution. An RFQ (request for quotation) replaces the RFP when you can specify exactly what you need and price decides. Our procurement methods guide compares them.

Who prepares the RFP document?

The buying organization prepares the RFP. A procurement or purchasing lead usually writes it with the people who will use the product or service, plus finance and legal. Some organizations bring in a procurement consultant to write and run it. Suppliers only respond, because letting one supplier help write the RFP gives it an unfair advantage.

How long should suppliers get to respond to an RFP?

Thirty days is a common response window for an RFP. The University of Arkansas calls a 30-day solicitation period typical for most RFPs. US federal agencies must allow at least 30 days for larger non-commercial purchases. Complex services, detailed pricing or site visits justify a longer window.

How many suppliers should make the RFP shortlist?

Two to four finalists make a practical RFP shortlist for most purchases. One finalist removes the competition that keeps final offers sharp, and more than four stretches the evaluation team. Invite enough suppliers to the first round to reach that number from compliant, competitive proposals.

What happens after an RFP is awarded?

After an RFP is awarded, the buyer signs the contract, notifies the other bidders and manages the switchover to the new supplier. The next step is easy to skip: checking that the agreed prices are loaded correctly and appear on invoices. The buyer should also track the service levels the contract promises.

Related service: RFP Management →

Link copied to clipboard