How to Award an RFP: Selection, Notification, and Debriefing

In the wild turkey world, the strut is just the beginning. After the male displays his feathers and fans his tail to the entire flock, there's a clear moment of selection. The hen makes her choice. No ambiguity, no "we'll circle back next quarter," no ghosting.

Awarding an RFP should be just as decisive. But in most organizations, the evaluation ends with scores on a spreadsheet and then... nothing happens for two weeks. Internal politics surface. Someone wants to "check with legal one more time." The winning vendor starts to wonder if they actually won. The losing vendors hear nothing at all.

Here's how to close the RFP process cleanly, professionally, and in a way that protects your organization and your reputation.

Step 1: Confirm the evaluation is complete

Before you announce a winner, make sure the foundation is solid:

All evaluators have submitted scores. No stragglers, no "I'll get to it this week."
Score discrepancies have been discussed. Where evaluators differed by 2+ points on a question, the team has talked through the reasoning. Not to force consensus — to ensure everyone saw the same information.
References have been checked. Call at least two reference clients for your top candidate. Ask specific questions: "Was the implementation on time? What would you do differently? Would you choose them again?"
Commercial terms are acceptable. Pricing, contract length, SLAs, termination clauses — legal and finance have reviewed the top vendor's proposal.

Rushing to award without completing these steps is how organizations end up committed to a vendor they should have screened out. And unwinding a vendor selection after announcement is exponentially more painful than taking an extra week to verify.

Step 2: Make the selection decision

The math should drive the decision, but the decision isn't purely mathematical. Consider:

The scores

Your weighted scoring matrix gives you an objective ranking. The vendor with the highest total score is your starting point. If you're deviating from the scores, you need a documented reason. For a deep dive into weighted scoring methodology, see How to Score Vendor RFP Responses.

The red flags

Sometimes a vendor scores well overall but has a specific weakness that's disqualifying. Maybe their data migration approach is vague. Maybe their key reference client had a rough implementation. Maybe their support model doesn't cover your time zone. A high total score doesn't override a critical gap. Learn to spot red flags that signal a bad vendor fit before you commit.

The gut check

After all the scoring and analysis, does this vendor feel right? Do you trust them to deliver? Did they demonstrate genuine understanding of your needs, or did they give polished generic answers?

The gut check shouldn't override the data. But if the data says one thing and your entire evaluation committee has reservations, that's worth exploring before you commit.

The opportunity cost of picking wrong is enormous. A bad vendor selection doesn't just cost you the contract value. It costs you months of implementation, the momentum of the project that depended on this vendor, and the organizational will to try again. Choose carefully.

Step 3: Get internal approval

Before you tell anyone outside your organization:

Document the recommendation. Write a brief summary: who you're recommending, why, how they scored, and how they compared to alternatives. This protects you and the process.
Get the necessary sign-offs. Budget owner, legal, IT (if applicable), executive sponsor. Know your organization's approval workflow and follow it.
Prepare the contract. Don't announce a winner and then spend six weeks negotiating terms. Have the contract framework ready so you can move quickly after notification.

Step 4: Notify the winning vendor

This should happen first — before you notify anyone else. The winner notification should include:

Clear confirmation. "We're pleased to inform you that [your company] has been selected as our vendor for [project name]."
Next steps. Contract timeline, kickoff meeting scheduling, key contacts.
Any conditions. Final contract negotiation points, compliance requirements, background checks if applicable.
Timeline. When you expect to have the contract executed and the project started.

Keep it professional but warm. This vendor is about to become your partner. Start the relationship well.

What not to do

Don't make a verbal commitment without written follow-up. "We've decided to go with you" said in a phone call without documentation leads to misunderstandings.
Don't announce before contracts are ready. A "win" that takes 8 weeks to materialize isn't a win — it's anxiety.
Don't skip internal approvals. Nothing undermines a procurement team's credibility faster than announcing a winner and then having finance reject the budget.

Step 5: Notify unsuccessful vendors

This is where most organizations fail. They ghost. They send a one-line email. They say "we went another direction" and offer nothing else.

That's a mistake for three reasons:

These vendors invested real time and effort in their proposals. A thoughtful response costs you nothing and preserves goodwill.
You might need them later. The vendor you didn't pick today might be perfect for your next procurement. Don't burn the bridge.
Your reputation precedes you. Vendors talk. If your RFP process is known for ghosting, the best vendors will stop responding to your RFPs.

What to include in an unsuccessful notification

Gratitude. Thank them for their time and the quality of their response.
The decision. Be direct: "We have selected another vendor for this engagement."
An offer to debrief. "We're happy to schedule a brief call to discuss our evaluation and provide feedback on your proposal." Not all vendors will take you up on this. The ones who do will respect you for offering.
Future consideration. If genuine, let them know you'd welcome their participation in future RFPs.

What not to include

Don't name the winning vendor. That's the winner's news to share, not yours.
Don't provide detailed scoring breakdowns in the notification email. Save that for the debrief call if they request one.
Don't apologize. You made a business decision. Be professional and direct.

Step 6: Conduct debriefs (if requested)

Debrief calls are optional but valuable. When an unsuccessful vendor requests one:

Share general feedback, not exact scores. "Your technical approach scored well, but your implementation timeline was a concern relative to other candidates."
Be constructive. Point out what they did well and where they could strengthen future proposals.
Keep it brief. 15-20 minutes is sufficient. This isn't a negotiation or a second chance.
Don't reveal proprietary information about other vendors' proposals or pricing.

A good debrief takes 20 minutes of your time and builds a relationship that might matter for years. A bad debrief — or no debrief — burns a bridge you might need later.

Common award mistakes

Awarding too slowly

The gap between "we've made our decision" and "the contract is signed" should be days, not months. Every week of delay risks the winning vendor reallocating resources, key team members becoming unavailable, or internal stakeholders losing enthusiasm.

If your organization's contracting process is slow, start it in parallel with the final evaluation — not after.

Not documenting the rationale

"We picked Vendor A" isn't a rationale. "Vendor A scored highest on technical capability and implementation approach, with the strongest reference client outcomes and competitive TCO" is a rationale. Document it. You'll need it when someone asks six months from now why you didn't pick Vendor B.

Letting the award drag into re-evaluation

Sometimes a stakeholder who wasn't involved in scoring tries to reopen the evaluation after the decision. Resist this. If they had input, they should have been part of the process. If they didn't, the decision was made through a structured, defensible process. Re-evaluating based on late opinions undermines the entire RFP framework.

Ghosting the losers

We said it above but it bears repeating. The vendors you don't pick today are the vendors you might desperately need next year. Procurement is a small world. Treat every participant with respect.

Close it clean

A well-run RFP award process takes 1-2 weeks from final scores to signed contract. It results in a motivated winning vendor, respected unsuccessful candidates, documented rationale, and organizational confidence in the decision.

The alternative — a messy, drawn-out, undocumented award — leaves everyone confused, frustrated, and already questioning the choice before the project kicks off. That's how vendor relationships start on the wrong foot and never recover.

For the complete buyer journey from requirements to contract, see the Complete Buyer's RFP Guide.

Strutter handles the full RFP lifecycle from generation through award. Score vendors with AI-assisted evaluation, compare responses side by side, and close your RFP with a structured award workflow — all in one platform.

Run your next RFP from start to finish. It's free to get started.