The owner gone for a day is not the same as the owner gone for two weeks. For one day a note can be enough; for longer you need clear edges on what the deputy can do on the spot and what needs a written yes. Without edges, the team improvises or freezes, and customers feel both.
The deputy is not “whoever has most seniority on the floor”: it is who can own a decision when needed, including awkward ones. If that person is always the same without pay or workable hours, the role hollows out.
What to put in writing
Who contacts suppliers and support, who handles keys and alarms, who tells the group about last-minute changes. Three lines are enough if everyone has seen them.
A classic mistake
Giving the deputy title but not the time to do it: calls, meetings, and exceptions eat the day like any other department.
A deputy works when delegation shows up in shifts and tasks, not only in the label.
Acting lead: decisions that stick when the owner is away
When the owner is off, the deputy is measured on decisions closed, not good intentions. Put numeric or category limits in writing: which discount bands they can approve alone, which returns wait for a text back, who holds keys and alarm codes. If every grey case is “call me,” the owner’s phone becomes the real manager and the deputy label is hollow. Log recurring exceptions in a shared note so when the owner returns, review is quick and nobody feels they betrayed the mandate.
Who owns approvals, edge-case returns, and keys
Separate routine from escalation. The team should ask in two lanes: “this fits the deputy sheet” versus “this needs the owner.” That cuts pressure on the deputy to invent policy at the till. If you rotate who carries the acting slot, refresh the limits each rotation so one person does not absorb every hard conversation for months.
Handoffs without endless chat threads
Capture date, topic, decision taken, what stays open. The next person on duty needs to know if a supplier is waiting, a till is under review, or a customer expects a callback. Without that thread, the owner’s absence lingers in people’s heads long after they are back.
Show the deputy in the rota, not only on the org chart
If the rota lists the deputy as “just another seller,” you hide the cost of judgement: calls, back-room huddles, till exceptions. Block time where they can stay on the floor with someone else fielding minor interruptions, or quiet windows to clear open cases. A full selling day with no coverage for exceptions is how mistakes and resentment stack up.
When to interrupt the owner anyway
Keep a tiny list of true emergencies—security, legal risk, major cash variance—where the deputy must break glass and call. Publishing that list prevents both paralysis and “everything is urgent” dialling.
After the owner returns
In the first days back from a long absence, sync what was delegated, what slipped, where the team had to tighten. It is not an audit—it updates limits before the next trip. If certain calls always bounced to the owner, widen the deputy mandate or stop treating non-essential asks as urgent.
Handling pushback without blaming the deputy
While the owner is away, the deputy says no to some discounts and delays some returns. Publish rules the team can quote in front of shoppers so they do not feel alone. After tense moments, a short debrief away from the floor separates process feedback from personal criticism.
Sked Solve
Sked Solve helps match responsibility with who is actually on shift, without assuming someone is always there. Start your free trial.