How a fabrication owner prepared to be away for two weeks
An illustrative account of writing down the daily decisions and handing them over a month ahead.
This story shows a practical response to writing down the daily decisions and handing them over a month ahead.
The business
This composite concerns a fabrication business with about 55 people. Drawings and revisions travel between the office, cutting bay and welding team. Some orders need outside finishing before packing. The department manager manages the daily improvement work. The owner is called when a commitment changes or a decision exceeds normal authority.
Records may be spread across open action list, weekly review notes, owner exceptions and team suggestions. This story centres on this recurring task: writing down the daily decisions and handing them over a month ahead.
What was going wrong
Near the dispatch gate, the department manager is dealing with an unclosed action. The immediate problem concerns writing down the daily decisions and handing them over a month ahead. The team can usually explain the situation after several calls. That explanation is rarely attached to the document that the next shift or the customer sees. In this case, the important missing link is list regular approvals before owner travels. It is not enough to know that someone spoke about it.
The second problem is timing. When every small decision waits for a call and the same issue returns next week, the check happens too late to change the next commitment.
What they changed
The team would start by giving one person responsibility for the action and decision limits board. Its first rule is simple: Record who can approve routine work and which exceptions must move upward. Staff can still make calls and use WhatsApp, but the approved reference and the reply return to that record. One owner keeps the entry current, and another person handles decisions outside the routine limit.
For this particular problem, the operating instructions are concrete:
- First check: List regular approvals before owner travels. Keep a reference to the source rather than a summary from memory.
- Next action: Assign deputies and escalation thresholds. Add the responsible role and the time the next answer is needed.
- Decision point: Rehearse one week. Do not quietly replace an old promise or technical record.
The team can copy this small register. Both entries below are illustrative examples, not records of a real business.
| Reference | Source | Required action | Owner | Status |
|---|---|---|---|---|
| S045-01 | action and decision limits board | List regular approvals before owner travels | owner | Open |
| S045-02 | written decision, delegated approver and completion proof | assign deputies and escalation thresholds | owner | Check |
At the end of the review, anything still uncertain stays open. The next person should be able to find the original source, understand which part is confirmed and see who is expected to act. If an approval involves price, safety or compliance, the authorised manager makes that decision.
What a normal morning looks like now
The department manager opens the action and decision limits board alongside open action list, weekly review notes, owner exceptions and team suggestions. They look first for work promised today and then for items missing an owner or proof. The owner does not need the complete history retold. Only the exceptions, their business effect and the requested decisions reach that desk.
A useful meeting ends with the reference, next action and date written down. The team checks the same list later rather than asking each department for a fresh verbal status. Start with one change you can measure. A long improvement list without closure becomes another register nobody reads.
What did not work at first
A likely first attempt is adding more columns or asking everybody to update another report. People then spend time copying entries from their own registers. A second attempt is to mark cases closed after a reassuring phone call. Neither establishes whether the underlying goods, amount or instruction has been checked.
The simpler practice keeps the original reference and records only what has changed. A disputed entry remains disputed. If the team cannot find evidence, it names the person who can, and sets a time for the next check.
What is still not solved
A register cannot remove a material shortage, a customer's disagreement or a long outside lead time. It can expose the risk early enough for a person to decide. This story does not claim an achieved saving, improved margin or shorter delivery time. The useful outcome to measure would be fewer unowned exceptions and a clear record of decisions.
If you want to try this
- Open Owner morning review and choose one live case matching this story. Identify the exact trigger and finish condition.
- Copy the fields from Owner morning sheet. Enter the source, one responsible person, the next check and its date. Use actual records, not the example figures here.
- At the next review, compare the register with the physical or financial evidence. If the same gap returns, revisit Nothing moves when owner away and change the control at that point.
Read next
- Nothing moves when owner away
- Owner morning review
- Owner morning sheet
