IT support around the work you do

Trades and site based work

Email, job documents and device access may be needed away from an office. Review what people need on site, how files are shared and what happens when connectivity is limited. Reporting projects should begin with reliable job records and agreed definitions.

Professional and office services

Shared records, client information and staff access need deliberate ownership. Tell us about confidentiality requirements and customer contracts before the work is scoped. General IT configuration does not replace specialist legal or regulatory advice.

Customer facing and online businesses

A website, business inbox and connected apps may be the first point of contact. Check the enquiry path, access and recovery arrangements. A form that looks correct still needs a delivery test and an inbox someone monitors.

Your requirements shape the scope

Tell us the software you use, where people work and which records matter. We confirm what can be supported and when a vendor or specialist needs to be involved. If a contract sets a requirement, include the relevant wording so the work can be scoped against it.

Describe a normal day of work

Tell us which tasks have to work and where people do them. For a trades business, that may mean opening a current drawing on a phone, receiving a job update and sending an invoice. For an office team, it may mean shared documents, a customer meeting and access to the accounting app.

Use those tasks to test the proposed setup. A demonstration in an office does not prove that a workflow works on site with different devices or limited connectivity. The requirements should describe that difference before equipment or software is chosen.

Account for the systems around the issue

A business application can depend on email, file access, a browser and a vendor account. When something fails, the useful first step is to identify which part is affected and who owns it. A fault in one vendor's service may need that vendor to investigate.

Keep the application name, error wording and time of the issue with the request. We can discuss the IT investigation and the point at which specialist application support is required. That makes the handover easier when a fault crosses several services.

Bring the requirements before the quote

If a client, insurer or contract sets an access, data location or evidence requirement, provide the relevant wording. The scope needs to identify the systems affected and what a successful result means. A general statement that the business needs to be secure is not enough to price formal assurance work.

The support plan should also say who maintains the arrangement afterwards. A control configured for an initial project needs review when staff, suppliers and applications change.

A checklist with a job to do

The tradie worksheet records who owns accounts and where current job records live. The hospitality worksheet helps a manager check essential tasks before opening and record the right vendor contacts. The office worksheet covers staff access and client file handovers.

Each has a public guide and a printable PDF. You can use the worksheet yourself or send a short description of a gap you want help investigating. Keep passwords and private customer information out of an enquiry.