What to Expect in the First 90 Days of a Managed Service

Signing a managed services agreement is only the beginning. The first few months decide whether the service settles into reliable, predictable operation or becomes a source of frustration for your teams and users.

Every transition is different, and timelines are agreed during scoping. But a well-run transition usually follows a recognizable pattern. Knowing what to expect helps you prepare your team, ask the right questions and spot problems early.

Before day one

Preparation starts before the service does. Both sides should agree:

• The exact scope: which systems, applications, users and locations are included
• Service levels for response and resolution, and how they will be reported
• Escalation paths and named contacts on both sides
• Access arrangements and security requirements
• How the transition will be governed and how progress will be reported

Unclear scope is the most common cause of early disagreements. Time spent here avoids disputes later.

Phase one: transition

The first phase focuses on knowledge transfer. The provider's team learns your environment, systems and ways of working, usually alongside the people or provider currently responsible.

During this phase, expect:

• Workshops and shadowing sessions with your current team
• Review and creation of documentation, runbooks and contact lists
• Setup of access, monitoring and ticketing integration
• Agreement on how incidents and requests will be logged and prioritized

Your team's time is essential here. Plan for key people to be available, because knowledge that is not transferred becomes a risk later.

Phase two: stabilize

Once the provider takes on day-to-day responsibility, the focus shifts to stability. Recurring issues are identified and resolved, gaps in monitoring or backups are closed and procedures are confirmed in practice.

Some disruption is normal at this stage. New people are handling familiar problems for the first time, and undocumented knowledge comes to light. What matters is how quickly issues are recognized, communicated and resolved.

A good provider will report openly on what they find, including problems that existed before the transition, and propose how to address them.

Phase three: operate

By this point, the service should be running to agreed service levels, with regular reporting. The first formal service review is an important milestone. It should cover:

• Performance against service levels
• Incident and request trends
• Open risks and issues
• Improvement recommendations and agreed actions

The first review sets the tone for the relationship. Look for reporting that explains what happened and why, not just numbers.

What your team needs to provide

A managed service reduces your operational workload, but it does not remove your responsibilities entirely. Your team will still need to:

• Make decisions on priorities, changes and approvals
• Provide access and information when requested
• Attend service reviews and act on agreed recommendations
• Keep the provider informed about business changes that affect the service

Assign a named service owner on your side. Without one, decisions are delayed and accountability becomes unclear.

Warning signs to watch for

Most transitions have some difficulties. These signs suggest a more serious problem:

• Documentation is not being created or updated
• The same incidents recur without root cause analysis
• Reports show numbers without explanation or actions
• Escalations take longer than agreed
• Key people on the provider's side change frequently without handover

Raise concerns early through the agreed governance. Problems are much easier to fix in the first months than once patterns are established.

Questions to ask your provider

Before and during the transition, it is reasonable to ask:

1. What does your transition plan include, and what do you need from us?
2. How will you report progress during transition?
3. When will you take full responsibility, and what conditions must be met first?
4. How do you handle issues that existed before the transition?
5. What will the first service review cover?

A structured transition protects your users and your business. With clear scope, committed people on both sides and transparent reporting, the first 90 days lay the foundation for a service that improves over time.