Prepare a brief that reflects ordinary work
Include approximate user and device numbers, main applications and working arrangements. Describe recurring issues through their business effect, such as staff being unable to use a shared application.
Add planned changes separately. A device rollout or email migration may need a project scope alongside the ongoing support proposal.
If you have an internal IT contact or a specialist application supplier, identify their responsibilities. This helps avoid comparing one proposal for complete support with another for limited additional help.
Ask how the support process would work
Request clear answers to these questions:
- Which systems and request types are included?
- What support hours and communication routes are proposed?
- How are priorities, escalation and onsite requirements handled?
- Who approves access and system changes?
- Which tasks remain with your business or another supplier?
Distinguish an acknowledgement from investigation and resolution when reviewing response commitments. Ask what happens outside the included hours and where those arrangements are documented.
For an initial scope discussion, our managed IT support page sets out the details to prepare.
Compare the full proposal
Look at setup work, recurring charges, licences, additional requests and projects. Check how new users or devices would affect the arrangement. Avoid judging value from the headline charge alone.
Ask for relevant evidence of suitability for the systems in scope. Consider the proposed security responsibilities and data handling arrangements separately from general statements about service quality.
Where a specialist application remains outside scope, clarify who coordinates with its supplier. That dependency may matter more to your business than a longer list of supported products.
Plan the start and the eventual handover
Before changing arrangements, establish what records are available, who owns them and how outstanding work will be transferred. Describe those records in early discussions without sending credentials or confidential files.
Ask how documentation and unresolved requests would be handed back if the arrangement later changed. A clear start is useful, but an unclear exit can leave important responsibilities unsettled.
Use the contact form to describe the support arrangement you want to discuss, including your current scope and any deadline for a change.