Most disputes between businesses and their IT provider trace back to the same cause: the agreement never actually defined what was included. A managed IT services agreement should leave very little to interpretation - here's what a properly written one covers.
Scope of Services
This is the section that determines everything else. It should list, specifically, what's covered:
- Helpdesk support - unlimited, or capped at a number of hours or tickets per month
- Which devices and systems are covered - workstations, servers, mobile devices, network hardware
- Patch management and monitoring - what's proactively maintained versus reactively fixed
- Cybersecurity inclusions - endpoint protection, email filtering, MFA management
- Backup management - configuration, monitoring, and test restores
- On-site visits - included, or billed separately by the hour or callout
Vague scope language like "IT support services as required" is the single biggest cause of disputes down the track. If it isn't listed, assume it isn't included, and get that confirmed before signing.
Response Times and SLAs
A proper agreement defines response time targets by priority level - typically something like 15 minutes for a critical outage, one hour for high-priority issues, and same or next business day for low-priority requests. It should also state what happens if those targets are missed. Read our full breakdown of managed IT response times and SLAs for what's realistic to expect.
What's Explicitly Excluded
Exclusions matter as much as inclusions. Common items left out of standard agreements include major projects (like office moves or server migrations), third-party software vendor issues, hardware replacement costs, and after-hours support outside a defined window. None of these being excluded is unreasonable - the problem is when they're excluded silently and only discovered when you're billed for them.
Pricing Structure
Confirm whether pricing is per user, per device, or a flat fee, and what triggers a price change - adding staff, adding locations, or annual CPI increases. See our guide on what managed IT actually costs in Perth for typical market rates to benchmark your quote against.
Data Ownership and Portability
The agreement should state explicitly that your business owns its data, configurations, and documentation - not the provider. It should also specify what happens to that data and access on termination: a defined handover period, not indefinite provider control. This clause is easy to skip past when you're signing with a new provider you trust, but it's the exact clause that matters most if the relationship later breaks down. See our guide on who owns your IT documentation, accounts, and domains.
Exit and Termination Terms
Look for a defined notice period (30 to 90 days is standard), what happens to prepaid fees if you leave mid-term, and an explicit obligation for the provider to hand over documentation and access on exit. A contract that's easy to enter but vague about exit is worth a second look before signing.
Insurance and Liability
Confirm the provider carries professional indemnity and cyber liability insurance, and check what the agreement says about liability caps if something goes wrong on their watch - a ransomware incident during a period of known unpatched vulnerabilities, for example. This won't be the deciding factor in choosing a provider, but it's worth knowing before you need it.
Frequently Asked Questions
What's a reasonable notice period to exit a managed IT agreement?
30 to 90 days is standard in the Perth market. Anything longer than 90 days is worth questioning, and a contract with no defined exit process at all is a red flag regardless of the notice period stated.
Should hardware and software costs be included in the monthly fee?
It varies by provider and it isn't automatically wrong either way, but the agreement should say explicitly which costs are bundled into the per-user fee and which are billed separately. The problems arise when this is left vague and disputed later.
What happens if my provider misses their stated response times?
A properly written agreement defines this, usually as a service credit or fee reduction for the affected period. If your agreement states response times but has no consequence for missing them, the SLA is effectively a marketing claim, not a binding commitment.
Can I negotiate a managed IT services agreement, or is it take-it-or-leave-it?
Most terms are negotiable, particularly around scope, minimum contract length, and exit notice. Response time SLAs are usually fixed since they reflect what the provider can realistically staff to, but it's still worth asking before assuming a term is non-negotiable.
Our managed IT agreements spell out scope, response times, and exit terms in plain English - no vague clauses to catch you out later.
Managed IT Services →Reviewing a managed IT agreement before you sign?
Call 0433 087 091 - we're happy to look over a competitor's proposal and flag anything worth questioning, no obligation.
Get a Free Quote ReviewFor related reading, see our guides to comparing IT provider quotes properly and co-managed IT services.