By Steadnet Cyber · 15 September 2026
Build a usable inventory
List users, primary devices, key applications, subscriptions and shared infrastructure. Record the owner of each system and whether access depends on an existing supplier. An incomplete list makes the handover harder to scope.
Agree responsibilities before access changes
Decide who administers accounts, approves changes, handles new starters and leavers, and contacts other vendors. Confirm the outgoing and incoming responsibilities so a task does not fall between providers.
Plan access carefully
Use named accounts and appropriate permissions. Transfer credentials through an agreed secure route. Check account recovery and ownership before removing existing access, and record the agreed change sequence.
Distinguish routine work from remediation
An initial review may identify outdated devices, missing documentation or configuration work. Onboarding and remedial projects should be separately quoted. A monthly support agreement should state which routine tasks are included.
Set the service expectations
- Coverage and communication routes.
- Response targets and escalation responsibilities.
- Endpoint patching and administration scope.
- Reporting and review frequency.
- Backup responsibilities and third-party dependencies.
Keep an agreed handover record and review it when your systems or team change. International teams should also agree time-zone expectations.