Identify work that stops when the main connection fails. Focus first on the work the technology supports and where it becomes unreliable. A useful review records the actual devices and tasks involved, rather than relying on a single speed or uptime figure.
Working through the details
Test a suitable backup route and the services it must support.
A check you can repeat
Give staff a clear escalation and recovery procedure. Agree a baseline and an owner before making changes. After the work, test a real task such as opening a shared file or completing a print job and record what happens.
Test it on a practical example
As a working exercise, choose one live example you can check from start to finish. Write down the intended result before comparing versions, or it will be difficult to tell whether a later change improved anything.
- Test a suitable backup route and the services it must support.
- Give staff a clear escalation and recovery procedure.
- Compare the final result with the intended use, and record who will confirm that it is ready.
Choose one repeatable office task and test it in the place where the problem occurs. Record the device, time and what the user was trying to do. Try one change before running the same test again. Where the work affects shared systems, agree how users will continue essential tasks if the change makes the situation worse.
What to record before sign-off
Keep enough detail for another person to repeat the test. Document equipment, outcome and ownership without including passwords or unrelated private information in the handover.
For help with this work, explore our business IT support in East Kilbride and Glasgow or tell us about your project.