Procurement Document Library / Doc Set 2026
RFPrequestforproposaltemplate.com
Document: RFP-ITMS-004Vertical: IT Managed Services
Industry Template / IT MSP

The IT Managed Services RFP Template That Holds the MSP to Real SLAs and a Documented Transition

IT managed services contracts run for 3 to 5 years, cover thousands of endpoints, and carry security risk that the MSP frequently underprices. This template makes four things explicit: the SLA tiers the MSP commits to, the security framework they operate against, the support model and on-call structure, and the transition plan. Each one has been a source of post-signature surprise on enough engagements to deserve its own RFP section.

Buying a managed SOC or 24x7 security monitoring from an MSP? The SOC requirements in Part II-B (SOC-01 to SOC-06) are written to paste into an MSP RFP as they stand.

Part I / SLAs

Service Level Objectives the MSP Will Actually Hit

MSP SLAs are easy to write and hard to operate. Most MSPs publish standard SLA tables that look identical across the industry; the differentiator is not the published number but the operational posture behind it. The RFP requirement is to specify the SLA by ticket priority, define the priority taxonomy in operational terms (not adjectives), and require the MSP to disclose the SLA achievement percentage they hit for their existing client base over the past 12 months. Vendors who cannot show the data have not measured it.

PriorityDefinitionFirst responseResolution target
P1 (Critical)Production system down; multiple users affected15 min4 hours
P2 (High)Major function impaired; workaround painful1 hour8 hours
P3 (Medium)Minor function impaired; workaround viable4 hours24 hours
P4 (Low)Cosmetic / request / scheduled change1 business day5 business days

Service credits if missed: a starting position to propose is 5 percent of the monthly fee per missed P1 and 2 percent per missed P2, capped at 25 percent of the monthly fee in any month. These are draft terms for negotiation, not an industry standard. Demand monthly reporting on SLA attainment with raw ticket data accessible to the client, not just the summary number. Reference frameworks: ITIL 4 service management, NIST SP 800-145 for cloud terminology if the MSP includes cloud operations.

Part II / Security

Security Controls and the Framework They Map To

MSPs are increasingly the attack vector in supply chain breaches. The 2021 Kaseya / REvil incident remains the canonical example: a single MSP RMM tool compromise affected 1,500 downstream organisations. The RFP requirement is not just that the MSP follows good security practice but that they operate against a recognised framework with auditable evidence.

SEC-01

NIST CSF 2.0 alignment

MSP maps their operating practices to the six NIST CSF functions (Govern, Identify, Protect, Detect, Respond, Recover). They provide a self-assessment scorecard against each function and disclose where they are externally audited vs self-attest. The 2024 update to CSF added Govern as an explicit function; require the MSP's mapping to use the 2.0 version.

SEC-02

CIS Controls v8 evidence

Top 18 CIS Controls operationalised across the MSP's tool stack. Particularly important: Control 5 (account management), Control 6 (access control), Control 8 (audit log management). Ask for the MSP's CIS Controls Self-Assessment Tool output for the past 12 months.

SEC-03

RMM tool security posture

The MSP's remote monitoring and management tool is the attack surface that matters most. Ask: which RMM (ConnectWise Automate, NinjaOne, Datto RMM, Atera, etc.), the MFA enforcement on RMM admin access, the privileged-access management for technician credentials, and the most recent vulnerability disclosure response time for their RMM vendor.

SEC-04

SOC 2 Type II report

MSP carries a SOC 2 Type II report covering the period including the past 6 months minimum. Provided under NDA. Particularly relevant trust service criteria: Security (mandatory), Availability (relevant given the SLA commitments), Confidentiality (relevant given client data access).

SEC-05

Incident response plan

MSP's documented IR plan including: detection capability (EDR, SIEM, logs), escalation matrix, customer notification SLA (typically 24 hours for security incidents affecting client data), and the post-incident review process. Plan tested annually (tabletop exercise or full simulation).

SEC-06

Backup + recovery testing

Specific to client data and infrastructure managed by the MSP: backup frequency, retention, encryption, off-site copies, and quarterly restore testing. The MSP should restore a sample restore monthly as a routine practice, not just on incident.

Reference documents: NIST CSF 2.0, CIS Controls v8, and CISA on protecting against MSP supply-chain threats.

