Daily Execution
Production Orders and Production Batches are planning documents. The Batch Cards and Operation Ledger Entries covered here are what your supervisors actually fill in every shift — the daily records of what happened.
If a Production Order tells the factory what to do, daily execution records what was done. The dashboards, the cost rollups, the audit trail — they all read from this data.
The two doctypes
- Batch Card — a daily snapshot from a Production Unit. One card per day per unit (typically). Records the operations performed, quantity processed, time spent, defects observed.
- Operation Ledger Entry — an event-level record of work moving. One entry per Start, Transfer, Handoff, Reprocess, End, or Scrap event.
The two play different roles:
Batch Cards say "today at this unit, this is what we did."
Operation Ledger Entries say "at this exact moment, work moved from here to there."
You don't need both for every event, but most factories use both: Batch Cards for the daily wrap-up the supervisor fills in by end of shift, Operation Ledger Entries for the real-time movements the Production PWA posts as work transfers between units.
Who uses what
- Line supervisors fill in Batch Cards at end-of-shift, usually from a tablet on the floor or the PWA.
- Quality and dispatch teams post Operation Ledger Entries for Transfers, Handoffs, and any Reprocess or Scrap events.
- Production managers read both: Batch Cards for daily output, Operation Ledger for "where is this Batch right now."
Getting there
Awesome bar: Cmd/Ctrl + K → type
batch cardoroperation ledger entry→ pick the relevant list.Click path: Desk → GarmentFlow → Production → Batches & Execution card.
What to do next
Start with Batch Cards for the daily-wrap-up pattern, then Operation Ledger for event-level tracking.