"Where is this job?" is the question a production floor asks all day. Answering it from NetSuite alone usually means asking a supervisor, who asks an operator, who remembers. Work order tracking closes that loop by recording progress at the point it happens.
A work order is not one thing — it is a routing across several work centers, and only one operation is current at any moment. FactoryBridge lists work orders by the work center where their current operation sits, with planned quantity, completed against planned, remaining, accumulated time and status. The list is searchable, sortable on any column and filterable, and columns can be shown or hidden.
Opening the operation details shows the full routing — every work center in order, its operation status, quantity completed and remaining — with the current operation marked. That is how an operator answers "where is this job actually up to" without leaving the console or calling anyone.
| Status | What it means |
|---|---|
| Pending | Routed here, not yet started |
| In Progress | Setup time running |
| Paused | Stopped against a coded reason; the timer is not accruing |
| Setup Completed | Setup closed, run not yet started |
| Runtime Complete | Run closed, awaiting a completion quantity |
| Partially Built | Completed for less than the balance; the remainder stays open |
| Completed | Planned quantity satisfied |
Real production rarely finishes a work order in one clean pass. Entering less than the balance moves the
work order to Partially Built and retains the remainder. Each completion becomes a record in its own right
— labelled for example WO1614-1 for the first completion of that work order — carrying its own
setup time, run time and total, and its own co-product and yield entries.
That matters for costing: a batch that produced two completions has two independent time records rather than one aggregate, so the two remain separable afterwards.
Because setup and run are timed separately and pauses carry a coded reason, tracking produces more than a status. It produces changeover time per operation, downtime by cause, and elapsed time per completion — the inputs to any serious throughput conversation.
Timers survive navigation: leaving the screen and coming back shows the operation still running with time intact.
Every start, pause, resume, issue and completion is attributed to an operator and written to the audit log, filterable by module, action type, operator, work order number and date range, and exportable to CSV. Each operator also has a personal My Activity view of their own trail.
See NetSuite shop floor control for the dispatch and timing side, NetSuite MES for the full execution picture, or FactorySync if the question is scheduling rather than tracking.
Explore FactoryBridgeThe list is filtered to work orders whose current routing operation is at the selected work center. If the job is still sitting at an earlier operation it will not appear there. Open the operation details on any work order to see where it currently sits.
Each action is attributed individually in the audit log, so a shift change mid-operation is recorded accurately. The work order lock governs simultaneous access, not the phase.
Not from the operator console — the completion dialog states that the action cannot be undone. Corrections belong in NetSuite, deliberately: the console is an execution record rather than an editing surface.
Reading work orders does, because they live in NetSuite. Submissions made while a tablet is offline are held and synced when it reconnects, so progress already recorded is not lost.