What Is Job Order?
Also known as: job, SyteLine job, work order
Definition
A job order in SyteLine is the production work order that authorises manufacturing a quantity of an item. It carries its own copy of the bill of material and routing, collects material, labor, and overhead costs, and moves through a defined status life cycle.
Job Order Explained
When SyteLine creates a job, it snapshots the item's current bill of material into job materials and the current routing into job operations. From that moment the job is independent: engineering can revise the master BOM without altering work already released to the floor. That snapshot behavior is fundamental to configuration control in regulated manufacturing, and it is also why a job created before an engineering change will happily continue building the old configuration unless someone deliberately refreshes it.
Jobs are identified by a job number plus a suffix, which allows a single job to carry multiple releases or a co-product structure. The status life cycle typically runs Planned, Firm, Released, Complete, then Closed. Planned jobs are planning suggestions that MRP or APS can reschedule freely. Firm jobs are protected from automatic rescheduling. Released jobs can receive material issues and labor transactions. Complete stops further reporting, and Closed finalises variances to the general ledger.
Cost accumulates against the job in buckets - material, labor, fixed overhead, variable overhead, and outside service - at both the job and operation level. Comparing accumulated actual against the job's standard or estimated cost produces the variance analysis that manufacturing finance lives on. Because the job holds its own routing, you can see precisely which operation consumed more hours than planned, which is far more actionable than a plant-level efficiency number.
Two things trip teams up repeatedly. First, jobs left in Complete but never Closed hold variances out of the ledger, so period-end numbers look wrong until someone runs the close. Second, the job's material and routing snapshot means a mid-stream engineering change requires a deliberate decision: refresh the job, scrap and reissue, or let it run as-is. Neither is automatic, and both have quality-record consequences in AS9100 environments.
Why It Matters
- The BOM and routing snapshot is what makes as-built configuration traceable, a hard requirement in aerospace and defense.
- Job status controls whether planning can move the work, so status discipline directly determines schedule stability.
- Unclosed complete jobs distort period-end cost of sales and are a recurring month-end close problem.
- Operation-level variance data pinpoints where money is lost far more precisely than plant-level efficiency reporting.
In Practice
A useful monthly control: list jobs in Complete status with a completion date more than thirty days old. Each one is unreleased variance sitting outside the ledger. Plants that add this to the close checklist typically eliminate a recurring source of unexplained margin swings within two periods.
Frequently Asked Questions
What is the difference between a planned job and a firm job in SyteLine?
A planned job is a suggestion generated by MRP or APS; the planning engine can move, resize, or delete it freely on the next run. Firming the job protects it from automatic changes, so the dates and quantity hold while the planner arranges materials and capacity. Releasing it then permits material issues, labor reporting, and receipts against the job.
Does changing a bill of material update existing SyteLine jobs?
No. When a job is created it takes a snapshot of the bill of material and routing, and later engineering changes do not flow into it automatically. That protects work already on the floor and preserves as-built traceability. If a change must apply to an open job, someone has to deliberately refresh the job materials or operations and record the decision.
Related Terms
Estimate Job
An estimate job in SyteLine is a non-production job used to cost a potential order. It carries materials and routing operations like a real job so SyteLine can calculate a full cost, but it creates no demand, consumes no inventory, and is ignored by planning.
Backflush
Backflush in SyteLine is the automatic deduction of material and posting of labor when an operation or job is reported complete. Instead of issuing each component manually, the system relieves inventory at standard quantity based on the quantity reported.
Current Operations
Current Operations in SyteLine is the shop-floor-facing view of job operations currently available or in process, filtered by work center or resource, from which operators report quantity complete, scrap, and labor time against the job.
Go Deeper
SyteLine MRP Health Check
Diagnose why your SyteLine MRP output is noisy or ignored, scoring data accuracy, parameters, and planner behavior across ten dimensions.
SyteLine APS: Advanced Planning & Scheduling Explained
How SyteLine APS advanced planning and scheduling works: CTP order promising, resource groups, APS vs MRP mode, and tuning tips for discrete manufacturers.
SyteLine Implementation Cost: 2026 Pricing Guide
SyteLine implementation cost ranges from $150K to $1.5M+. See 2026 pricing by company size, phase-by-phase budgets, and the hidden costs to plan for.
Working with Job Order in a live environment? Our engineers do this every day - and our AI agents automate most of it.