V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryWO
Manufacturing · The complete guide

Work Order (WO): Operational Production Orders on the Shop Floor

In short

Follow a production order from authorised scope through scheduling, shop-floor execution, material reconciliation and human review.

4,101 words · ~19 min read
Supervisor in hair cover, mask, glasses and gloves reviewing work order steps on a tablet at a mixing vessel
On this page
  1. 01What a WO authorises—and what it does not
  2. 02Work order, master record, batch record and sales order
  3. 03Baseline the order against a specific master version
  4. 04WO lifecycle states, transition ownership and human review
  5. 05Operator execution: turning planned tasks into recorded events
  6. 06Scheduling capacity without confusing reservations with consumption
  7. 07Production-order terminology across manufacturing industries
  8. 08The data model connecting scope, execution and evidence
  9. 09Worked cases: material reconciliation and realistic line loading
  10. 10US drug requirements and other product-specific regulatory boundaries
  11. 11Integrations, duplicate postings and recovery after interrupted work
  12. 12Failure controls and a practical implementation review checklist
On this page · 12 sections
  1. 1What a WO authorises—and what it does not
  2. 2Work order, master record, batch record and sales order
  3. 3Baseline the order against a specific master version
  4. 4WO lifecycle states, transition ownership and human review
  5. 5Operator execution: turning planned tasks into recorded events
  6. 6Scheduling capacity without confusing reservations with consumption
  7. 7Production-order terminology across manufacturing industries
  8. 8The data model connecting scope, execution and evidence
  9. 9Worked cases: material reconciliation and realistic line loading
  10. 10US drug requirements and other product-specific regulatory boundaries
  11. 11Integrations, duplicate postings and recovery after interrupted work
  12. 12Failure controls and a practical implementation review checklist
AI · Explain it for MY operation

How does WO apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What a WO authorises—and what it does not

A Work Order (WO) is an operational production document that authorises a specific production run and tracks its planned quantity, materials, process steps, equipment and execution status. Production order is a common operational alias; naming variations are addressed in the industry terminology section.

Here, authorisation means permission to undertake the defined work under the site's operating process. It does not mean permission to sell or release the resulting product. This article concerns production work orders, not maintenance orders for repairing equipment or service orders for work performed for a customer.

A useful WO gives planners, operators and supervisors a shared reference for the run. From the order and its linked records, they should be able to answer:

  • What product is being made, including the relevant item or product identifier?
  • What quantity is planned, and in which unit of measure?
  • Which instructions govern the work, and where can operators find them?
  • Which materials, equipment and other resources are intended for the run?
  • Who owns the work and coordinates unresolved questions?
  • What has happened so far, including progress, interruptions and outstanding work?

These are practical information needs, not a universal legal template. The order can point to detailed electronic work instructions and batch execution history rather than reproduce them. Its operational value is keeping the intended work and its current position understandable to the people responsible for carrying it out.

02Work order, master record, batch record and sales order

Using the production scope definition above, distinguish the WO from the documents that define the process, capture execution or represent demand. The comparison below uses common manufacturing terminology, not universal legal definitions.

Document or identifierPrimary purposeOperational question answeredRelationship to the WO
Work order (WO)Authorise and track a specific production run.What work is authorised for this run?Run-specific operational reference connecting planned work with execution.
Master manufacturing record (MMR)Maintain the reusable, approved production definition.How is this product intended to be made?Provides the production definition used to plan the WO.
Executed batch manufacturing record (BMR)Record actual execution and associated results.What happened during manufacture?Documents performed work rather than merely the order's planned scope.
Customer sales orderRepresent customer demand in a commercial document.What has the customer ordered?May drive production demand; does not itself authorise shop-floor production.
Batch or lot identifierProvide a traceability reference for material or product.Which batch or lot does this activity concern?Links the WO to identified material or output; is not another name for the WO.

A site may combine these functions in a controlled packet or application while retaining their different purposes. Shared screens or paperwork do not make planned instructions, commercial demand and execution evidence interchangeable.

Use explicit relationship links rather than assuming a universal sales-order–WO–batch hierarchy. Depending on the production strategy, a WO may support several customer orders, while a customer order may draw from several production runs. Record the relevant demand references, master reference, execution-record references and batch or lot identifiers so those relationships remain understandable.

03Baseline the order against a specific master version

