Practical notes

Useful questions before the next IT decision.

A little preparation makes a support request, a system change or an office move easier to understand. These are good places to start.

Discuss your requirement

When something stops working

Record the symptom before changing several things at once. A useful report describes what you were trying to do, what happened instead and whether anyone else is affected. If an error appears, capture its wording without exposing passwords or sensitive business information.

Note when the problem started and any recent change.
Explain whether it affects one device, one location or the wider team.
Describe the business impact so the response can be prioritised.

Before a colleague joins or leaves

Accounts and equipment are only part of the handover. Decide who should approve access, who owns shared information and what happens to ongoing conversations or files. Plan the effective date so business continuity and access changes can be handled together.

List the tools, shared folders and groups relevant to the role.
Identify the manager who can approve access and data handover.
Include company devices and any administrative responsibilities.

Before you rely on a backup

Ask what is included, how long previous versions are kept and who can start a restore. Then consider the actual recovery task. Retrieving a deleted file and recovering an unavailable system require different preparation; a job marked successful is only one part of the evidence.

Identify the data and systems that matter most.
Agree who reviews failed or missed jobs.
Include an appropriate restore check in the recovery plan.

Before an office move

Bring IT into the schedule while the layout and supplier dates are still being decided. Internet availability, cabling routes and equipment locations can affect each other. A move plan should show the dependencies and the checks needed before colleagues start using the new space.

Confirm responsibilities for connectivity, cabling and equipment.
Record what will move, what will be replaced and what must stay available.
Agree how the team will work if a key dependency is delayed.

Let’s look at what
you need.

Tell us about your office and the systems you rely on.

Start a conversation