Eyes Open, Hands Off: A Site-Visit Discipline for UK Group Directors

A group board can govern a subsidiary for years without any director setting foot inside it. Papers arrive, numbers reconcile, assurance letters are signed. Yet the felt reality of an operating company — its pace, its pressures, the gap between what is written down and what is done — rarely travels intact to a boardroom. Site visits close that gap, but only if they are designed with care. Turned into an inspection, they breed defensiveness. Left unstructured, they produce anecdote rather than assurance. The answer is a protocol: short, consistent and deliberately restrained.

Start with the decision, not the diary

A visit should exist to inform something. Before agreeing a date, the group director should be able to name the board question it serves: is capital being deployed as approved; are safety behaviours embedded; is a integration programme holding; is a commercial claim credible. A visit with no decision attached becomes a courtesy call, and courtesy calls are easily stage-managed.

Ask the local managing director for a short pre-read: the site's current key indicators, recent incidents and near-misses, customer complaints, staff turnover, and any capital projects underway. Request that it includes what has gone wrong as well as what has gone well. Agree the scope and timing in advance, and share the outline agenda. The purpose is not surprise. It is a shared understanding of what the visit is for and what it is not.

Who to meet, and who to leave alone

A common failure is to meet only the senior leadership team, who are practised at presenting. A second failure is to bypass that team so conspicuously that local authority is undermined. The protocol should avoid both.

Ask the managing director to assemble a small cross-section: a finance lead, an operations or production manager, a frontline supervisor, and two or three people from the shop floor or customer-facing teams, met in small groups rather than a formal panel. Let the local leader choose the individuals, but be explicit that you want a range of views, not a showcase. Meet the leadership team first, so that they know what you have heard and can respond.

What to observe: the physical and the conversational

A site tells you things that a board pack cannot. Walk the floor. Notice housekeeping, signage, the condition of equipment, whether safety equipment is worn without prompting. Observe the pace of work and whether people seem rushed or waiting. Look at noticeboards and shift handover notes: are they current, and do they reflect the messages the group believes it is sending?

The conversation matters as much as the observation. Ask open questions — what makes your job harder this month; what would you change if you could; what do you think the group does not understand about this site. Listen for the second answer, not the first. Note where local practice diverges from central policy, and resist the urge to correct it on the spot. Divergence may be sensible local adaptation or a control failure; the visit is for noticing, not adjudicating.

A common lens across the portfolio

To compare sites without turning them into a league table, use a small, stable set of prompts on every visit. These might cover safety leadership, the visibility of group strategy locally, the quality of management information, how customer issues are escalated, and how staff describe the group's values. Keep the prompts short enough to remember and consistent enough to compare.

Record observations in a single page: what was seen, what was heard, what requires follow-up. Qualitative language is more honest than scores. A pattern across three sites — the same escalation blockage, the same confusion about a group policy — is far more useful to a board than a ranking that invites defensiveness.

Feeding findings back without undermining management

Before leaving, debrief with the managing director. Share the headline observations, including the uncomfortable ones, and give them a right of reply. This is not a negotiation of facts; it is a courtesy that preserves trust. Anything requiring action should be routed through the normal line: a note to the local board, an item for the group audit committee or the next group board, with an owner and a date.

Group directors should avoid issuing instructions directly to site staff. The visit is an assurance activity, not a command channel. Where a serious issue emerges, the correct response is to escalate through the local managing director and the group's risk process, not to intervene personally.

The discipline of restraint

A two-hour visit is often enough. Twenty minutes of pre-brief, an hour of walking and talking, thirty minutes of debrief, ten minutes of notes. Keep the format stable across sites so that local teams know what to expect and directors compare like with like. Schedule visits on an annual cycle rather than in response to crisis, and rotate which directors attend.

A site visit is a governance instrument, not a goodwill gesture. Done with discipline, it gives the board something no paper can: direct evidence, fairly gathered, of how the group actually operates. Done without it, it gives everyone a long day and a flattering photograph.