How to Write an RFP Rejection Letter That Doesn't Burn Bridges
Templates and guidance for writing RFP rejection letters that are professional, specific enough to be useful, and preserve vendor relationships for future opportunities.
The vendor rejection is the part of the RFP process most teams handle worst. Either the letter is so vague it tells the vendor nothing, or it disappears entirely and vendors are left waiting without any notification at all.
Both approaches damage your organization's reputation in ways that take time to see. Vendors talk to each other. Markets are smaller than they appear. The company you reject today may be a critical supplier in three years, or may be at the table when you run your next RFP.
A good rejection letter takes fifteen minutes to write. Here is how to do it well.
Why most rejection letters fail
The most common rejection letter looks like this:
"Thank you for participating in our RFP process. After careful review, we have selected another vendor. We appreciate your time and effort and wish you the best."
This tells the vendor nothing useful. It does not explain why they were not selected, whether they were close, or what they could do differently. It reads as dismissive because, structurally, it is.
The second-most-common outcome is no communication at all. The vendor submits, follows up once or twice, and eventually concludes they were not selected. This is worse than a vague letter. It signals that your procurement process does not respect vendors' time, and that impression will reach other vendors in the market.
Timing: send the rejection before the vendor asks
The right time to send rejection letters is when you notify the winning vendor, or within 48 hours. Do not wait for vendors to follow up. The moment your team decides on a winner, the non-selected vendors should be notified.
Delayed rejections are frustrating for vendors who have budgeted time and resources based on a potential win. They also reflect poorly on your organization's ability to manage a process.
If your selection is delayed for internal reasons, send an interim note: "Our evaluation is taking longer than expected. We expect to make a final decision by [date] and will notify all vendors at that time." That takes two minutes and prevents vendors from following up repeatedly.
What to include in the rejection letter
A good rejection letter covers four things:
1. The outcome, stated clearly at the top. Do not bury the news. The vendor needs to know in the first sentence whether they were selected. "After completing our evaluation, we have selected a different vendor for this engagement" is clear. "We wanted to reach out regarding the outcome of our recent RFP process" is not.
2. A brief, honest reason. You do not need to share your full evaluation scores or a detailed critique. But a single sentence about the primary factor in the decision is genuinely helpful: "Our selection was based primarily on [pricing, technical fit, implementation timeline, compliance requirements, or specific capability]." This gives the vendor something to act on.
3. An acknowledgment of their specific effort. If the vendor submitted a thorough response, say so. "Your proposal was detailed and your security documentation was particularly strong" is worth including. It is true (or you would not include it), and it signals you read their submission carefully.
4. A door for the future. If there is any genuine possibility of working together in the future, say so. "We plan to revisit this category in 18 months and will be in touch when we do." If there is not, do not say it.
What not to include
Do not be dishonest about the reason. If you selected a vendor because they were 40% cheaper and that was the deciding factor, say that. "Pricing" is a legitimate answer. Do not invent a technical reason if pricing is the real one. Vendors often know more about competitive pricing than you expect, and a fabricated reason erodes trust.
Do not over-explain. A rejection letter is not a debrief. One sentence on the primary reason is appropriate. A paragraph explaining every factor in your evaluation is more than the situation requires and invites argument.
Do not make promises you will not keep. "We will definitely consider you for future opportunities" is an empty statement if you have no current RFPs on the horizon. "We will keep your information on file" means nothing to a vendor. Be specific or say nothing about the future.
Do not copy-paste the same letter to every vendor. You do not need a fully customized letter for each rejection. But using the exact same template for every vendor, including the same "we were very impressed" language regardless of the actual quality of the response, is transparent and unhelpful.
Templates by scenario
Scenario 1: Close second (vendor was seriously considered)
Subject: [RFP Name] Outcome Notification
[Vendor Name],
Thank you for the time your team invested in our [RFP Name] process. After a thorough evaluation, we have selected [or: we have made our final selection] for this engagement.
Your proposal was competitive. Our decision came down to [one sentence: pricing, a specific technical capability, an implementation timeline, compliance certification]. This was a close evaluation and your submission was strong.
We are running a similar process for [related area or timeframe] and will reach out when that opens. We would welcome the opportunity to work together in the right situation.
Thank you again for your participation.
[Name, Title]
Scenario 2: Did not meet a key requirement
Subject: [RFP Name] Outcome Notification
[Vendor Name],
Thank you for participating in our [RFP Name] process. We have completed our evaluation and selected a vendor for this engagement.
Your response was thorough, and we appreciate the detail your team provided. Our selection was based primarily on [the specific requirement: SOC 2 Type II certification, an existing integration with our ERP platform, geographic support coverage]. This was a mandatory requirement for our procurement.
We appreciate your participation and wish your team continued success.
[Name, Title]
Scenario 3: Poor overall fit (pricing, scope, capability)
Subject: [RFP Name] Outcome Notification
[Vendor Name],
Thank you for submitting a response to our [RFP Name] RFP. We have completed our evaluation and selected a different vendor for this engagement.
Our decision reflected [a one-sentence summary: a combination of pricing and the specific capabilities we prioritized, or: the match between your offering and our specific requirements]. We appreciate the time your team invested in the response.
We will keep your information for future consideration when we have a need that may be a stronger match.
[Name, Title]
Handling debrief requests
Vendors who were competitive will sometimes request a debrief. This is a reasonable request and you should accommodate it when possible.
A good debrief call lasts 20-30 minutes. Cover: where the vendor scored well, the primary factor in the decision, and one or two specific areas where a stronger response would have helped their score.
You are not obligated to share other vendors' pricing or scores. You are not obligated to justify your decision in detail. The goal of a debrief is to give the vendor useful feedback they can apply to future proposals, not to defend your selection.
What you should not do in a debrief: tell the vendor they were the right choice but lost for internal politics reasons, or that they would have won if pricing had been 10% lower. Both statements invite negotiation and create false expectations about future opportunities.
For a complete buyer workflow from RFP creation through award, see the RFP Process Step by Step guide.
The operational side
In Strutter AI, you can close an RFP and mark a winner without sending rejection letters from the platform. That part happens outside Strutter, in your regular email.
What Strutter does give you: a complete record of each vendor's scores and the evaluation rationale. This makes writing a specific, accurate rejection letter faster. Instead of relying on memory about why Vendor B was not selected, you have their scores, the AI-generated rationale, and the comparison matrix to reference.
A rejection that took your team three weeks to get around to writing because someone had to reconstruct the evaluation from memory is a rejection that reads as an afterthought. A rejection that goes out within 48 hours with a specific reason is one that vendors remember positively.
Run your next RFP in Strutter and have the documentation ready when it is time to close.