A Deputy Reveals Whether the Manager Has Built a Branch or a Dependency

The observation

A capable branch manager can produce strong results while also creating a hidden dependency. They know the customers, approve the exceptions, settle disagreements and notice what needs attention. The branch appears controlled because the manager keeps it moving.

The real test is what happens when that manager is genuinely unavailable. A deputy may be trusted to open, close and run the rota but still lack the authority, judgement and confidence to handle commercial, customer and people decisions. Operational cover exists. Leadership cover does not.

How dependency develops

• The manager answers quickly because resolving the issue personally feels faster than explaining the decision and allowing somebody else to make it.

• Delegation transfers tasks but not the outcome, decision boundary or authority needed to own them.

• The deputy receives additional work when the branch is busy but little structured exposure to judgement, trade-offs or feedback.

• The team continues to seek the manager's approval because previous attempts to act have been corrected or reversed without useful coaching.

• Senior leaders praise the manager for always being available, which can reward the dependency instead of questioning it.

None of this proves that the manager is controlling or the deputy is weak. The cause may be unclear policy, insufficient experience, commercial risk or a genuine authority limit. The point is to make the dependency visible and decide what capability the branch needs.

A hypothetical example

The following is a hypothetical example designed to test deputy readiness. It is not a real case study and the figures are included only to make the decisions and consequences clear.

A branch manager takes five working days away and agrees not to monitor email or answer routine calls. The deputy has worked at the branch for three years, understands the team and can manage opening, closing, deliveries and the rota. Both believe the branch is ready.

On Monday, a regular customer disputes a £1,650 credit for returned material. A new £14,000 order is waiting, but the account cannot move until the dispute is understood. The deputy knows the return was checked and believes the credit is justified, but no one has defined what value or evidence they are authorised to approve. The issue waits for the manager.

On Tuesday, a £22,000 quotation needs a one-and-a-half-point price concession and a second delivery. The deputy understands the customer opportunity but does not know the permitted margin floor or service-cost boundary. They send the manager a message rather than risk the decision. By Wednesday afternoon, the customer has placed the urgent part of the order elsewhere.

Two employees then report sick. The deputy can change the rota but is unsure whether they can authorise overtime or short-term cover. The trade counter works under pressure while an experienced salesperson leaves planned customer visits to help. The branch remains open, but another commercial cost has been created by waiting.

By Thursday, the manager has received thirteen messages and logs in during the evening to approve the credit, review the quote and agree the staffing response. When they return, the team says the deputy coped well. In reality, the manager still made the important decisions from a distance.

• Customer credit
  Missing boundary: Value and evidence boundary
  Practical consequence: Decision waits and the next order is delayed

• Price and delivery exception
  Missing boundary: Margin floor and service-cost authority
  Practical consequence: Customer places urgent work elsewhere

• Staffing response
  Missing boundary: Overtime or short-term cover authority
  Practical consequence: Sales capacity is diverted to the counter

The branch has not failed, and the deputy has not performed badly. The absence has exposed missing decision boundaries. The next step is not to tell the deputy to be more confident. Confidence without authority or evidence would simply increase risk.

The manager and deputy now choose three recurring decisions for development. They define the outcome to protect, the evidence to consider, the financial or policy boundary, the point that requires escalation and how the decision will be reviewed afterwards. The deputy then makes those decisions during normal trading while the manager remains available for coaching, not prior approval.

What deputy readiness looks like

• The deputy can explain the branch priorities and make routine trade-offs between customer response, margin, stock, cash and capacity.

• Authority is specific. The deputy knows which decisions they own, the limits that apply and when an exception must be escalated.

• The deputy uses evidence rather than copying what the manager did last time. They can explain the information, options and risk behind the decision.

• The manager reviews judgement after the event. A different decision can become a useful coaching conversation rather than a reason to reclaim control.

• The team recognises the deputy's authority. Customers and employees are not encouraged to bypass them and wait for the manager.

Three practical tests

1. List the five decisions that return to the manager most often. Separate those that genuinely require the manager from those retained through habit or unclear authority.

2. Select one commercial, one operational and one people decision that the deputy can own within written boundaries for the next four weeks.

3. Review each decision afterwards. Discuss the evidence used, the judgement made, the outcome and what the deputy would repeat or change next time.

A planned absence can then test the system, but it should not be the deputy's first exposure to important decisions. Capability is built during normal trading, where feedback is available and the risk can be managed.

Pause and consider

• What stops, waits or returns to the manager when they leave the building?

• Which decisions could be development opportunities instead of interruptions?

• Has the deputy received authority and boundaries, or only additional responsibility?

• Does the team accept the deputy's decisions when the manager is available?

A sensible next step

Choose three recurring branch decisions and define what the deputy can decide, the evidence they should use and the point that requires escalation. Let the deputy own them during normal trading and review the judgement afterwards. If the dependency is material, the BM-015 Branch Manager Succession and Deputy Development Toolkit provides a structured way to build readiness. The toolkit page is available for preview. The toolkit itself is currently in preparation.