Why this decision matters
Loss of a remote feature should not be confused with proof that every local function has failed.
Work through the actual task
- Ask which functions remain local during a connection failure.
- Agree who receives outage reports and how staff operate meanwhile.
- Write down the expected behaviour during a connection loss and the way the system reports it.
Worked example
Remote management relies on the office internet connection. This is a hypothetical example, not a completed customer installation.
The useful evidence at the end of this example is: A communications dependency and fallback instruction for each critical task.
Limits and follow-up
Agree a service scope in writing. Hardware supply, cabling, networking, monitoring and response attendance may be priced separately.
If the relevant check cannot be completed, record what remains uncertain and who will resolve it before work or sign-off proceeds.
Sources and equipment references
Checked for the product, supplier or information details used here. Exact procedures depend on the installed model; these links are not a substitute for its instructions.