A useful operational control is to establish an order baseline before execution: the referenced master version, routing version, authorised quantity and unit, and applicable instructions. Together, these identify which instructions govern that WO, rather than leaving operators to infer them from whatever document is currently displayed.

Two configuration-control approaches can serve this purpose: an immutable copy of the governing content, or a durable reference to a preserved version. Suitability depends on reliable retrieval and controlled changes, not the name of a database field. A copy can omit linked instructions; a reference can fail if its target is overwritten or removed. Check that the complete applicable instruction set remains retrievable throughout the order’s use and subsequent review.

Resolving an active WO against a mutable latest-version reference risks silently changing its instructions mid-run. For example, a routing revision could introduce a check after the affected operation has already finished. Recipe effective dating helps distinguish when a revision becomes applicable from which revision governs an existing order.

For subsequent scope changes, preserve the original baseline and record the proposed change, its assessment, authorisation and point of application through change control. Include the effect on work already performed: whether it remains acceptable, needs additional checks or calls for another documented decision. This is a proposed operational control, not a prescribed snapshot mechanism. The record comparison covers master instructions and executed records; here, the concern is identifying the instructions governing the order.

04WO lifecycle states, transition ownership and human review

The following is an illustrative production-order lifecycle, not a prescribed regulatory sequence. Labels vary between sites; transition conditions and accountable owners matter more than the names assigned to states.

State enteredProposed owner and transition check
DraftPlanning establishes product, quantity, scope and intended instruction baseline.
AuthorisedDesignated personnel confirm scope and instructions are ready for work.
ScheduledPlanning assigns a feasible resource slot within the authorised scope.
ExecutingOperators confirm start conditions and record work performed.
On holdSupervisors manage operational exceptions, identify affected work and define restart conditions.
Execution completeOperators declare planned work finished; supervisors check outstanding tasks and exceptions.
Under reviewAuthorised reviewers assess completion evidence, discrepancies and unresolved actions.
ClosedThe designated closure owner records acceptance of operational completion after review.

Workflow summary: draft → authorised → scheduled → executing → execution complete → under review → closed. Branches accommodate holds, cancellation and controlled reopening.

A temporary hold pauses affected work without abandoning the order. The proposed restart check confirms that the hold reason has been addressed and identifies who permits resumption. A process event log can preserve the reason, actor, time and prior state for each transition.

Cancellation ends the remaining authorised work rather than merely delaying it. Designated personnel should record the reason and account for work already performed; cancellation does not erase execution history. Controlled reopening should identify the additional work, approving person and review route while retaining the earlier closure. Direct instruction changes through the order baseline, rather than silently changing tasks during a status transition.

Operational closure and product quality disposition are separate decisions: a closed WO does not itself authorise batch release. Accountable humans approve work and release product within their assigned authority. Software status records workflow progress; it does not certify compliance.

From authorised scope to reviewed WO closure
  1. 1
    Define scopeEstablish the product, quantity, unit, intended outputs and responsible owner.
  2. 2
    Baseline InstructionsReference the approved master version and record the order authorisation.
  3. 3
    Schedule ResourcesAllocate materials, equipment and people without treating reservations as consumption.
  4. 4
    Execute tasksIdentify resources and record actual work against the authorised scope.
  5. 5
    Resolve exceptionsPause affected work, preserve context and obtain the appropriate decision.
  6. 6
    Reconcile evidenceCompare material movements, outputs, completed tasks and outstanding issues.
  7. 7
    Review and closeAuthorised people confirm operational closure; product disposition remains separately visible.
Illustrative operational flow; state names and decision ownership follow the site's defined process.

05Operator execution: turning planned tasks into recorded events

A practical execution pattern connects each task on the work order to evidence of what happened. A kiosk or shop-floor terminal is one possible recording point; controlled paper forms or other controlled electronic records can serve the same operational purpose.

  1. Identify the WO and task before starting, so the entry belongs to the intended production run.
  2. Confirm the applicable instructions and their revision for that task.
  3. Identify the equipment and materials at the workstation, including the material lot rather than only the item name.
  4. Perform the task according to the applicable instructions.
  5. Record actual observations and results as work occurs, and report exceptions against the affected task.

Keep planned values separate from recorded actuals: a target quantity is not evidence of the quantity used. As relevant to the operation, capture the material lot, actual quantity and unit, equipment identity, task result, responsible person and event time. Preserve enough context to distinguish an observation from a correction to an earlier entry.

