CONSULT CIRCLE | IT PROCUREMENT
The sections a managed services RFP needs, the questions that reveal capability, and a scoring model that resists a polished response.
Managed services RFPs frequently select the best proposal writer rather than the best provider. That happens when questions invite description instead of evidence, and when scoring rewards completeness of answer rather than quality of answer.
This template is structured to make that harder. The questions are ones a capable provider answers easily and a weak one cannot answer specifically.
RFP structure
| Section | What to include | Why |
|---|---|---|
| 1. Background | Who you are, why you are going to market, and the timeline | Providers who understand the driver propose more appropriately |
| 2. Current environment | Estate size, technologies, locations, user numbers, ticket volumes | Vague inputs produce padded prices and later change requests |
| 3. Scope of services | Explicitly in scope and explicitly out of scope | Ambiguity here becomes a dispute during service |
| 4. Service levels | Response and resolution targets by priority, and hours of cover | Sets the bar you are actually buying against |
| 5. Transition | Expected onboarding approach, knowledge transfer, timeline | Transition is where managed services engagements most often go wrong |
| 6. Commercial | Pricing model, what triggers additional charges, indexation | Prevents surprises after signature |
| 7. Response requirements | Format, page limits, submission deadline | Comparable responses are far easier to score fairly |
| 8. Evaluation criteria | Published weightings | Publishing them improves response quality and defends the decision |
Table 1 — RFP section structure.
Questions that reveal capability
These are harder to answer generically than the standard questions, and the difference between responses is informative.
- Describe your transition approach for an environment of our size, with a week-by-week plan and what you need from us.
- What happens in the first thirty days if we discover the environment is not as documented?
- Give an example of a service level you missed in the last year and what changed as a result.
- Who specifically will work on our account, what are their qualifications, and what else are they assigned to?
- How do you handle a P1 outside business hours? Walk through the actual sequence, including escalation and who is woken.
- What is explicitly not included, and what would be charged separately?
- How do you hand back at the end of the contract, and how long does that take?
- What tooling will you deploy in our environment, who owns the data in it, and what happens to it at exit?
- How do you keep documentation current, and can we see a sample of what we would receive?
- Provide two references for engagements of comparable size that ended, as well as ones that continue.
The question that separates providers: Asking about a missed service level. Strong providers answer it directly, describe what changed and move on. Weak ones claim never to have missed one, which is either untrue or means they have not run at scale.
Evaluation criteria and weighting
| Criterion | Suggested weight | What you are assessing |
|---|---|---|
| Technical capability | 25% | Genuine depth in your technologies, evidenced by named people and comparable work |
| Service delivery model | 20% | How support actually works: triage, escalation, out-of-hours, continuous improvement |
| Transition approach | 15% | A specific plan for your environment, not a generic methodology |
| Commercial | 20% | Total cost over the term including likely extras, not headline monthly price |
| References and track record | 10% | Comparable size and sector, including engagements that have ended |
| Cultural and operational fit | 10% | Whether the people you met will be the people you get |
Table 2 — Suggested evaluation weighting.
Adjust the weights to your situation, but publish them. Publishing weightings improves the quality of responses and makes the decision defensible afterwards.
Scoring that resists polish
- Score against evidence provided, not against assertions made. “We have deep expertise” scores nothing without something behind it.
- Score each question independently before forming an overall view of the bidder, to limit halo effects.
- Use more than one evaluator and reconcile differences by discussion rather than by averaging.
- Weight the transition plan heavily. Most managed services relationships that fail, fail during transition.
- Model total cost over the full term including expected out-of-scope work, not the monthly headline.
- Meet the people who would actually deliver, not only the bid team.
- Take references yourself and ask specifically what has gone wrong and how it was handled.
The most common procurement error: Selecting on monthly price without modelling what falls outside scope. A lower headline with a narrow scope routinely costs more over three years than a higher price that includes what you actually need.
Related reading
- Managed services vs self-managed in the cloud: ROI and operational tradeoffs
- Monitoring and observability for integration flows
- IT Procurement Services and Monitoring as a Service
Frequently asked questions
What should a managed IT services RFP include?
Background and drivers, a detailed description of the current environment, explicit scope in and out, service levels, transition expectations, the commercial model, response format and published evaluation criteria.
How long should an RFP process take?
Typically eight to twelve weeks from issue to award for a mid-sized engagement, allowing three to four weeks for responses, time for clarification, presentations and reference calls. Compressing it tends to favour incumbents and large bidders.
How many providers should we invite?
Four to six is usually right. Fewer limits comparison; more creates an evaluation burden that leads to superficial scoring.
Should we publish our budget?
Publishing a range usually improves responses, because bidders propose an appropriate solution rather than guessing. Publishing an exact figure tends to attract proposals priced at it.
What is the most important evaluation criterion?
For most organisations, the transition approach. Technical capability matters, but managed services relationships most often fail in the first ninety days, and a specific transition plan is the best available predictor.
Talk to Consult Circle
We support IT procurement, including requirement definition, RFP preparation and evaluation — and we are happy to advise even where we are not bidding.
Book a free 30-minute call - 0203 916 5593 - info@consultcircle.com