Job Traveler
Job Traveler is a job-specific operation-route and execution document that accompanies identified work through authorised operations and accumulates actual completion evidence.

On this page · 11 sections
- 1What a job traveler records
- 2Issue the route for identified work
- 3Record the work actually handed over
- 4Connect operation entries to retrievable evidence
- 5Case: assembly completed, test evidence missing
- 6Case: one job split across two stations
- 7Case: rework without rewriting the original result
- 8Review missing operations and keep decisions separate
- 9Place device travelers in the right regulatory context
- 10Keep linked systems consistent when work changes
- 11Test the traveler with a focused retrieval trial
How does Job Traveler 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.
01What a job traveler records
Job Traveler is a job-specific operation-route and execution document that accompanies identified work through its authorised manufacturing route and accumulates evidence of what actually happened to that work. Job traveller, manufacturing traveler and manufacturing traveller are aliases for the same manufacturing concept, not separate regulatory document classes.
In ordinary manufacturing usage, the traveler connects a particular job to its applicable operations and their execution entries. Its scope follows the identified work, whether an assembly, a lot or a defined group of units. The distinction between reusable route, issued document and completed record matters:
| Record | Scope | Planned or actual information | Relationship to the traveler |
|---|---|---|---|
| Blank/master route | Reusable manufacturing route | Planned operations and instruction references | Basis for issuing a job-specific traveler |
| Issued traveler | Identified job and applicable route | Planned route with accumulating actual entries | Working document accompanying the identified work |
| Completed traveler | Executed route for that job | Actual completion entries and evidence references | Resulting execution record |
| ERP work order | Production demand and job administration | Planned quantity, dates and reported progress | Establishes job context; does not replace operation evidence |
| Electronic work instruction | Method for performing an operation | Instruction content | Explains how; the traveler records job-specific execution |
| Broader DHR/eDHR record collection | Manufacturing history for identified devices | Collected production and acceptance records | May contain or reference the traveler |
| As-built configuration snapshot | Configuration of the manufactured item | Actual components and revisions | Describes what was built, not its operation-by-operation passage |
| Serial genealogy | Relationships among serialised items and components | Actual identity links | Supports tracing relationships beyond the route record |
These records can share identifiers without becoming interchangeable. A traveler may reference an electronic work instruction rather than reproduce its method, and sit within a broader eDHR record collection rather than contain every supporting record. This article concerns the issued route and its accumulating handoff history—not parent-record assembly, instruction writing, production scheduling or genealogy traversal. Paper and electronic formats serve the same basic purpose; the defining feature is their connection to identified work and its operations.
02Issue the route for identified work
A practical issue sequence starts by matching the job identifier to the product or assembly identifier and its applicable revision. Establish the starting quantity and unit of measure, select the authorised operation route revision, and identify the instruction references and revisions applicable to that work. Then assign an identifiable traveler instance before production begins. These are proposed manufacturing controls, not a prescribed form.
On paper, the issued packet can physically accompany the identified work. Electronically, accompaniment means that personnel at each station can retrieve the applicable traveler and distinguish it from other jobs or superseded copies. The record need not move physically, but its association with the work needs to remain unambiguous at every handoff.
Give each operation a stable identifier independent of its displayed sequence number. Reordering the display then leaves references to that operation intact. Where the local route permits conditional operations or parallel branches, identify the selection conditions, branch relationships and return points explicitly; a simple numbered list can otherwise imply a sequence that was never intended.
Issue planned operations, not apparent execution evidence. Instruction references and expected activities belong in the issued plan; completion signatures, actual quantities and result references remain unfilled until the corresponding events occur. An empty execution field communicates work still to be supported, not a missing planning value.
For a mid-job instruction change, assess work already performed separately from outstanding operations. Record the authorised applicability decision, including affected work, the change boundary, who authorised it and when. Identify the current traveler instance through a revision or linked supplement, retain the preceding issued state, and make the applicable version clear at the next station. Silent replacement obscures which instructions governed earlier work.
- Identify jobAssign product identity, quantity and the applicable route revision.
- Issue travelerBind the job to its authorised instructions and operations.
- Perform operationRecord the actual attempt, performer and supporting result references.
- Transfer workIdentify the receiving station, work subset and actual quantities.
- If an exception occursHold affected work. Its disposition specifies a rework return, permitted onward transfer or scrap; do not assume the next operation.
- Review evidenceCompare the issued route with operation attempts and results.
- Close recordRecord the responsible person's closure decision and evidence reference.
03Record the work actually handed over
A useful traveler handoff tells the receiving station which work arrived, what operation it came from, and what status applies to that particular subset. The following fields are a practical design proposal, not a prescribed regulatory form.
- Operation record: operation_id, route_position, station_id, instruction_id, instruction_revision, started_at and completed_at. Keep operation identity distinct from its position in the route so a sequence change does not silently relabel earlier work.
- Handoff record: handoff_id, from_operation_id, to_operation_id, work_subset_id, quantity_sent, quantity_received and unit_of_measure. Link the transfer to its originating and receiving operations rather than recording only a station-to-station movement.
Identify the actual units transferred through a serial list or range, lot subset, or identified container with recorded contents. A parent job number alone cannot distinguish parallel subsets. Where containers carry the identity, keep their contents association traceable through moves and repacking; bin-level lot genealogy addresses that supporting relationship.
At a stated reporting point, such as the sending operation’s handoff time, record mutually exclusive quantities: accepted-for-that-operation, held, scrapped and still in process. Name the operation in the acceptance status instead of using an undifferentiated good quantity. Keep this status snapshot separate from cumulative transfer totals, so sending and receiving entries do not count the same physical units twice.
State what is counted: individual components, assemblies or packs. When that basis changes, record the conversion relationship, actual input consumed, output produced and any residual or rejected quantity. Do not reconcile unlike units by simply subtracting their totals.
Have the receiver acknowledge the actual identity and quantity received, with who checked it and when. Preserve the sender’s entry if the physical handoff differs; link a receiving discrepancy and record the affected subset’s status while the difference is resolved.
04Connect operation entries to retrievable evidence
A practical traveler record structure connects the issued route to each execution attempt, its evidence and any associated exception. Keep the review record linked to the specific entries examined, so a later reader can reconstruct what supported the review decision.
Review record → issued traveler → operation attempt → result records Operation attempt → associated exception → disposition record Review record → evidence examined and decision recorded
Use an attempt identifier combining the traveler identity, planned operation identity and a distinct execution suffix. A repeated test then has its own identity rather than replacing the first attempt. Link each result to the affected serials, lot or subset and the applicable test or inspection instruction revision.
Identify the actual report, attachment or instrument record—not merely the test name or a folder. Where relevant, include measured values with units, equipment identity and the applicable acceptance-criteria reference. A reference to the applicable inspection record should retrieve the observations for this execution, not a blank form or another job’s report.
For attributable recording, distinguish who performed the work, who recorded the observation and who reviewed the evidence, even when one person fills multiple roles. Label each signature’s meaning, such as execution confirmation or evidence review. Record the relevant event time and time-zone context; distinguish execution time from later entry or review time. One unexplained signature column obscures these differences.
Use durable record identifiers and defined retrieval arrangements: a paper packet and page locator, an electronic record with its retained version, or a hybrid cross-reference connecting both. Give authorised reviewers access to the referenced evidence. Avoid links that resolve only to a mutable latest document; the reference should retrieve the evidence actually reviewed.
As proposed recordkeeping practice, retain the original entry when correcting it and identify the change, its reason, the person making it and when it occurred. Keep the correction traceable from the affected attempt.
Review record
Identifies the decision and its evidence.
- review_id
- traveler_id
- decision_type
- reviewed_by
- evidence_refs
Issued traveler
Identifies the job and applicable route.
- traveler_id
- job_id
- part_number
- part_revision
- route_revision
Operation attempt
Connects execution to the applicable instruction.
- attempt_id
- traveler_id
- operation_id
- instruction_id
- instruction_revision
- performed_by
Result record
Preserves the attributable observation or measurement.
- result_id
- attempt_id
- measured_value
- unit
- result_status
- recorded_at
Disposition record
Explains the treatment of affected work.
- disposition_id
- attempt_id
- result_id
- affected_units
- decision
- authorised_by
05Case: assembly completed, test evidence missing
Assume hypothetical job JT-ALPHA contains 24 sensor assemblies, each remaining one countable unit throughout this example. All identifiers, revisions, route conditions and outcomes are fictional, not approved customer specifications. The product is SENSOR-ASM revision C; the applicable instructions are WI-ASSEMBLE revision D and WI-FUNCTION revision B. Issued route revision E contains assembly, inspection, functional test and packing. Under this assumed route, packing is conditional on reviewed passing functional-test evidence for each assembly.
All 24 assemblies have assembly-completion entries and acceptable inspection records. The functional-test route is ticked complete, but review finds only 23 attributable passing test records. Serial A-17 has no retrievable result behind its tick. Its status is an evidence hold, not a recorded test failure: the reviewer cannot establish whether it passed, failed or was actually tested. A recorded failing result would instead establish that an executed test did not meet its acceptance criteria.
The test-review balance is: 24 units = 23 units with documented passing results + 1 unit on an evidence hold + 0 scrapped units. This is an evidence-status balance, not a declaration that every assembly conforms. It leaves A-17 visible in the job quantity rather than allowing the completed route tick to hide it.
The reviewer searches using unit A-17, operation-attempt identifier FT-A17-FIRST and instrument-record identifier IR-ALPHA-A17. If records cross systems, MES-to-LIMS integration is relevant to maintaining that linkage. A reference correction is appropriate only if the original result can be reliably matched to this unit and attempt under WI-FUNCTION revision B. Record who corrected the reference, when and why; preserve the original entry. A nearby passing result is not a substitute.
If retrieval fails, the responsible reviewer documents the investigation decision and whether technically appropriate retesting is authorised. Any retest receives its own attempt identity and actual execution record; nobody invents a measurement or backdates execution. Under this example’s route conditions, the reviewer permits the 23 supported units to proceed to packing. A-17 remains separately identified on hold, with its unresolved evidence reference carried forward. That handoff does not authorise distribution.
06Case: one job split across two stations
Assume a hypothetical job, JT-BETA, contains 120 diagnostic-cartridge assemblies and splits once between equivalent authorised stations. Processing does not create additional assemblies. All identifiers and quantities below are illustrative; no engineering limits or real customer specifications are assumed. The traveler assigns 70 assemblies to child subset BETA-A and 50 to BETA-B before either station starts work.
Each subset receives its own handoff identity and operation-attempt records, linked to JT-BETA. This uses a parent–child record relationship without assuming that the split creates new manufacturing lots. Each station records its performer, applicable operation and instruction revision, quantities received, outcome quantities and result references against the subset actually processed.
- Station A: 70 assemblies = 66 accepted for the operation + 3 held + 1 scrapped.
- Station B: 50 assemblies = 46 accepted for the operation + 2 held + 2 scrapped.
- Parent reconciliation: 120 assemblies = 112 accepted + 5 held + 3 scrapped. Accepted: 66 + 46 = 112; held: 3 + 2 = 5; scrapped: 1 + 2 = 3.
The proposed merge handoff contains only the 112 operation-accepted assemblies. Its receiving entry identifies the contributions from BETA-A and BETA-B rather than recording an unexplained total. Acceptance here concerns this operation, not distribution authorisation. The five held assemblies retain their subset identities, physical hold locations and exception references; they are not included in the proposed onward quantity.
Keep physical segregation, subset records and parent totals distinct. Combining the accepted assemblies into an onward container does not combine the held material or erase the scrap history. The three scrapped assemblies remain accounted for through their originating subsets, with scrap reason records supporting their recorded disposition. A consolidated record is not evidence that every physical assembly moved together.
Treat the parent view as a roll-up, not another quantity transaction: posting both child outputs and the parent total as production would double count the same assemblies. After consolidation, a reviewer can still retrieve Station A’s and Station B’s separate performers, operation attempts and results. Any later movement of held assemblies is recorded separately against their retained subset identities.
07Case: rework without rewriting the original result
Assume job JT-GAMMA contains 40 cable assemblies identified as G001–G040. All identifiers, instructions, route decisions and outcomes in this example are fictional, not approved customer specifications. Initial electrical testing records 40 assemblies = 34 passing assemblies + 6 failing assemblies held for disposition, with no initial scrap. The held units are G035–G040; their first test results remain part of the job history.
Hypothetical disposition DISP-GAMMA authorises those six identified units for connector rework under WI-RW revision B, followed by electrical retest under WI-ET revision C. The disposition defines packaging entry as the return point for units whose retest results are reviewed and accepted. This is a job-specific rework route, not permission to repeat repairs until a passing result appears.
Issue branch JT-GAMMA-RW linked to JT-GAMMA, G035–G040, each failed electrical-test attempt, its original result record and DISP-GAMMA. Linking only to the parent job would leave the reviewer to infer which units and failures the authorisation covers. Keep the branch identity on its handoff record so the receiving station can distinguish returning units from untouched work.
Record connector rework and retest as separate operation attempts against each affected serial. Each attempt captures the instruction revision used, performer, completion time and relevant execution or result reference. Preserve all six original failing results; later passing results do not replace them. The history then shows what failed, what intervention occurred and what the subsequent test established.
Retest produces 6 assemblies = 5 passing assemblies + 1 assembly subsequently dispositioned to scrap. After that scrap disposition is recorded, final in-process quantity reconciliation is 40 assemblies = 39 operation-accepted assemblies + 0 held assemblies + 1 scrapped assembly. The accepted total is 34 + 5. Rework and retest are processing events on existing units, not additions to the original job quantity.
At packaging entry, the designated reviewer checks the five returning serials against the disposition, completed rework attempts and accepted retest evidence. The scrapped serial does not return. Any further intervention would need a separate disposition decision; this example establishes neither a universally acceptable repair method nor an allowable number of attempts.
08Review missing operations and keep decisions separate
A practical traveler review compares the issued route, authorised changes and recorded operation attempts—not just filled boxes. Match each applicable operation to its attempts and evidence references. Investigate missing, duplicated, out-of-sequence or unexplained entries; a repeated attempt may represent legitimate rework rather than an accidental duplicate.
- Not performed: identify the affected work, establish its status and refer the omission for an authorised recovery decision. Do not substitute a retrospective completion tick for execution.
- Performed without adequate evidence: investigate the evidence gap, retrieve attributable records where possible and assess whether they support the result. Any decision to repeat work follows an authorised path, preserving the original uncertainty.
- Made inapplicable: link the authorised route decision, its scope and rationale to the affected operation. An unexplained blank does not communicate an approved exclusion.
Use explicit signature purposes to distinguish the following human decisions. Assign responsibilities locally rather than assuming that a particular job title owns every decision.
- Operation completion records the execution decision: what work was performed.
- Result review assesses the supporting evidence against the applicable acceptance criteria.
- Nonconformance disposition governs what happens to affected work.
- Traveler closure determines whether the record is complete, including resolved or explicitly transferred exceptions.
- Distribution authorisation separately determines whether the product may enter distribution.
A route tick or completed traveler is not proof of product release. For each exception, link the relevant deviation record or disposition and record an attributable review conclusion: reviewer, date, evidence considered and outcome. Unresolved references remain visible rather than disappearing behind closure. Where electronic history explains a questionable entry, use a focused audit trail review. Check the supporting records themselves: a complete-looking route can conceal incomplete evidence. The assembly, split-job and rework cases above illustrate why these review paths differ without changing the meaning of completion.
09Place device travelers in the right regulatory context
For US medical-device manufacturing, check the current text of 21 CFR Part 820 and FDA’s Quality Management System Regulation overview for scope. FDA identifies QMSR as the revision of Part 820 effective 2 February 2026, incorporating ISO 13485:2016. The standard, Medical devices – Quality management systems – Requirements for regulatory purposes, concerns medical-device quality management systems. That regulatory context does not itself specify the proposed traveler layout.
When interpreting older US device-production documents, distinguish historical references from current scope. Do not turn legacy DHR terminology into a present-day traveler field specification. Keep the transition and incorporated-standard questions separate from document design; QMSR versus ISO 13485 provides related context without making the traveler an ISO clause checklist.
Use FDA MDSAP Audit Approach production-process and product-status questions as audit-guidance context and review prompts, not as binding US traveler requirements. Treat traveler terminology, proposed fields, route controls and signature arrangements as manufacturing practice rather than a universally prescribed FDA form. Establish their suitability for the work concerned. This US medical-device discussion should not be extended to other jurisdictions, product categories or aerospace practices.
10Keep linked systems consistent when work changes
A practical responsibility map assigns ERP the job identity and planning references, the traveler record the operation execution history, result repositories the measurements, and the quality record the exception disposition. Designate an authoritative record and responsible owner for each information type; linked copies should not become competing originals.
Connect these records through stable job, traveler, operation-execution, unit or lot, and result identifiers rather than copying every attachment into the traveler. For MES–QMS integration, link an exception to the affected execution and its disposition record. Keep scheduled quantity distinct from quantity actually issued and from quantities recorded at subsequent handoffs: a planning change does not rewrite physical movement.
Distinguish an event recorded locally from a message sent and a transfer acknowledged as accepted by the receiving system. A process event log can provide the reconciliation trail. Match duplicate messages against stable event identities before applying quantity changes again. For delayed messages, establish execution order rather than treating arrival order as production sequence.
If updates conflict, make the discrepancy visible to the responsible person and reconcile the affected work before further transactions against that disputed state. A completion flag is not a conflict-resolution rule. Record the resolution and retain the conflicting submissions so the chosen state remains explainable.
For offline work, preserve operator identity, work identity, capture method, recorded execution time, and later synchronisation time. Distinguish contemporaneous recording from delayed transcription rather than making a later entry appear to have occurred online during execution. When a job is cancelled or superseded, retain work already performed, identify the replacement job where applicable, and explicitly account for remaining work in progress. Cancellation changes the job’s status; it should not erase its execution history.
11Test the traveler with a focused retrieval trial
A practical starting point is a bounded trial for one representative product family and its meaningful route variants, including splits or rework where applicable. Treat this as a local usability exercise, not a universal implementation plan.
- Assign ownership. Name individuals responsible for route definitions, identifier conventions and interface mappings, with a clear contact for resolving inconsistencies discovered during the trial.
- Observe recording at the station. Ask the operator to capture evidence while performing the task, using the actual paper form or shop-floor terminal. Note any step that depends on later memory, inaccessible references or another person's login.
- Test independent retrieval. Give a reviewer a selected traveler and ask them to locate its applicable instructions, operation evidence and exception decisions without coaching from its operator.
- Check access over time. Test production and reviewer access to paper attachments and electronic references. Include archived records and superseded instruction revisions to assess continued retrieval, not merely whether today's links open.
- Remove avoidable friction. Record unnecessary transcription and ambiguous fields. Revise them, then repeat the affected recording and retrieval tasks to judge whether the change actually helps.
A successful local trial demonstrates those tasks under the conditions tested. Keep broader system-suitability assessment, including any applicable computer software assurance work, and assessment of regulatory obligations separate.
Frequently asked questions
Q.Can one traveler cover a mixed lot when every unit follows the same operation route?+
A shared route alone is not enough. A common traveler can be practical if each constituent lot remains identifiable and entries clearly show which units, quantities and results they cover. Check whether instruction revisions, sampling arrangements, acceptance criteria or disposition differ between lots. Where these differences make a shared entry ambiguous, use separate travelers or clearly linked subrecords. Preserve lot identity at every handoff; sharing paperwork should not imply merging lots. Define any inspection population separately from this administrative grouping; see Inspection Lot.
Q.How should a traveler record a temporary instruction supplement?+
Give the authorised supplement its own identifier, applicable operations and work boundary; refer to the mid-job applicability discussion above for revision decisions. A temporary supplement also needs a clear end condition, such as completion of specified serials, not an assumption that everyone knows when it expires. Preserve the base instruction reference alongside the supplement and make both retrievable. At closure, check whether the supplement was withdrawn, absorbed into a later revision or remains applicable to unfinished work. These are proposed controls, not a universal FDA supplement format.
Q.What happens to traveler references when a result repository is replaced?+
Test existing references against the proposed replacement before retiring access to the earlier repository. A practical migration crosswalk maps each retained result identifier and version to its destination without changing the traveler’s historical meaning. Include paper references, attachments and rejected results in the retrieval exercise, not just current passing reports. Investigate unmatched references and keep a usable retrieval path until their disposition is resolved. Record migration checks separately from the original observations; successful copying alone does not establish data integrity or prove that every reference still resolves.
Q.Can the next station accept work while a required result is still missing?+
Distinguish receiving physical custody from accepting work for further processing. A station can receive identified work into a controlled hold when the site’s arrangements allow it, but a missing prerequisite result should not be treated as satisfactory. Record the missing evidence, affected quantity, location and restriction. If further processing is proposed, seek a documented decision from the designated authority under the applicable procedure. An exception record supports the disposition decision; opening that record alone does not grant permission.
Q.When does a split job need child travelers rather than another quantity line?+
Child travelers are useful when branches need independent execution histories: different stations operating concurrently, different remaining routes, separate holds, or different rework decisions. Another quantity line may be enough when the split is only a temporary physical separation and every entry still identifies the affected work unambiguously. Base the choice on whether each branch’s identity, quantities, status and evidence remain independently readable. At reunion, reconcile branch quantities and unresolved holds before recording the combined handoff. The split-job case above shows why the parent total is not another production transaction.
Q.What evidence supports marking an operation not applicable?+
A not-applicable entry should point to an authorised applicability rule or a documented technical decision covering the identified job and operation. Useful supporting evidence includes the relevant product variant, route condition, specification reference and decision-maker’s identity. Distinguish an operation excluded by the route from one that was missed or could not be completed. The latter needs assessment, not retrospective relabelling. If applicability depends on an earlier result, reference that result and show how it satisfies the specified route condition.
Q.How should production recover a lost traveler or handle a duplicate copy?+
First establish the work’s identity, location and last supported operation status; pause progression where uncertainty affects the next step. Reconstruct missing entries only from attributable records, identifying the replacement and its basis rather than recreating signatures from memory. For duplicates, designate the authoritative record and reconcile conflicting entries without discarding their history. If the original later appears, assess it against the replacement. Record unresolved gaps for disposition. These actions preserve batch execution history instead of merely producing a clean-looking form.
Q.Who can sign an operation entry when the person who performed it is no longer on shift?+
A replacement signer should attest only to what they actually did or can substantiate in their assigned role. A supervisor may document a review of machine records or other attributable evidence, but should not sign as though they performed the operation. Where the procedure permits a later entry by the original operator, distinguish the entry time from the operation time. If performance cannot be substantiated, escalate the gap rather than substitute a convenient signature. The attribution section above distinguishes execution, recording and review roles.
Primary sources
Want to see how Job Traveler could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