Scanning identifies a reference; it does not establish that a physical manufacturing step occurred correctly. A material scan alone does not demonstrate that the material was added or that the intended amount was used.

At personnel changes, use a shift handover report to identify unfinished tasks, outstanding exceptions and the person accepting responsibility. Record where work stopped and what remains unresolved. Use the WO state transitions for hold and completion decisions.

06Scheduling capacity without confusing reservations with consumption

A WO schedule is a proposed allocation of resources, not proof that work can start. In common finite-capacity scheduling practice, planners compare requested start and completion dates with equipment eligibility, staffing, material availability and completion of preceding operations. Changeover and cleaning occupy capacity too; a line may be idle for production yet unavailable for another order.

A nominal production rate estimates running time only. It does not establish a feasible completion time unless the schedule also accommodates preparation, resource calendars, dependencies and competing work. Keep rate assumptions visible and specific to the planned operation; the worked cases show how these affect line loading.

Keep planning allocations separate from execution transactions. A material reservation earmarks stock for an order; it is neither a physical issue to production nor recorded consumption. Likewise, planned equipment identifies an intended resource, not the equipment actually used. Express demand and production quantities in explicit units, with a defined conversion between commercial packs and manufacturing units rather than silently equating them.

A practical handoff to operator execution occurs when the responsible coordinator confirms readiness and dispatches the operation. From that point, actual starts, resource use and interruptions inform replanning rather than being inferred from the scheduled dates.

07Production-order terminology across manufacturing industries

Production order, process order, shop order and job order may describe related operational objects. Local procedures and ERP conventions govern their meaning. For readers in pharma, supplements, food, devices and chemicals, compare the work authorised, its units and its traceability relationships—not just the order name.

  • Batch-oriented processing: an order might authorise blending in kilograms or litres, linking input material lots to an output batch.
  • Packaging: an order might authorise filling or cartoning in bottles, packs or cases, linking bulk product to packaging components and finished lots.
  • Discrete assembly: an order might authorise building units, linking components or subassemblies to finished lot or serial identities.

These are examples, not fixed industry classifications; one site may use all these patterns. In MES–ERP integration, map local meanings explicitly rather than assuming matching labels mean matching work. Shared vocabulary does not imply shared legal obligations; use the product-specific regulatory mapping for applicability questions.

08The data model connecting scope, execution and evidence

A useful conceptual model separates the order’s scope from its execution history and supporting records. The following entities describe relationships for production traceability, not a prescribed database schema or software feature.

EntityPurpose and relationship
Work orderIdentifies the operational scope and carries current summary fields, such as status and completed quantity.
Order baselineConnects the WO to the planned scope and instruction version selected for execution.
Execution eventRecords an action against the WO, with relevant task, actor and resource context.
Material movementConnects the WO to a material lot, quantity, unit and movement type, such as issue or return.
Record linkConnects the WO to relevant commercial, master or batch records without merging their identities.

In this model, wo_id identifies the order; lot_id identifies material; equipment_id identifies the physical resource. These identifiers answer different questions and should not substitute for one another. Explicit relationships can accommodate several WOs contributing to one batch, or one WO referencing multiple material lots. Label each relationship so a commercial reference cannot be mistaken for an execution record.

Current summary fields show where the order stands now. The underlying process event log explains how it reached that state. A completed-quantity total alone does not explain partial completions, reversals or corrections; retaining their contributing events makes that total reconstructable.

For reconstruction, preserve quantity units, actor identity and, where needed, both performed-at and recorded-at times. Retain external transaction identifiers for cross-system reconciliation. Corrections can reference the original event and preserve its prior value and correction reason rather than replace history invisibly. Message retries and interrupted transfers belong in integration and recovery design.

Conceptual WO Entities and Evidence Relationships

Work order

Run scope and current operational state.

  • wo_id
  • product_id
  • planned_qty
  • qty_uom
  • status

Order Baseline

Instructions associated with the authorised scope.

  • baseline_id
  • wo_id
  • master_version_id
  • routing_version_id

Execution Event

Actual task, resource, person and time.

  • event_id
  • wo_id
  • step_id
  • equipment_id
  • operator_id
  • performed_at

Material Movement

Lot-level transaction with replay identity.

  • movement_id
  • wo_id
  • lot_id
  • quantity
  • uom
  • movement_type
  • idempotency_key

Record link

Explicit connection to another controlled record.

  • link_id
  • wo_id
  • record_type
  • record_id
