How to win a managed IT services RFP: what evaluators actually score

A public managed IT services RFP isn't decided by who runs the best help desk. It's decided by a committee with a scoring sheet, reading your response next to four or five others. Most providers lose points on paper that their service would have earned. Here's what evaluators actually score, and how to write for it.

1. Read the evaluation section before anything else

Almost every public RFP tells you how responses will be scored: a list of criteria, often with points or percentages. That section is the most important page in the document. It tells you where the points are, so it should decide where your effort goes.

Before anyone writes a word, build your outline from it. If the transition plan is worth 30 points and your company history is worth zero, your response should look like it. A common mistake is spending pages on "about us" and a single paragraph on the transition plan the buyer weighted most heavily.

2. Build a compliance matrix first

A compliance matrix is a simple table: every requirement in the RFP in one column, and where your response answers it in the next. Go through the document line by line and capture every "shall," "must," and "provide," plus every required form, signature page, addendum acknowledgment, and page or format limit.

This matters because public buyers often check compliance before scoring. A missing form or an unanswered requirement can get a response set aside as non-responsive, and you may never learn that's what happened. Put the matrix at the front of your response, and evaluators will thank you: it does part of their job for them.

3. Lead with the buyer's priorities, not your history

Most RFPs include a background or scope section that says, in the buyer's own words, what they're worried about: aging infrastructure, after-hours coverage, a cyber insurance renewal, a failed previous vendor. Your executive summary should open by restating those priorities, then show how you address each one.

Compare two first sentences. "Founded in 2009, we are a full-service managed service provider" could be pasted into any proposal. "The City asked for dependable response across six sites and a backup program its insurer will accept" could only be written for this buyer. Evaluators notice the difference immediately.

4. Replace adjectives with evidence

"Best-in-class support" and "industry-leading security" score close to nothing, because every competitor wrote the same words. What scores is evidence a committee can point to:

• Measured response and resolution times, with the period they cover
• Client retention or renewal rates
• Certifications and audit reports you actually hold
• Named references from similar organizations, with their permission
• Specific outcomes from comparable engagements

Most providers already have these numbers in their ticketing system or contracts. They just never make it into the proposal. Only use figures you can verify; an evaluator who catches one inflated number will discount the rest.

5. Make the transition plan concrete

Switching IT providers is risky for a public buyer, and the evaluation committee knows it. A transition plan that says "we will work closely with your team to ensure a smooth onboarding" doesn't reduce that risk. A plan with dated milestones does: discovery and documentation in the first 30 days, tool deployment by site, a cutover approach that avoids business hours, and checkpoints the buyer signs off on. Show the plan as a table or timeline, not a paragraph.

6. Answer in their order, with their numbering

If the RFP asks questions 3.1 through 3.9, answer 3.1 through 3.9, in that order, under those numbers. Don't reorganize the response around how you like to describe your services. Evaluators score with the RFP open next to your response; every time they have to hunt for an answer, you risk losing points for something you actually answered.

7. Make it scannable

Evaluators often read many responses in a short window. Headings that mirror the RFP's sections, service levels in a table, short paragraphs with one idea each, and a clear executive summary all help your best content get found. Design isn't decoration here; it decides whether the strong parts get read.

8. Debrief every result

Win or lose, ask the buyer for a debrief and, where available, the scoring results. Public bid results are often published or available on request. The feedback tells you exactly which criteria cost you points, which is the fastest way to improve the next response.