Part II-B / Managed SOC

SOC RFP Requirements for MSPs: Managed Detection and 24x7 Monitoring

Many MSPs now bundle a security operations centre (SOC) service, and some resell a third-party SOC under their own name. The RFP has to pin down who watches the alerts, which logs they see, what they are allowed to do without asking, and how you measure them. Two terms collide here: a SOC 2 report is an AICPA attestation on the MSP's own controls (SEC-04 above); a SOC is the team and tooling that monitors yours. Ask for both.

SOC-01

Coverage and staffing

MSP states the hours the SOC is staffed (not just alerting), where analysts sit, and whether the SOC is operated by the MSP's own employees or a named subcontractor. If subcontracted, the subcontractor is named in the response and bound by the same confidentiality and security terms.

SOC-02

Log sources and data ownership

MSP lists the log sources it will ingest (identity provider, EDR, firewall, email and collaboration suite, cloud control plane, critical servers), the SIEM or XDR platform used, the retention period you require, and who owns the tenant and the log data at contract exit.

SOC-03

Detection and response metrics

MSP reports monthly mean time to detect, acknowledge and contain, calculated from raw alert data you can inspect. The response defines what 'respond' means: notify only, or take containment action. Bidders state the targets they will commit to contractually.

SOC-04

Pre-approved response actions

A written runbook of actions the SOC may take without client approval (isolate an endpoint, disable an account, block an IP or domain), the actions that need approval, and the out-of-hours escalation contacts on both sides.

SOC-05

Detection engineering and threat hunting

MSP describes how detections are written and tuned, how often proactive threat hunts run, and maps its detection coverage to MITRE ATT&CK techniques relevant to your environment.

SOC-06

Incident notification and evidence

Notification timeline for confirmed incidents set to meet your own regulatory and contractual obligations (state breach laws, sector regulators, cyber insurance terms), with forensic evidence preserved and handed over on request.

Reference documents: MITRE ATT&CK and the AICPA SOC 2 overview.

Part III / Support Tiers

The L1 / L2 / L3 Tiering, and What Actually Lives at Each Level

Every MSP claims a tiered support model. The differentiator is which tickets resolve at L1 vs escalate: a high escalation rate means slower resolution, more handoffs, and higher overall cost. Ask the MSP to disclose their actual L1 resolution percentage from the past 12 months and the distribution of ticket types across tiers.

The model the RFP should anchor on:

  1. L1 (help desk). Password resets, basic account management, software install issues, common how-to questions, hardware swaps. Ask for the share of tickets L1 closes on first contact. Staffed during business hours plus on-call rotation overnight.
  2. L2 (technical support). Server issues, network troubleshooting, application errors requiring vendor escalation, security alert triage. Handles tickets that L1 cannot close within 30 minutes.
  3. L3 (engineering / architecture). Infrastructure design, complex troubleshooting requiring root cause analysis, project work, change management for infrastructure modifications. Engaged for tickets L2 cannot resolve, plus all proactive engineering and project work.
  4. vCIO (virtual CIO). Quarterly business review, technology roadmap, budget planning, vendor management. Strategic layer above day to day operations. Ask the MSP to state the hours per month included in the retainer.
Part IV / Transition

The 90-Day Transition Plan

Transitioning to a new MSP is high risk. The new MSP does not yet understand your environment; the old MSP has limited motivation to support the handover. A documented transition plan in the RFP avoids the worst-case scenario where the new MSP turns up day one with no documentation and the old MSP has already disabled their accounts.

Days 1 to 14: Discovery + documentation

MSP shadows existing IT operations, conducts environment discovery (Lansweeper or similar tooling deployed), and produces an as-built network and infrastructure document. Old MSP cooperation is required; build a contractual exit-assistance clause into the outgoing contract before issuing the new RFP.

Days 15 to 30: Tooling deployment

MSP deploys their RMM, MDM, EDR, and backup tooling onto your environment. Old tooling continues to run in parallel. PSA (professional services automation) configured for ticket intake. Initial knowledge-base population from discovery.

Days 31 to 60: Parallel operation

Both MSPs receive tickets; new MSP takes increasing share. Daily handover calls. Runbook documentation refined as edge cases surface. Outgoing MSP contractually committed through day 60 (typically a 30-day extension at standard rate).