Proposed field names illustrate relationships, not a particular software schema.

09Worked cases: material reconciliation and realistic line loading

Case A: below target, but all material accounted for

Assume a packaging WO receives 500 kg of net product from one material lot. Every pack contains exactly 0.5 kg, and the target is 1000 packs. There is no process loss or measurement uncertainty. Recorded output is 980 packs, with 6 kg of rejected material and 4 kg of unused product. These are hypothetical inputs, not operating limits; packaging weight is outside this product-mass calculation.

  • Packed product: 980 × 0.5 kg = 490 kg.
  • Material reconciliation: 490 kg + 6 kg + 4 kg = 500 kg.

The packed quantity falls short of the target, but the accounting contains no unexplained material loss: all incoming product appears in packed, rejected or unused quantities. This is why a theoretical-versus-actual yield comparison answers a different question from the mass balance. Neither calculation alone explains why material was rejected or left unused.

The remaining decisions are concrete: determine whether the unused product can support further packing or needs another documented destination; establish the permitted handling of the rejected material; and decide whether to complete the original order quantity or authorise a changed quantity. The reconciled total does not decide any of those actions.

Case B: production time is not total line occupancy

Assume a WO calls for 2400 cartons at a constant rate of 600 cartons per hour. Changeover takes 0.5 hour and cleanup takes 0.5 hour on the same line. All activities are sequential, with no downtime. The available window is 4.5 hours. These are hypothetical planning inputs, not standard rates or required durations.

  • Production: 2400 cartons ÷ 600 cartons per hour = 4 hours.
  • Line occupancy: 4 + 0.5 + 0.5 = 5 hours.
  • Window shortfall: 5 − 4.5 = 0.5 hour.

The order does not fit unchanged. Planning options are to move it in the schedule, extend the available window, or obtain authorisation to change its scope and recalculate the load. Omitting cleanup from the booking does not remove its line occupancy. Apply the capacity planning reasoning above when testing alternatives through finite-capacity scheduling, rather than treating the carton target as proof that the booking is feasible.

10US drug requirements and other product-specific regulatory boundaries

Binding regulation: US drug products

For US drug products under 21 CFR 211, the following requirements concern procedures and production records. The operational connections are proposed ways to connect a WO to those records, not additional legal requirements.

Jurisdiction and product scopeProvisionSupported requirementProposed WO connection
US drug products under 21 CFR 211211.100(a)Written production and process-control procedures, including changes, require review and approval by appropriate organisational units and the quality control unit.Reference approved procedures; route changes through change control.
US drug products under 21 CFR 211211.100(b)Written production and process-control procedures must be followed, with execution documented at the time of performance. Deviations must be recorded and justified.Connect execution events and deviation records to the affected operation.
US drug products under 21 CFR 211211.186(a)Master production and control records are required for each drug product and each batch size.Select the applicable product and batch-size master.
US drug products under 21 CFR 211211.188Batch production and control records must be prepared for each batch produced.Connect the order to each resulting batch record.
US drug products under 21 CFR 211211.188(a)Batch records must include an accurate reproduction of the appropriate master production or control record, checked for accuracy, dated and signed.Preserve the master-to-executed-record relationship.
US drug products under 21 CFR 211211.188(b)(2)Batch documentation must identify individual major equipment and lines used.Link actual equipment use, not merely planned assignments.
US drug products under 21 CFR 211211.188(b)(3)Batch documentation must specifically identify each batch of component or in-process material used.Link actual material batches to execution.

Keep other authority and design choices separate

  • Official guidance: assess applicable agency recommendations separately from the binding provisions above.
  • Industry practice and operational design: treat the WO baseline, lifecycle states and data model as proposed controls, not statutory names or mandated software mechanisms.
  • Proposed software support: use the WO evidence relationships described above, supported by consistent production context tagging, to connect records. A WO identifier alone is not the evidence; review and release decisions stay with authorised people as in the lifecycle section above.
  • Other products and markets: for supplements, food, devices, chemicals and non-US markets, review the current product- and jurisdiction-specific framework rather than extending this US drug mapping.

11Integrations, duplicate postings and recovery after interrupted work

A proposed integration design assigns an authoritative owner to each field rather than letting every system overwrite it. For execution–warehouse interfaces, document ownership and unit conversions explicitly:

