An IT support agreement should be understandable to the people who depend on it. If staff cannot tell which requests are supported, or managers cannot tell who owns a problem, the service will feel inconsistent even when individual tickets are resolved well. Clarity begins with a scope you can use.
A usable support scope tells people how to get help, who can approve change and where responsibility ends.
Define the supported environment
List user devices, operating systems, network equipment and cloud services. Identify specialist applications and suppliers whose involvement may be required. Include remote work and shared workstations where relevant. Record exclusions without burying them in generic wording. The inventory does not need to be perfect on day one, but there should be an agreed way to update it as the estate changes.
Agree access to help
Set out support hours, contact methods and the information users should provide. Define how urgent incidents are distinguished from routine requests. Explain who can authorise new accounts, access changes and purchases. Requests from unverified people should not automatically become changes to the environment. A clear approval route makes support more predictable and helps the provider understand which business decisions it can act on.
Separate incidents from planned work
Restoring an existing service is different from designing a new office network or migrating an application. Ask how changes and projects are assessed, quoted and approved. Also discuss recurring tasks such as patching, account administration and device lifecycle reviews. Naming these activities helps avoid the familiar situation in which both parties assume the other is dealing with an important task.
Review patterns, not just ticket totals
A ticket count can show workload but does not explain whether the business is improving. Look at repeated problems, affected users, avoidable delays and actions completed since the previous review. Connect the findings to a small set of priorities. If the same issue keeps returning, discuss ownership of the underlying fix rather than celebrating that each individual ticket was closed.
PUT IT INTO PRACTICE
Your starting checklist.
Use these prompts to prepare your next decision or conversation.
YOUR NEXT STEP WITH IT MOUNTAIN
Turn the question into a plan.
Discuss your working day with IT Mountain. We can help turn the systems and tasks you depend on into a clearer service proposal.
