Key takeaways
- Define scope and exclusions precisely: ambiguity is where disputes start.
- Use measurable targets per priority and report them regularly.
- Agree responsibilities, change handling and security duties in writing.
- Plan the exit before you sign: documentation, data return and transition support.
Scope and exclusions
List exactly which systems, users, locations and services are covered, and which are not. Include the assumptions the price is based on, such as the number of users or devices.
Service levels that can be measured
Good service levels are specific and verifiable:
- Priority definitions with examples.
- Response and resolution targets per priority, and the hours they apply.
- Availability targets for monitored systems where relevant.
- How remedies work if targets are missed.
Reporting and reviews
Agree what is reported, how often and in which format, and hold regular service reviews. Reports should show performance against targets, trends and recommendations, not just activity.
Responsibilities and change handling
Write down who does what: the provider, your team and any third parties. Define how changes are requested, approved and tested, and who owns security tasks such as patching, access reviews and backups.
Exit and transition
Before you sign, agree how the contract ends: notice periods, documentation you receive, return or deletion of data and support during the hand-over. A fair exit clause is a sign of a confident provider.
Red flags
Be cautious when you see:
- Vague scope with open-ended extras billed by the hour.
- Targets without measurement or reporting.
- No clear data ownership or exit terms.
- Reliance on subcontractors that is not disclosed.