Branch connectivity
A branch is a small, distant version of a head office, usually without a specialist on site. Connectivity work at branches is therefore as much about what a local manager can check with a torch as about what an engineer can configure from Denver.
One site, one written picture
For each branch we maintain a page: the services present, the connected pathways, the person responsible, the maintenance window, and the steps to follow if the connection fails. It fits on a single sheet, which is the point. A branch with a one-page picture needs far less support than a branch with a forty-page document nobody reads.
- What arrives. Which pathways serve the site and how they are terminated.
- What is kept locally. Which records stay on site and which live centrally.
- Who may reach. The named roles at that location and the services they reach.
- How it fails. The known failure modes and the first three checks to run.
- Who fixes it. The escalation path, with telephone numbers, kept current.
Roles before machines
Branch access is designed around roles: reception, duty manager, warehouse, clinician, duty technician. A role is granted the reach its task needs and nothing else. When a person moves between roles at the same branch, the change is a single edit to a single register entry rather than a sequence of hopeful conversations.
Multi-site consistency without uniformity
Branches differ. A warehouse does not need the same reach as a clinic, and pretending otherwise creates either gaps or excess. We apply a common vocabulary — the same register, the same review dates, the same close-out steps — while allowing each site's reach to reflect its actual work. Consistency of method, not of permission, is what makes a multi-site estate manageable.
Single-sheet per site
One page per branch, readable by the person on duty at two in the morning.
Role-based reach
People receive what their task requires, and a role change is one register edit.
Tested escalation
Escalation contacts and steps are tried in advance, not discovered during an outage.
Adding, moving and closing a site
Opening a branch is a project with a natural sequence: agree the roles, plan the pathways, prepare the positions, test the result, hand the site its single sheet. Closing one is the same sequence reversed, plus a close-out note that records the wiring removed, the grants withdrawn and the records archived. Both are priced from our rate card and scheduled with the client's own teams.
Bring a branch into the register
Start with your most distant or least understood site. We will document it, align its reach with its roles, and leave the local team a sheet they can use.
Reach us Continuity planning