Operation Ledger

The Operation Ledger is the event-level record of work moving through the factory. Every Start, every Transfer, every Handoff, every Scrap — each one is an entry.

Where Batch Cards are a daily wrap-up, the Operation Ledger is a transaction log. Together they tell the story of a Batch's journey from cut to finished goods.

Entry types

Every Operation Ledger Entry has one of six entry types, and the type decides what it does:

• Start — work has begun at an operation. Sets the operation's Step to In Progress, records actual start time.
• Transfer — partial movement within the same operation (e.g., bundles moving between sub-stations).
• Handoff — work moves from one operation to the next, or from one Production Unit to another. The single most common entry type.
• Reprocess — work is returned to an earlier operation for rework. Tracked separately so cost and time are honest.
• End — the operation is complete for this Batch (or the quantity that's been handed off equals the Batch quantity).
• Scrap — units are written off as unsellable. Quantity reduces the Batch's effective output.

The entry type is set when the entry is posted; you don't normally change it after the fact.

What's on an entry

• Entry section. Posting date, datetime, entry type, posting user, related Production Batch.
• Operations section. From Operation, To Operation. (For Start and End, only one side is populated.)
• Reference section. From Unit, To Unit, From Warehouse, To Warehouse. The physical movement.
• Material Consumption section. The Ledger Material Consumption child table — one row per material consumed by this operation, with quantity. Driven by the Consumption Method field: None (no consumption), Recipe Based (auto-populated from the Tech Pack BOM), or Manual (typed in).
• Verification section. Acceptance signature, verifier user. For Handoff entries that require sign-off, this is where it's captured.

How entries get created

Three ways:

• From the Production App — the dominant path. A line supervisor scans a bundle, picks an action (Handoff, End, Scrap), and the entry is posted with the right defaults.
• From the Operation Ledger Entry form — for entries that need fields beyond what the App exposes, or for back-dated corrections.
• Auto-generated — some entries are posted automatically by GarmentFlow (e.g., a Cutting Order Handover posts a Handoff entry for the Cutting operation).

Most supervisors never visit the Operation Ledger form. They post from the App, and the Ledger fills itself in.

Reading the Ledger for a Batch

The fastest way to read a Batch's history: open the Batch, scroll to the Logistics section (the embedded Operation Ledger view), and read top-down. Every entry, in order, with operation, unit, quantity, and the user who posted it.

That's the audit trail. When a brand asks "what happened to this batch on Tuesday," this is where the answer is.

What to do next

That closes daily execution. For the analytical views that read from this data, head to Dashboards.