SystemProposed ownership
PlanningWO identifier, planned quantity and unit, scheduling status.
ExecutionOperation/event identifiers, measured quantities and units, step status.
InventoryLot/location identifiers, posted stock quantities and inventory units, availability status.
QualityReview identifiers and disposition status; references production quantities and units without redefining them.

An accepted interface message confirms receipt or processing under the interface contract—not that a physical operation occurred. Keep transport acknowledgements separate from execution evidence.

Proposed controls include stable transaction identifiers and idempotency keys retained across retries to prevent duplicate delivery from creating duplicate postings. Route conflicting or unresolved events into reconciliation queues. For out-of-order events, check predecessor relationships before changing status. For offline recording, preserve original identifiers, operator attribution and event time; map event time separately from server receipt time in the process event log.

After a lost acknowledgement, inspect the destination transaction, reconcile its identity and payload against the originating event, then determine whether retry is appropriate. If the result remains uncertain, retain it for reconciliation rather than assuming failure or success.

Before restarting interrupted work, establish the last confirmed physical step, compare recorded and physical material state, preserve the interruption history, and obtain the applicable local authorisation. Use the implementation review checks to test recovery behaviour, including unresolved discrepancies.

12Failure controls and a practical implementation review checklist

Use these risk-based review examples to test recorded inputs, actions and outcomes—not merely whether a screen accepts an order. They are suggested operational checks, not an exhaustive compliance checklist.

FailureObservable symptomProposed controlReview evidence
Unit mismatchIssued quantity uses an incompatible unit.Reject incompatible units; record authorised conversions.Input units, conversion basis, resulting quantity or rejection.
Wrong physical-resource identityRecorded equipment differs from equipment used.Confirm asset identity before execution.Presented asset identifier, comparison result, operator response.
Undocumented reopeningClosed order gains new transactions without explanation.Restrict reopening; capture reason and authorisation.Previous state, requester, authoriser, timestamp, subsequent activity.
Incomplete correction trailChanged quantity obscures the original entry.Preserve original and corrected values with attribution.Before-and-after values, reason, actor, time in the audit trail.

Implementation review checklist

  • Identifier ownership: identify who assigns identifiers and resolves collisions.
  • Unit conversions: test permitted conversions and incompatible-unit rejection.
  • Baseline retrieval: retrieve the version bound to a historical order.
  • Transition permissions: exercise permitted and denied actions using representative roles.
  • Correction handling: reconstruct a correction through the audit trail review workflow.
  • Linked-record retrieval: follow order links to material, equipment and execution evidence.
  • Interrupted-work recovery: interrupt execution and confirm resumed work neither loses nor duplicates postings.

Apply the reasoning in the earlier sections. Use the worked production cases as sample review scenarios, not acceptance limits; record expected results, observed results and unresolved discrepancies.

Frequently asked questions

Q.How can one customer sales order be fulfilled through [several production WOs](/glossary/production-schedule-board)?+

A sales order records customer demand; production WOs authorise the runs used to fulfil it. Operationally, planners can split demand across WOs to accommodate equipment capacity, material availability or delivery priorities. Each WO retains its own planned quantity and execution status, while allocation records connect eligible output to the relevant sales-order line. Track allocated, unallocated and shipped quantities separately so the same output is not promised twice. Allocation arbitration addresses competing demands for available stock.

Q.When can several WOs contribute to the same batch without losing [record traceability](/glossary/batch-execution-history)?+

This arrangement is workable when the site defines the batch boundary and gives each contributing WO a distinct operational scope. A practical record model links every WO to the batch identifier and attributes material movements, equipment use, results and operator actions to the relevant operation. Handoffs identify what was transferred and accepted, rather than merely marking both orders complete. Production context tagging helps explain these relationships; shared batch identity alone does not establish which WO performed a particular step.

Q.How should a revised master be assessed when an active WO still references the [earlier baseline](/glossary/recipe-effective-dating)?+

Treat the revision as an impact-assessment question, not a reason to overwrite the active WO. Under a practical change-control process, compare the changed instructions with completed work, remaining operations, issued materials and recorded results. The authorised decision can retain the earlier baseline, introduce a controlled transition or stop the run for further assessment. Preserve the original reference and document where any approved change takes effect, so later reviewers can distinguish instructions actually used from instructions published afterward.

Q.What [inventory state](/glossary/hold-tag-electronic) should remain visible if a WO closes while product disposition is still pending?+

