The work order says what to make; the job card records how it was made. Capture both as the work happens and production stops being a black box.
Production should not be a black box
In many factories, the office knows what was planned and what was finished, but very little about what happened in between. Material goes to the floor, finished goods come back, and the gap is filled with phone calls and paper sheets typed in at the end of the week.
That gap is expensive. You cannot tell which orders are running late until they are late. You cannot see where material is being wasted. And the cost of each product is a guess based on what the BOM says should have happened.
The work order: what to make
A work order in Sundial is the instruction to make a quantity of one item, using a specific bill of materials, by a planned date. It can be created from a sales order for make-to-order items, from a production plan, or by hand.
The work order carries everything the floor needs to start:
- The item and quantity to produce, and the BOM version to use.
- The materials required, calculated from the BOM, and where they should come from.
- The operations and workstations, in sequence.
- The warehouses involved: a source for raw material, a work-in-progress location and a target for finished goods.
When the work order is released, material is transferred from the store to work in progress, so stock shows exactly what is on the floor rather than pretending it is still on the shelf.
The job card: how it was made
Each operation on a work order gets a job card. The job card is where the floor records reality: which operator worked on it, at which workstation, when they started and stopped, how many units were completed and how many were rejected.
Operators can start and stop time logs as they work, from a tablet or phone at the workstation. Pauses for breaks, changeovers or breakdowns are captured as they happen, not reconstructed from memory.
Because each job card is tied to a workstation, you build a record of how each machine and each line actually performs. That record is the foundation for realistic planning, for costing and for understanding downtime.
What you can see while work is running
With work orders and job cards recorded as work happens, the office can answer questions that used to require a walk round the floor:
- Which work orders are in progress, which are waiting for material, and which have not started.
- Which operation each order is at, and whether it is on schedule.
- Which workstations are busy, idle or stopped.
- How much material has been issued against each order compared with what the BOM requires.
A planner can then make decisions during the day, such as moving a job to another workstation or expediting a missing component, rather than discovering the problem at the end of the week.
Finishing the order
When the final operation is complete, the work order is closed with a manufacture entry. This consumes the materials from work in progress, adds the finished goods to the target warehouse and records any scrap or by-products. The cost of the finished goods includes the materials actually consumed and the operating cost from the job cards.
Any difference between planned and actual consumption is visible on the order. A few units of extra material on one order may be noise. The same difference on every order means the BOM or the process needs attention.
Rejections and rework
Not every unit passes. Job cards record rejected quantities at each operation, and a quality inspection can be required before finished goods are accepted. Rejected units can be moved to a separate warehouse for rework or scrap, so they never show as available stock. Sundial's Quality module links non-conformance records to the job card, so the cause and the corrective action stay with the production record.
Getting the floor to use it
The best tracking design fails if operators find it slower than paper. A few principles help:
- Put a device at each workstation, and make the job card the only screen an operator needs.
- Ask for the minimum: start, stop, quantity done, quantity rejected and a reason for any stop.
- Show supervisors the live view, so the data is used the same day and people see why it matters.
- Start with one line or one product family, fix what is awkward, then expand.
We are building Sundial so an AI agent can watch open work orders and flag the ones likely to miss their date, with a planner deciding what to change. To see work orders and job cards on sample data, try the demo.





