Out of hours and weekend IT dispatch: what to settle before you need it

Out of hours means any time outside the normal operating hours of the site or the facility, and the two can differ. A colocation facility may have staff on site around the clock for its own operations while its customer services follow business hours. Your office may close at six while the building manager leaves at five.

Write down the definition for every site before you need it. Include nights, weekends, public holidays and the days around them. Then check what changes inside those hours: who staffs the front desk, whether the loading dock is open, whether the facility treats the visit as a different class of service, and whether notice requirements are longer. Zen's published colocation terms, for example, ask for not less than four hours' notice before access and state that immediate access may not be possible.

Name a small group of people who can request and approve out of hours work, with a backup for each, and keep the list in one place. A request from anyone else should be refused or confirmed with a listed person before dispatch.

Facilities enforce this too. Zen's colocation terms require the customer to supply a list of authorized personnel and to report changes in writing. They also allow the facility to refuse entry to anyone who cannot show they are authorized by the customer. Telstra International's colocation guide asks customers to nominate at least two authorized representatives and treats everyone else as a visitor.

Register the engineer with the site before the visit, not when they arrive. Most facilities want names, company, date and purpose in advance, and some require photo identification matching the name on the list.

Lead times vary. Telstra International's guide asks for a visitor access form at least three business days before the visit, listing names, titles, company and the type of access. That timing does not suit an emergency, so ask each facility two questions: what is the fastest way to add a named visitor, and who can approve it at night? Then record the answers.

Settle the escort and building rules at the same time. Many sites require an escort for visitors, and some check bags and materials at the door. Decide who escorts, what the engineer carries, where they park and which entrance they use. At a branch office, confirm who holds the keys and the alarm code and how to reach them.

Decide before the incident who supplies the part and where it will be received. A spare that sits in a locked cage or an unstaffed receiving area is not a spare.

Facilities also set rules for shipments. Telstra International's guide asks customers to give three business days' notice of a delivery, with the expected time, the number of boxes and the courier name, and to include shipping documents that name the customer and the site. Check the equivalent rule at each site.

Keep the choices simple. Either store spares on site in a known, accessible place, or have the engineer carry them and confirm model and firmware beforehand. If a courier must deliver at night, name who signs for the parcel and where it goes.

A rehearsal in office hours finds the gaps while the cost of a gap is small. Pick a low-risk task, such as a visual check of a rack or a label verification, and send it through the same path you would use at night.

Use the real requester, the real ticket format and the real site contact. Ask the engineer to register, arrive, get escorted, complete the task and send evidence. Then review what slowed the visit and update your list.

Set escalation contacts and stop conditions in writing, so the engineer knows when to keep going and when to call. A stop condition is a point at which the engineer pauses the work and asks for a decision.

Good stop conditions are specific. The engineer stops if the device does not match the ticket, if a label and a record disagree, if the task needs a step that is not in the written scope, or if the site contact cannot be reached. The engineer does not guess, and does not touch live equipment that is not part of the task.

Give the escalation path as a short chain: the on-site contact, the requester, then the approver, each with a phone number. State how long the engineer waits at each step before moving on, and what the fallback is if no one answers, such as leaving the equipment in its current state and reporting.

Ask for time-stamped records of arrival, work and departure, plus photos and test results where they apply. You were not there, so the evidence is what lets you sign off the next morning.

The most common failures are an authorized list that is out of date, a locked dock or door, and no reachable person on site. Each one stops the visit before it starts.

Other frequent causes are an engineer who was never registered with the facility, a part delivered to the wrong place, and a ticket that does not say which rack or room. Check each of these in your rehearsal.

Whichever provider you use, ask for the access and escort plan in writing before the visit. Deploris, for example, works from a written scope, uses vetted engineers from a network and gives you one engagement manager as the point of contact. The same checks apply to any provider.