A named deputy is not operational cover. Build and test the capability, authority, access and relationships that let people keep standards and customer commitments moving when a manager is away.
The production manager has flu. The quality manager is at a customer audit. The commercial lead is dealing with a family emergency. None of this is remarkable. What matters is whether the business can still plan the day, release product, answer an important customer and protect cash without turning one ordinary absence into a management event.
Founders often test whether they can step away. That is useful, but it misses a more frequent risk: a capable manager is unavailable and there is nobody below them who can run the work safely and credibly. In a €2m to €500m business, a gap at this level can stop a line, delay a shipment, weaken a customer relationship or create a poor commercial commitment long before the CEO hears about it.
A management team is not a bench. A bench exists only when the next person can carry the work, make the agreed decisions and keep the important relationships moving.
Most businesses cope with absence through goodwill. Someone works longer hours, a senior manager watches another department and the founder takes calls from the car. The week may move, but it is a hidden dependency on people being available and helpful at once.
Consider this illustrative example, not a real Terence Monaghan client case study. A fabrication business has a strong production manager who knows the sequence, subcontractors and customer's priorities. When she is off for a week, the supervisor can allocate labour but cannot alter the sequence, see the drawing release or speak confidently to the customer. Quality waits for a concession decision. Sales promises a recovery date without checking capacity. The managing director stitches together decisions that should have stayed inside the operation.
The problem is not that the production manager was absent. Good people will be absent, move roles and eventually leave. The problem is that the business had one manager-shaped point of failure. You discover it when the person is away, which is later than you want to discover it.
Many companies can point to a deputy. The label may be supervisor, assistant manager, senior engineer, team leader or number two. That tells you little. A named deputy is only an intention until they have covered the role under real, bounded conditions and the work has continued to the required standard.
Job shadowing is helpful, but it is not proof of competence. Sitting beside the manager does not show that someone can diagnose a delivery risk at 4pm, weigh competing commitments or hold a difficult supplier discussion. Nor does experience confer formal competence, a qualification, regulatory permission or sign-off. Those need their own documented route and must not be assumed because somebody has been 'covering'.
Be equally clear about authority. The answer is not to send every decision to the chief executive or seek board approval as routine. Define the ordinary decisions a cover person may make, their limits and the genuine exceptions. A deputy who must ask permission to reorder material within an agreed plan, respond to a routine customer issue or move a shift has not been given meaningful cover responsibility.
A Practical Test For Every Critical Role
These four elements are distinct. A technically capable supervisor may lack authority to revise the plan. A commercial cover may have authority but no access to current order status. Calling both 'cover' conceals different gaps.
Start with roles whose absence could affect safety, quality, customer commitments, cash or compliance. Do not limit the exercise to directors. A planner, quality lead, buyer or credit controller may be more exposed than their job title suggests.
The Coverage Matrix
Use one live record per critical role, not a large dense spreadsheet nobody updates. Capture: role; cover person; decisions they may make; system and physical permissions required; competence or formal permission required; evidence of readiness; named dependency or gap; and when the cover was last tested. Keep supporting documents where people can find them, with access reviewed by the appropriate system owner.
For production, name who can run the daily meeting, alter the sequence within guardrails and trigger maintenance support. For quality, identify who may quarantine, investigate, release or escalate, and what formal sign-off remains restricted. For commercial cover, state who can speak to named accounts, issue recovery updates and agree a response within pricing and contractual boundaries. For finance, cover the payment run, collections, cash forecast and banking contact, while keeping bank mandates and segregation of duties intact.
A dependency is not a failure if it is visible and has a plan. You may decide that only one qualified person can approve a particular release for now. Record it, define the backup escalation and build the next person's route to competence. What is dangerous is pretending the dependency does not exist.
The best coverage test is planned, controlled and progressively harder. It is not a licence to remove everyone, abandon standards or manufacture a crisis. Start with a planned half-day in a normal operating period. The cover person runs the routine, makes pre-agreed decisions and records questions. The manager is backup, not beside them answering every call.
Next, test a full shift or day. Add one realistic exercise: late critical material, a request to bring forward a job, a quality concern or a disputed invoice. Set safety and quality limits in advance. Preserve emergency escalation for serious safety, legal, quality, contractual or cash risks. Confirm who handles customer commitments and how decisions are recorded. Then review the exercise with the cover person and manager.
Do not ask, 'Could they cover?' Ask, 'What did they decide, what did they need, and would we be comfortable putting that decision in front of the customer?'
A week of planned cover is useful once smaller tests work. The usual discoveries are mundane but important: a missing system permission, unclear spending boundary, supplier contact saved only on a phone, customer who has never met the deputy or report understood by one person. Fixing those is the point of the test.
Development should be staged, not a sudden handover when somebody resigns. First, explain the operating rhythm and why decisions are made. Then let the deputy lead a contained part of it: tomorrow's production review, a supplier call with preparation, a customer update with the manager listening, or the first pass at a weekly cash forecast. Coach the judgement afterwards, including what information was used and what was missed.
Move from observing to assisted delivery, then to independent delivery within boundaries, then to a tested period of cover. Rotate opportunities among suitable people where the role permits. The aim is not to create a permanent apprentice attached to every manager. It is to build enough depth that operational knowledge and relationships are carried by a team.
Be honest about capacity. Giving a high-performing supervisor deputy responsibility on top of an unchanged workload simply creates overtime and resentment. Remove or redistribute work, define what takes priority and review the additional responsibility. If deputising becomes regular or materially expands the job, review pay, role scope and HR implications with the appropriate advisers. This is a management decision and should not be treated as an informal favour.
The same people are often asked to cover because they are conscientious and calm. That can quietly punish your most reliable employees. It can also leave their own role uncovered, concentrate knowledge in a new place and block the development of others. A bench is not one heroic deputy who covers three managers. It is a deliberate pattern of coverage with realistic workload and manageable spans.
Use the matrix in the monthly management review. Ask what critical role has not been tested, which cover person has changed job or workload, whether access is still correct and which relationship needs a second contact.
Customers feel it when a call is answered by someone who knows the order, can make a sensible commitment and follows through. Suppliers feel it when purchasing continues professionally during leave. Your people feel it when absence does not create panic or a scramble for senior attention.
A transferable business is one where important work, decisions, controlled knowledge and relationships are not trapped in individual heads. It is resilient enough that a normal absence remains normal, while protecting the standards and customer trust it has worked hard to earn.
Your bench is real when the person covering can keep the promise, protect the standard and hand the role back in good order.
Put This Into Practice
The CEO Scorecard gives you a clear view of the constraints affecting profit, cash, the team and your time.
Continue Reading
Back to all articles