Keep the product's pending-disposition or hold status visible independently of the WO's administrative closure. A practical inventory view shows the batch, quantity, unit, location and restrictions on allocation, movement or shipment. Closing an order can indicate that production accounting is finished without establishing that its output is available for use. The batch-release decision remains with authorised people; a closed WO should not be interpreted as that decision or silently remove inventory restrictions.

Q.How should unused material be handled when a run finishes below its planned quantity?+

Reconcile the material actually consumed, remaining, sampled, spilled or otherwise lost before resolving the unused balance. A practical return assessment considers identity, container condition, exposure, storage history and any restrictions on reuse. Record the returned quantity, unit, source lot and destination; do not calculate consumption solely by subtracting planned output from planned input. Where warehouse and production records interact, MES–WMS integration provides a useful framework for distinguishing physical returns from reservations released without a material movement.

Q.What should an operator do when physical work is complete but an interface posting has no acknowledgement?+

Treat the posting as unresolved, not as proof that the physical operation failed. Follow the site's exception procedure: preserve the transaction reference, record what physically occurred and notify the responsible support or supervisory role. Avoid repeating production or creating an unrelated replacement posting simply to clear the screen. A practical MES–ERP integration recovery process checks whether the receiving system accepted the original transaction before authorising a retry, then reconciles the business record with the physical quantity.

Q.Can a single WO cover both bulk processing and packaging, and what relationships would that need?+

Yes, as an operational design choice, provided the order structure distinguishes bulk operations from packaging operations. Useful relationships connect the bulk lot to quantities issued into each packaging run, the packaging-material and label lots used, and the resulting finished-product lots or stock identities. Record intermediate storage, partial transfers, unused bulk and packaging losses against the appropriate operation. Bin-level lot genealogy supports understanding these transfers when material changes location; a shared WO number alone is too coarse.

Q.What evidence helps an authorised reviewer choose between resuming, cancelling or replacing an interrupted WO?+

A practical decision package brings together the last confirmed operation, material and equipment condition, elapsed holding conditions, outstanding checks, deviations and unresolved transactions. A process event log can establish the interruption sequence without treating schedule status as evidence of product suitability. The reviewer assesses whether remaining work can proceed under the approved instructions and documented conditions. Cancellation or replacement also calls for explicit treatment of existing material, recorded consumption and successor-order links, rather than erasing the interrupted history.

Primary sources

  • 21 CFR 211.100
  • 21 CFR 211.186
  • 21 CFR 211.188
Software that covers WO
V5 Ultimate Shop Floor Data Collection Software
Barcode scans, scale readings, operator checks and downtime reasons recorded at the station as work happens, each with who, what…
V5 Ultimate Shop Floor Execution
Each operation shown on the operator's screen in the order you set, with scans confirming materials and equipment, results…
V5 Ultimate MES Software
V5 takes planned work orders to a kiosk at the line. Operators follow the configured steps, record weights and checks, and sign.…

Explore this topic

WO sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.

MES, WMS, ERP & QMS Layer
15 related entries

Where each shop-floor system fits and what it owns vs the ERP above it.

MESWMSQMSERPLIMSRoutingBOMTraining RecordSOPRBACSSO / SAMLDocument controlAudit ManagementCMMSAsset Lifecycle Management
Planning & MRP
17 related entries

Material requirements planning, BOM explosion, net requirements, scheduling and demand signals that drive what the floor makes next.

MRPMRP IIBOMBOM ExplosionPhantom BOM ExplosionNet RequirementsRoutingBackward SchedulingForward SchedulingFinite Capacity SchedulingDemand ForecastingEconomic Order Quantity (EOQ)Days of Supply (DOS)Fill RateBackflush ConsumptionFEFOFIFO
Talk to us about WO

Want to see how WO could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Inside V5
  • → Production — run the work order, record it as it happens.
  • → Manufacturing kiosk — the shop-floor terminal your batch record needs.
Example reports
V5Ultimate

Sample report

Work Order Traveler

Plan & make

Work Order TravelerView on screen or print
→ All example reports
Related terms
  • → BOM
  • → Routing
  • → MMR
  • → eBMR
  • → eDHR
  • → MES
  • → WMS
  • → QMS
  • → ERP
  • → LIMS
  • → Training Record
  • → SOP
  • → RBAC
  • → SSO / SAML
  • → Document control
  • → Audit Management
  • → CMMS
  • → Asset Lifecycle Management
  • → MRP

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC