Counting output every two hours instead of at day end

This story shows a practical response to a small board at each machine filled every two hours.

Before

In this machined components business with about 45 people, the issue is a small board at each machine filled every two hours. The trouble appears first at the hand-off, before the monthly report can reveal it. The routine depends on the production supervisor knowing which call, slip or instruction matters. Records exist in confirmed orders, machine availability, stores position and shift output sheets, but another person cannot reliably reconstruct the decision. This is the problem behind counting output every two hours instead of at day end.

A request arrives and somebody responds to the loudest part first. The original source is left in a folder or WhatsApp chat. Later, when the production manager needs to review it, people reconstruct what happened from memory. The missing piece is often material ready, machine slot, tools, drawing revision and orders already promised. By the time it is found, another person has already acted on an assumption.

The cost is visible as interrupted work, repeated checking or a promise that needs correcting. No saving or improvement figure is claimed here. The point is to change one repeatable action so that the next case can be handled without a chain of calls.

Why it was like that

The previous method relies on informal permission and experience. Staff may understand the right thing to do, but not where to record it or who can approve an exception. Adding a shared spreadsheet without clarifying authority would leave the same bottleneck in place.

In this example, the control that is missing is any rush insertion names the work it will displace. An urgent request can legitimately break the normal rule. The exception still needs a named decision-maker, a reason and a source reference. Otherwise the exception becomes the usual way of working.

The change

The replacement is a one-page production plan and job card board. Write count at fixed two-hour intervals. This is the required check before an instruction moves to the next person. Note machine stops. Finally, adjust shift plan before it is too late. Each line retains the evidence needed if the decision is challenged later.

Copyable rule for this team

Example register rows, for illustration only:

Job / item	Quantity (example)	Check required	Status	Decision owner
S064-A	12	Write count at fixed two-hour intervals	Open	production supervisor
S064-B	15	note machine stops	Needs proof	production manager

The owner can set a sample limit, but it should be based on actual financial exposure, not copied from another firm. A rule that touches statutory dues, credit, worker pay or electrical safety also needs a qualified reviewer.

After

In the revised composite routine, the first person records the incoming request once. Another team member can see its source, status and next action without recontacting everybody. The production manager sees only the cases needing judgement. Routine cases move under written delegated authority.

For the specific case in this article, the first visible change is write count at fixed two-hour intervals. The next person can then note machine stops. At the end, adjust shift plan before it is too late. That sequence matters because each part leaves a record that the next role can verify.

A weekly check samples a few entries rather than trusting the tick column. The manager looks for cases marked closed without supporting evidence, repeat exceptions and requests that still depend on the owner. Those are reasons to revise the rule.

What to watch out for

Staff may start filling the register after the event. Check the time and reference against the source.
The authorised manager may approve an exception by phone and forget to record it. Ask for the decision to be added to the same entry.
The team may treat every request as urgent. Compare actual deadlines and commercial or safety effects before changing priority.

A plan must reserve time for changeovers and rework. A full machine calendar does not mean a realistic plan.

Copy it

Use the table above as a starting point. Replace the example entries with two current cases. Mark unclear evidence as Open, then name the next person to check it. Keep the source record, owner, next review date and reason for any override. An example exposure of ₹42,000 or 12 units is illustrative only; set limits from your own business records.

Start with Shift production report. If you need the full sequence, use Production plan to output. Measure open exceptions and missed commitments for four reviews before deciding whether the change holds.