Choose IT care with a clear scope
A single fault, recurring workplace care and complete operation need different offers. Affected users, systems and tasks matter, as do responsibilities retained by your organisation.
Describe needs and environment
State the reason, user count and main systems. Computers, mobiles, networks, servers and cloud applications have different prerequisites. List known platforms and sites in one short common brief.
Describe impact without guessing a technical cause. One workstation without internet differs from an organisation-wide outage. Further symptoms and previous attempts help assess scope.
Define tasks and limits
Agree covered devices, applications and tasks individually. Ordinary care does not automatically include security incident response, migration or every hardware repair. Clarify manufacturer and third-party involvement.
| Area | Clarify scope |
|---|---|
| Workplaces | Devices, installation and user help |
| Network / servers | Components and operating boundaries |
| Applications | Versions, licences and contacts |
| Additional projects | Separate scope and approval |
Separate remote and on-site help
Remote help may include screen viewing, shared control or broader access. It depends on platform, connectivity and permissions. An available remote session does not promise every fault can be fixed without a visit.
For site visits, locality, access and operating windows matter. Clarify travel, parts and work outside normal use. Multiple sites and home workplaces must fit the offer.
Agree availability and priorities
For recurring care, define support hours, reporting channel and priorities by impact. Response and resolution times differ: an initial response does not mean a faulty part has been replaced.
Describe genuinely required hours rather than automatically choosing round-the-clock care. Agree escalation, dependencies and separate projects. Availability and response targets require explicit agreement.
Control access and responsibility
Credentials, verification codes and customer records do not belong in the enquiry. Later agree authorised access, suitable rights, records and revocation at contract end. Unattended access needs a separately defined scope.
Clarify internal owners and existing providers. Backup, updates and security tasks need concrete responsibility; a support contract does not automatically guarantee complete protection.
Compare costs on the same basis
Hourly work, prepaid allowance and flat fees need the same scope. Check billing units, unused hours, extras and licences. A low base price without required support hours is not a complete comparison.
| Item | Check |
|---|---|
| Setup | Handover, inventory and documentation |
| Care | Users, tasks and hours |
| Extras | Travel, extended hours, parts and licences |
| Contract end | Notice, data and handover |
Make setup and results traceable
Start with an agreed inventory and clear transfer of contacts and responsibilities. Test an ordinary support request and the agreed escalation route. Changes receive traceable approval.
Agree a clear record of work and outstanding points. On changing provider, documentation, data and access are transferred or revoked. A useful completion record names remaining limits.
Frequently asked questions
Does support cover complete IT operation?
Only within expressly agreed scope. Clarify tasks, systems and exclusions individually.
Can remote help solve every fault?
No. Platform, connectivity, permission and hardware condition determine feasibility.
What does response time mean?
The agreed initial handling or response, distinct from actual resolution.
Do I need round-the-clock care?
It depends on operating hours and outage impact. Compare genuinely required hours.
Must I send passwords?
No. Describe the environment initially. Authorised access is agreed later in a controlled way.
Which costs may be separate?
Depending on terms, setup, travel, parts, licences, extended hours and projects. Check exclusions explicitly.
