Decide what managed means for your service.
Begin with the estate: servers, cloud accounts, websites, databases, control panels and dependencies. Record the provider, customer and application supplier responsible for each layer. Operating-system administration, application maintenance and business support are different tasks, even when they affect the same outage.
A management proposal should identify included work, exclusions, approved access and the service hours. Public cloud operations, enterprise web hosting and outsourced server support can require different boundaries. The NCSC shared-responsibility model provides a useful basis for these discussions.
Turn recurring work into owned tasks.
Agree the maintenance calendar, monitoring checks and routine reviews before onboarding. Identify who responds to an alert, who authorises a restart and how an application owner confirms that a change worked. Record the route for urgent work outside a planned window.
The operating schedule can cover patch coordination, capacity reviews, backup checks, certificate renewals and supplier escalation where included. Each item needs an owner and completion evidence. A dashboard alone does not establish that someone has investigated or resolved its findings.
Keep the service understandable.
Prepare a service inventory, access register, dependency diagram and practical runbooks for common tasks. Useful documentation includes the business purpose, critical integrations, recovery sequence and contacts who can approve disruptive actions. Credentials belong in an agreed secure system rather than a general handover document.
As environments change, update the records and explain exceptions. Review repeated incidents, unresolved capacity constraints and tasks delayed by missing permissions. These are operational decisions to address with the customer, rather than issues that disappear when a ticket is closed.
Start with an agreed baseline and handover.
An onboarding review identifies inherited problems, supported software versions and access or recovery gaps. Agree the work needed to reach the accepted baseline, then separate that project from ongoing management. Existing technical debt should remain visible in the service record.
For a proposal, share an approximate estate size, platform types, current management arrangements and the tasks you want covered. BLCS Global confirms the available scope, responsibilities and commercial terms before work starts. Application changes and third-party products are included only where specifically agreed.