Days 61 to 75: Cutover

New MSP takes full responsibility. Old MSP available on a defined consultation basis for previously-undocumented issues, typically at hourly rate. Cutover communication to all internal users on a defined date.

Days 76 to 90: Stabilisation

Heightened monitoring of SLA attainment and ticket categorisation. Weekly review meetings between client and new MSP. End-of-period review confirms transition successful or identifies gaps for remediation.

Part V / Pricing

Per-Endpoint Pricing With Honest Inclusion / Exclusion

Per endpoint pricing is the cleanest model. MSPs do not publish a common rate card, so the bids themselves are your benchmark. What moves the rate is inclusion: does the rate cover unlimited tickets or a capped allotment, is after hours included or upcharged, is project work bundled or billed separately. The RFP requirement is a transparent breakdown of what each per endpoint dollar buys.

See the master template at requestforproposaltemplate.com and the broader scoring guidance at RFP Evaluation Criteria.

Part VI / FAQ

Frequently Asked Questions

Q.How is MSP pricing typically structured?+
A.Three common models. Per-user or per-device pricing (a monthly rate per seat) is simplest and most predictable. Per-server or per-instance pricing is common for infrastructure-focused MSPs. All-you-can-eat block pricing is a flat monthly fee covering everything within a defined scope. There is no published market rate: MSPs quote, and the rate moves with what it includes (ticket allowance, after-hours cover, security tooling, project work). Ask every bidder to normalise its price to a per-endpoint monthly figure with the same inclusions listed, so the bids compare.
Q.What should a SOC RFP for an MSP include?+
A.Six requirements: SOC staffing hours and whether the SOC is the MSP's own or a named subcontractor; the log sources ingested, the SIEM or XDR platform and who owns the data at exit; monthly time-to-detect, acknowledge and contain reported from raw alert data; a runbook of response actions the SOC may take without approval; detection engineering mapped to MITRE ATT&CK; and an incident notification timeline that meets your own regulatory obligations. Ask separately for the MSP's SOC 2 Type II report, which covers the MSP's own controls.
Q.Should I require a co-managed or fully outsourced model?+
A.Depends on internal IT capacity. Fully outsourced (MSP owns everything from helpdesk to architecture) suits organisations with no internal IT or with a small team that wants to focus on strategy. Co-managed (internal team owns user experience and strategy; MSP owns tooling, monitoring, after-hours, and specialist domains) suits larger organisations and is the more common 2026 model. The RFP should specify which model and let MSPs that do not operate in that model self-disqualify.
Q.What security framework should the MSP follow?+
A.NIST CSF 2.0 is the practical default. It covers Identify, Protect, Detect, Respond, Recover, and Govern. CIS Controls v8 maps neatly to it and is more prescriptive for implementation. ISO 27001 is common in EU contexts. Ask the MSP which framework they operate against, where they self-attest vs where they are independently audited, and how they report security posture to clients. Generic 'we follow best practices' answers are red flags.
Q.What SLA targets are realistic for help desk and incidents?+
A.First response: P1 (system down) 15 minutes, P2 (major impact) 1 hour, P3 (minor impact) 4 hours, P4 (request) 1 business day. Resolution: P1 4 hours, P2 8 hours, P3 24 hours, P4 5 business days. Treat these as a starting position for your draft, not a market benchmark: bidders will counter-propose, and tighter P1 and P2 targets usually cost more.
Q.How long should the transition / onboarding take?+
A.60 to 90 days for a typical mid-market organisation (100 to 500 endpoints). Phases: discovery and documentation (2 weeks), tooling deployment (2 to 3 weeks), parallel run (2 to 4 weeks), cutover (1 week), stabilisation (4 weeks). A 30-day transition usually means the MSP skipped discovery and will be relearning your environment during incidents.
Q.How do I evaluate MSPs that all claim 24/7 support?+
A.Ask: where the after-hours team sits geographically, whether after-hours is staffed by the same engineers as business hours or a separate team, what the after-hours escalation looks like, and what percentage of tickets are resolved at the L1 vs escalated. Many MSPs technically offer 24/7 via a small night-shift team that only triages, then waits for the day shift to resolve. Honest disclosure of staffing patterns is more useful than a 24/7 marketing claim.
Related Industry Templates

Other industry RFP templates