Exceptions, Audit, and Handoff Integrity

Three dashboards for the things that need human attention.

Production Exceptions

The catch-all for things that have gone visibly wrong: Batches that have been On Hold for too long, Cutting Orders Rejected, Operation Ledger Entries with unexplained Scrap quantities, Production Orders past their End Date with no Batches in progress.

The Exceptions dashboard is meant to be acted on, not just read. Open it once a day, work through each row, decide what to do.

Batch Audit

A document-level audit trail across all Batches. Every change of state, every value-edit, every comment, by user and timestamp. The dashboard makes it possible to investigate questions like:

• "Why was this Batch put On Hold?" The audit shows when, by whom, with the comment.
• "Why did this Batch's quantity change after Cut?" The audit shows the change and the user.
• "When was the Cost field last touched on this Batch?" The audit shows it.

You don't open Batch Audit every day. You open it when something doesn't add up and you need to know exactly what happened.

Handoff Integrity

A data-quality dashboard. The Operation Ledger is fragile if entries are wrong — a missing Handoff, an out-of-order Start, a Transfer that doesn't reconcile with a Receive. Handoff Integrity scans the Ledger and flags entries that don't make sense:

• Handoffs without a corresponding Receive on the destination unit.
• Operations that have a Start but never an End.
• Scrap quantities that don't reconcile with the Batch's running quantity.

These aren't usually malicious — they're often a supervisor who forgot to post the second half of an event, or an App action that didn't sync cleanly. The dashboard surfaces them so a production manager can chase them down before they distort the cost rollup or the dashboards.

The audit reports behind them

Dashboards are for browsing. When you want a list you can work through, export or send to someone, four reports cover the same ground with more precision:

• WIP Aging — pieces still waiting at an operation, and how long they've been idle. The forgotten-handoff finder.
• Consumption Pending — operations recorded without their material actually being drawn, because the consumption Stock Entry was left as a draft. Understated stock and understated cost until someone finishes it.
• Operation Over Transfers — entries that moved more out of an operation than had arrived there. The entries behind negative and phantom stock.
• Batch Card Quantity Check — cards whose quantities don't reconcile with their batch.

All four are described in Production reports.

When to read these

• Exceptions — daily.
• WIP Aging — daily or every other day. Idle work ages fast.
• Handoff Integrity and the other audit reports — weekly. Often Friday afternoon, so the floor isn't carrying bad data into the weekend.
• Consumption Pending — before month end, without fail. It moves cost.
• Batch Audit — only when you have a question.

That closes out dashboards. For the tabular reports, see Production reports.