Traveler / Router

Operational meaning

In manufacturing, a **traveler** (also called a **router**) is a structured production document that accompanies a work order, lot, or batch as it moves through the plant. It defines the required processing path and provides a place to record execution data for each step.

A traveler/router commonly includes:

– Identification: work order, part or product ID, revision, lot or batch number
– Routing definition: ordered list of operations, work centers, or machines
– Process details: standard operation descriptions, reference to methods, drawings, or recipes
– Parameters to record: quantities, times, measurements, test results, and defect codes
– Accountability: operator sign-offs, approvals, and sometimes electronic signatures
– Status fields: operation completion flags, hold or rework indicators, and scrap recording

Travelers/routers may be implemented as:

– **Paper forms** that physically follow the material through each work center
– **Electronic travelers/routers** inside an MES or ERP that logically track the work order as it is processed

Use in manufacturing workflows

In day-to-day operations, a traveler/router is used to:

– Communicate which operations must be performed, and in what sequence
– Indicate required resources such as work centers, tools, or fixtures
– Capture production data at each operation (e.g., start/finish times, yields, test values)
– Document inspections, quality checks, and holds
– Provide traceability from finished product back to the operations and conditions under which it was produced

On the shop floor, operators consult the traveler/router to know what to do next and record what was actually done. Supervisors and planners use the traveler/router to monitor progress and verify that required steps were completed.

Boundaries and distinctions

– A traveler/router **defines and records** the process path and execution data for a given work order or batch; it is not the same as:
– A **work instruction** or **SOP**, which provides detailed step-by-step how-to content
– A **process route master**, which is the template or master data from which individual travelers/routers are generated
– A **shipping document**, which covers logistics after manufacturing is complete
– In many systems, the word **router** emphasizes the planned sequence of operations (routing), while **traveler** emphasizes the physical or logical document that accompanies the work. In practice, the two terms are often used interchangeably.

Electronic travelers/routers in regulated environments

In regulated or highly controlled manufacturing (e.g., pharmaceuticals, medical devices, aerospace), travelers/routers are frequently managed in electronic systems such as MES or integrated ERP/MES platforms. In these contexts they commonly:

– Enforce predefined routings and processing rules
– Capture electronic records of execution, including operator IDs and timestamps
– Reference controlled documents, recipes, and specifications
– Support traceability, deviation recording, and quality review processes

The core concept remains the same as with paper travelers/routers: a defined routing plus a structured record of how each unit, lot, or batch moved through that routing.

Common confusion

– **Routing vs. traveler/router**: “Routing” usually refers to the reusable master definition of the process path for a product. A traveler/router is the instance of that routing (plus record fields) for a specific work order or batch.
– **Batch record vs. traveler/router**: In some industries, the terms overlap. A batch record often includes additional formulation, processing, and quality data beyond the routing steps. A traveler/router may be one component of, or equivalent to, a batch record depending on the plant’s documentation model.

Site context application

On this site, *traveler/router* commonly refers to the production documentation and routing mechanism that links shop-floor operations, MES/ERP master data, and quality records. It is a key object used for execution tracking, traceability, and integration between OT and IT systems in manufacturing environments.