Covered systems
Start with an inventory of servers, operating systems and applications. Confirm supported versions and any existing constraints.
MANAGED SERVICES
Server management
with an agreed scope.
Choose the systems and maintenance tasks you want covered. Document who approves changes, who responds to issues and which work stays with your team.
Named systemsAgreed responsibilitiesRecorded changes
YOUR MANAGEMENT SCOPEAgree before you deploy
Operations, clearly defined.Example service-planning view
- Review the environmentAssess
- Define the responsibilitiesAgree
- Schedule the maintenancePlan
- Keep decisions recordedReview
The management agreement identifies covered systems, responsibilities, maintenance windows and escalation procedures.
A SERVICE WITH A CLEAR BOUNDARY
What is managed, and by whom?
Start with named systems and recurring tasks. Agree who carries out the work, how changes are approved and what remains your responsibility.
An agreed change process
Identify maintenance tasks, approval requirements and change windows. Keep access, backup and recovery responsibilities explicit.
Scheduled reviews
Document what is checked, how findings are reported and how issues are escalated. Review the scope when the environment changes.
EXPLORE THE MANAGEMENT BOUNDARY
Choose the scope to discuss.
Use this planning matrix to frame your enquiry. It is an example allocation of responsibilities, not an active service agreement.
| Responsibility | Requested scope | What to confirm |
|---|---|---|
| Operating-system patches | Provider scope | Supported OS, approvals and maintenance window |
| Monitoring checks | Provider scope | Signals, alert routes and escalation arrangements |
| Backup operations | Agreed backup policy | Covered data, retention, storage and restore tests |
| Application stack | Customer | Named applications, versions and support exclusions |
| Content, code and user permissions | Customer | Data ownership, authorised contacts and approvals |
| Service review | Scheduled review | Reporting format and agreed review cadence |
Selected focus: Server operations. Final responsibilities are agreed in writing for the named environment.
Discuss this management scopeBEFORE THE FIRST CHANGE
What to include in your management request.
Include the operating systems, applications and work you want covered. Exchange access credentials later through an agreed secure process.
- Server inventory, operating systems and application versions.
- Existing alerts, known issues and operational dependencies.
- Current backup process and recovery expectations.
- Approved contacts, access requirements and change authority.
- Preferred maintenance windows and reporting requirements.
Keep secrets out of an enquiry. Do not include passwords, private keys, API tokens or sensitive customer records in your initial requirements brief.
FROM REVIEW TO ROUTINE
Create an operating plan your team can follow.
Assess the environment
Review the systems, dependencies and current responsibilities before setting the service boundary.
Agree the scope
Document covered tasks, exclusions, access controls, maintenance windows and the process for approvals.
Work from the plan
Record changes, review agreed checks and update the scope when applications or business requirements change.
MANAGED SERVICES QUESTIONS
Understand the service boundary.
Does managed service include application development?
Not automatically. Code changes, new features, content updates and third-party application support must be explicitly included in the agreed scope.
Is monitoring the same as incident response?
No. Define the monitored signals, the notification route and what response work is covered. Detection, acknowledgement and resolution are different parts of an operating agreement.
Who owns the data and access decisions?
The customer retains responsibility for its data, authorised users, application requirements and approval decisions. Any provider access should be limited to the tasks and systems covered by the agreement.
Are backups part of every management scope?
Backup operations are covered only when agreed. Specify the data included, schedule, retention, storage location, restore process and testing responsibilities.
Can management be added to an existing server?
That depends on the current environment and supported systems. Start with a review of the server, software versions, access arrangements and any unresolved issues before scope is confirmed.
Define the support your environment needs.
Bring your system inventory and the work you need help with. Agree the covered tasks, exclusions and responsibilities before the service starts.
