IT support services agreement, Calder and Roe managed support
IT support services agreement with response times by priority
Managed support is sold on a monthly fee and judged on how fast the phone gets answered when nobody can work. This agreement grades every ticket into four priorities with a published response and resolution target, credits the fee when the target is missed, and writes down exactly what the provider hands back on the way out.
The document, page by page
Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.
Section by section
What each section is for, so you can keep the ones you need and drop the rest.
- Cover and contents
- A contract cover naming the engagement, then a contents list to the seven sections.
- Parties and key terms
- Provider and client, then the monthly fee, the seat count, the P1 response and the notice.
- 1. What is supported
- The devices, tenancy, servers and network in scope, what support means, and desk hours.
- 2. Priorities and response times
- The four level priority table, how a ticket is graded, and the service credit trigger.
- 3. What is not included
- The out of scope list and the rates and written approval that chargeable work needs.
- 4. Fees
- The itemised monthly fee to $2,640 including GST, pro rata seats and the capped annual review.
- 5. Data, security and privacy
- Client ownership, Australian hosting, named accounts, backup testing and breach notification.
- 6. Access, obligations and reporting
- What each side supplies, and the monthly report and quarterly review.
- 7. Ending the agreement and offboarding
- Notice and breach, the 15 day handover list, and the liability cap and dispute path.
- Signatures
- A block for the provider and one for the client.
Clauses in this document
- Cross border data transfer clause
- Cyber security clause: the controls a supplier must keep
- Data breach notification clause
- Data processing clause under UK GDPR Article 28
- Data protection clause
- Data return and deletion clause
- Dispute resolution clause: the ladder before anyone goes to court
- Privacy clause in a service contract
- Reporting obligations clause: what the supplier must tell you, and when
- Service credits clause: what a missed service level costs the supplier
- Service level clause: turning good service into numbers
How to adapt this agreement
For a co managed arrangement where the client has its own IT person, add a responsibility matrix naming who owns each system and change the service desk clause so tickets are triaged internally first. For a client with a compliance obligation such as a medical practice or a law firm, tighten clause 5 with a data residency warranty, a subcontractor approval right and an annual security attestation. For a smaller client under about 10 seats, collapse the four priority levels into two, drop the service credits, and keep the offboarding clause untouched, because that is the clause that protects a small business most when a relationship ends badly.
What makes this document work
Response means a person, not an autoresponder
The priority table sets 30 minutes for P1 and four hours for P3, and clause 2.1 defines response as a named engineer making contact. Miss the P1 target twice in a month and the client takes 10 percent of that month's fee off the next invoice.
Offboarding is written before anyone wants it
Clause 7.2 hands over the asset and licence register, every administrative credential, the network diagrams, the backup configuration and the last full backup set within 15 business days, plus 20 free hours, and says data is not held as leverage over an unpaid invoice.
The fee is itemised, so scale changes are arithmetic
Thirty seats at $62, two servers at $185, network at $110 and backup at $60 add to $2,400 a month and $2,640 with GST. A seat added mid month is $62 pro rata, which needs no negotiation.
Questions people ask
What should an IT support agreement include?
The environment being supported, what support covers and when, response and resolution targets by priority, what is out of scope and what it costs, the fee and how it changes with scale, data handling and security obligations, reporting, and what happens at the end.
What do P1 to P4 priorities mean?
P1 is nobody can work or client data is at risk, P2 is a team blocked with no workaround, P3 is one user with a workaround, and P4 is a request or a question. The table pairs each with a response time and a resolution target so the grading has consequences.
What are service credits?
A rebate when the provider misses its own targets. Here, missing the P1 response more than twice in a month or the P2 target more than five times gives the client 10 percent of that month's fee back on the next invoice, calculated from the ticket system.
Should an IT provider hold the client's credentials?
It needs administrative access to do the work, but the accounts should be named and the client should be able to get everything back. Clause 5.2 requires named accounts with multi factor authentication and logged privileged access, and clause 7.2 hands every credential back on exit.
How are backups verified?
By restoring something. Clause 5.3 sets nightly backups with 30 day retention and a monthly copy held for 12 months, and requires a quarterly restore test on a file, a mailbox and a full server, with the result written into the report whether it passed or failed.
What happens after a suspected data breach?
Clause 5.4 requires a report to the client within four hours of detection covering what is known, what has been contained and what is still unknown. Both parties then follow the client's obligations under the notifiable data breaches scheme, with the provider assisting the assessment.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make my it support services agreement with response times by priorityOther document examples
HVAC maintenance agreement with a visit checklist and a parts cap
Planned maintenance contracts usually fail in the gap between the scheduled visit and the breakdown nobody priced. This one fixes the checklist for both visits, sets a 48 hour response, and gives the contractor a $300 ceiling to fix small things on the spot instead of booking a second trip.
Software development agreement with sprints and an acceptance test
Custom software goes wrong in the space between delivered and accepted, where one side thinks a sprint is finished and the other is still writing a list. This agreement fixes a ten business day acceptance window against criteria written before the sprint started, and assigns the intellectual property sprint by sprint as each invoice is paid.
Translation services agreement with word rates and turnaround bands
Translation is priced by the word and judged by the deadline, so an agreement that names neither is just a handshake. This one puts five language pairs and two rates in a table, bands the turnaround by word count, and says exactly what a certified translation is before anyone argues about whether the authority will accept it.
Want the steps in the builder? Read Create a document with AI, then Layout, spacing and page breaks. For everything this generator can do, see the document maker.
Written and checked by the OneCraft team. Last checked .