A service team has an appointment at a Turkish facility, but a change in the work requires additional approval. The overseas headquarters has closed for the day or for a public holiday. An unanswered call is neither approval nor rejection; the business needs its previously agreed authority arrangements to operate.
This article concerns routine visits and service requests. Emergencies follow the site's relevant emergency arrangements. A tight commercial timetable and an urgent safety or health need should not be placed in the same approval queue.
What global-team research contributes
Maznevski and Chudoba's 2000 study followed three global virtual teams for 21 months, examining the fit between communication and decision processes. It supports attention to regular coordination; it does not prescribe a security response time or holiday staffing level. [1]
Our proposal is to identify who may make each decision before creating a contact list. Having everyone's telephone number does not solve a process in which nobody's authority is clear.
Identify the type of decision
A request may concern confirmation of an existing approval, alteration of authorised work or the start of a new activity. A local owner's authority may differ across these situations. Instructions should include straightforward examples that help officers recognise the distinction.
For example, one visit has changed its timing, while another has added a team member. Rather than calling both changes minor and providing the same answer, management should identify the relevant decision owner and limits. Nationality or managerial seniority should not substitute for this process.
Define the local substitute's authority
The substitute should be more than someone who answers calls. State which matters they can decide, what must be referred to headquarters and how decisions are recorded. On a site involving several companies, make clear which operating entity they represent.
NPSA's human-factors guidance for control rooms discusses operating procedures understood by the teams working together. [2] Our proposal is to turn that into a concise decision card. Detailed contact chains should remain internal rather than appearing in public-facing material.
Record six elements of a pending request
- The request and relevant visit reference.
- The specific difference from the existing approval.
- The business unit and authorised decision owner.
- Notifications and responses, explicitly recording when no response has arrived.
- The current position explained to the visitor and the next follow-up point.
- The owner responsible for implementing the eventual decision.
Make the time zone of recorded dates and times understandable. Pending, approved and rearranged are different states. When a new message arrives, the record should preserve when the uncertainty was resolved rather than concealing that a decision was previously outstanding.
Keep continuity across shifts
HSE's shift-handover guidance emphasises transferring relevant information for continuity of work. [3] An incoming officer should see the missing confirmation without repeating the whole contact process. This also helps teams avoid giving visitors contradictory explanations across shifts.
After a holiday period, distinguish delays caused by unclear authority from the overall time requests remained open. Repeated situations may justify revising the approval arrangement. The security provider's contribution is consistent application of the defined authority and follow-up process, rather than creating new authority on headquarters' behalf.
