What an owner needs before leaving for a week

This story shows a practical response to who decides what, who to call, and what can wait.

Who this is

This composite follows the owner in a packaging business of about 40 people. Their work crosses several desks, with handwritten registers and messages used alongside digital records. The role is answerable for the state of the action and decision limits board and for passing exceptions to the owner. Calls most often come from people who need a yes, no or reliable date before they can continue.

The task here is what an owner needs before leaving for a week. The responsibility is limited: this person can check and record facts within their role, then seek approval when money, safety, customer promises or rules require it.

The moment

A written rule changes the choice: record who can approve routine work and which exceptions must move upward. The difficulty is applying the rule to real exceptions. The owner has to decide what can move now and what must wait. The information comes from open action list, weekly review notes, owner exceptions and team suggestions. A quick answer is tempting, especially when the next team is already standing nearby, but an unverified status can become a commitment.

The first action is to put the current source on the desk or screen. It may be a job card, a supplier message or a bank entry. The owner compares the source with the last approved record. A difference is recorded openly. The role then asks who can verify it, rather than inventing a missing value.

This particular moment turns on three small decisions: issue deputies, decision ceilings and escalation contacts before travel, test access and reporting routine, and name who can decide during absence. Their order matters. A later approval does not repair a wrong quantity or an unsafe condition discovered after work has started.

What they check, in order

1. Confirm the case. Issue deputies, decision ceilings and escalation contacts before travel. Look at open action list, weekly review notes, owner exceptions and team suggestions. Write the reference next to the question instead of keeping it only in chat.
2. Check the original evidence. Verify decision needed, accountable person, authorisation limit, due date and evidence of closure. If two records disagree, keep both and record what needs reconciliation.
3. Look for downstream effects. Test access and reporting routine. Tell the affected team which job, payment, batch or person is waiting. Avoid giving a firm time without evidence.
4. Apply the authority boundary. The owner reviews exceptions involving an altered commitment or a decision outside the normal limit. A verbal approval should be documented.
5. Keep the next action visible. Name who can decide during absence. Show the person, deadline and the record that will prove the task is done.
6. Verify closure. Find written decision, delegated approver and completion proof. If it is missing, keep the item open and make it the first check at the next review.

The checks are intentionally small. They should fit into the person's existing shift instead of creating another report. More detail is useful only when someone will read it and act on it.

What they wish they knew earlier

They would prefer to have decision needed, accountable person, authorisation limit, due date and evidence of closure before the request becomes urgent. A short update from the previous team can prevent repeated calls. The hard part is deciding whether the update is current and authorised.

The actual action and decision limits board is more useful than a polished summary that has no source reference. Start with one change you can measure. A long improvement list without closure becomes another register nobody reads.

The one sheet that helps

A small action and decision limits board brings the question, the evidence and the next person together. The rows below are examples only. They are neither a real company's records nor measured results.

Update the sheet when something changes, even if that change is a revised promise or a failed check. Do not erase the original instruction. For a reusable version, open Decision limits table.

If you do this job

1. Tomorrow, select one real case that matches Who approves what. Keep the original source visible while you make the check.
2. Record who owns the next move. If the evidence is missing, mark the case open and state the exact document or physical check needed.
3. Before hand-over, tell the next role which part is confirmed and which part still needs a decision. Use Nothing moves when owner away to investigate any repeated gap.

Read next

• Nothing moves when owner away
• Who approves what
• Decision limits table