Blitzpanel · Standard Operating Procedure

Job Traveler / Document Control SOP

Draft ID: SOP-0019 Version: 0.1.0 Owner: TBD Last reviewed: 2026-07-01

First draft for review. Cite comments by section & line — e.g. "§6 L4" means Section 6, line 4 (line numbers are in the left gutter and reset each section). Items marked TODO need Blitzpanel-specific confirmation.

1. Purpose

This procedure defines how Blitzpanel creates, moves, and controls the job traveler that accompanies every panel through the shop, and how released drawings and other build documents are kept under revision control while the job is in production.

It exists to guarantee that the shop floor always builds to the current, approved revision of every drawing and instruction, that every required inspection and signoff is actually recorded at the point it occurs, and that a complete, traceable record exists to support UL508A listing and customer requirements after the job ships.

A disciplined traveler and document-control practice prevents build errors from out-of-date drawings, closes the gap between "what was supposed to happen" and "what was verified to have happened," and gives Quality and Engineering a defensible paper trail during audits or non-conformance investigations.

2. Scope

Applies to every job released to the shop floor, from traveler creation at job release through final signoff and archival after shipment, for all panels, subpanels, and enclosure-modification work.

Covers the traveler document itself (routing, checkpoints, signoffs), the controlled set of drawings and instructions attached to or referenced by the traveler, revision marking and supersession on the floor, and retention/archival of the completed package.

Does not cover how a drawing revision is engineered, reviewed, and approved before release — see the Engineering Change Order / Revision Control SOP — nor the detailed criteria for individual test and inspection checkpoints, which are defined in their own SOPs and referenced from the traveler.

3. Definitions

Traveler (a.k.a. router or job packet) — the physical or electronic document that follows a specific job through every production stage, listing required operations, checkpoints, and signoffs in sequence.

Controlled document — any drawing, schematic, BOM, wiring diagram, or work instruction whose current revision is tracked and whose use on the floor is restricted to the latest released version.

Master file / master set — the single authoritative, current-revision copy of each controlled document for a job, held in the document control system, against which all floor copies are checked.

Revision (rev) — a tracked, approved change to a controlled document, identified by a revision letter or number and a date, per the Engineering Change Order / Revision Control SOP; the prior revision becomes a superseded copy that must be pulled from circulation and marked or destroyed.

Signoff — a dated initial or electronic acknowledgment by an authorized person that a specific traveler line item or checkpoint has been completed and verified.

Redline — a hand-marked, in-process correction to a drawing on the floor that has not yet been formally re-issued as a new revision.

4. Roles & Responsibilities

RoleResponsibility
Production Control / PlannerCreates the traveler at job release, attaches the current-revision document set, and sequences operations and checkpoints.
Document Control AdministratorMaintains the master file of controlled documents, distributes current revisions, and pulls/marks superseded copies. TODO: confirm who holds this role — dedicated admin vs. shared Engineering/Quality duty.
EngineeringIssues and approves drawing revisions and communicates them to Document Control before floor distribution (see ECO / Revision Control SOP).
Shop Floor Lead / OperatorVerifies the drawing revision at each station matches the traveler before starting work, executes the assigned operation, and signs off the corresponding traveler line.
Quality / QCVerifies signoff completeness at inspection gates, holds the job if a required signoff or current-rev document is missing, and reviews the completed traveler before shipment release.
Production ManagerOwns this procedure, resolves floor-level revision disputes, and approves exceptions. TODO: confirm title/owner.

5. Materials, Tools & Systems

Traveler template (paper router or electronic form) listing job number, customer, operations, checkpoints, and signoff fields. TODO: link the current Blitzpanel traveler template/form number.

Document control system of record holding the master, current-revision set of drawings, schematics, BOMs, and work instructions for each job. TODO: name the system (PLM/ERP/shared drive/paper binder) and who administers it.

Revision stamp, colored border, or watermark used to visually distinguish the current-revision floor copy from superseded copies. TODO: define the physical marking convention if paper copies are used.

Traveler routing folder or job box, and a barcode/QR or job-number label, used together to physically match the traveler, controlled documents, and panel at every station. TODO: confirm whether barcode/QR tracking is in use or planned.

Document archive/retention system for completed job packages after shipment. TODO: name the archive location (physical, network, or cloud) and access owner.

6. Procedure

6.1 Traveler creation at job release

On order acceptance and job release (see Ordering SOP), Production Control opens a traveler and assigns it the job number used on all related paperwork, labels, and the BOM.

Pull the current-revision document set for the job from the document control master file — schematics, panel layout, wiring diagrams, BOM, and any customer-approved submittal (see Customer Submittal / Drawing Approval SOP) — and record the revision letter/number and date of each document on the traveler cover sheet.

Sequence the traveler operations to match the actual production flow (kitting, cutting, wire duct/layout, wiring, subassembly, functional test, QC, packaging, shipping) with a signoff field for each.

Insert the traveler and the printed or authorized-access current-revision document set into the job routing folder before the job is released to the first work cell.

6.2 Verifying current revision on the floor

Before starting any operation, the operator compares the revision letter/number and date on the drawing in hand against the revision recorded on the traveler cover sheet.

If the two do not match, or if a drawing is missing a revision block entirely, stop work on that operation and route the traveler to Document Control or Engineering for resolution before proceeding — do not build to an unverified document.

Do not use personal, printed, or previously downloaded copies of drawings that are not the copy issued with the traveler; any such copy found on the floor is treated as unverified until checked against the master file.

When Engineering issues a new revision after a job has already been released, Document Control pulls and marks every superseded copy at every active work cell and reissues the current-revision copy with the traveler before work resumes on the affected operation (coordinate through ECO / Revision Control SOP).

6.3 Recording signoffs

The operator or inspector responsible for a traveler line signs (initials) and dates that line immediately upon completing and self-verifying the operation — not in advance and not in a batch at the end of shift.

Signoffs must be legible, attributable to a specific individual, and dated the day the work was performed. TODO: confirm whether electronic signoff (system login) is acceptable in place of handwritten initials.

At each defined inspection gate (see Design Checklist / Final Checkoff Gates SOP and the Functional Test / Power-Up Test SOP), QC confirms that every preceding traveler line is signed and dated before permitting the job to advance; an incomplete traveler holds the job at that station.

If an operation is skipped, deferred, or performed out of the traveler's normal sequence, note the reason and get Production Control or Quality concurrence noted on the traveler before proceeding.

6.4 Handling floor redlines and mid-build changes

If a floor issue requires an in-process correction to a drawing, mark it clearly as a redline (distinct color, dated, initialed) directly on the floor copy — never erase or obscure the original content.

Notify Engineering of every redline before the job advances past the affected operation; Engineering determines whether the redline becomes a formal revision or a one-time deviation (see ECO / Revision Control SOP).

Attach the redline sheet to the traveler package as a permanent record even if it is later superseded by a formal revision.

Any non-conforming condition discovered on the floor is logged and dispositioned per the Non-Conformance / Rework SOP, with the NCR number referenced on the traveler.

6.5 Job close-out and archival

Before shipment release, QC reviews the completed traveler for full signoff coverage, confirms every attached document reflects the final as-built revision, and resolves or documents any open redlines.

Reconcile the traveler and final revision set against the build report (see Build Reports SOP) so the shipped documentation package matches what was actually built.

Compile the closed traveler, final-revision drawing set, redlines, NCR references, and test/inspection records into the job's permanent record and file it in the document archive. This record supports UL508A listing documentation requirements. TODO: confirm archive retention period; verify exact UL508A clause before citing.

Remove and destroy or clearly mark as superseded any remaining floor copies of job-specific drawings once the job has shipped, so they cannot be mistaken for a current document on a future repeat order.

7. Records & Documentation

Completed traveler with full signoff history, including operator initials, dates, and any noted exceptions or deferrals.

Final as-built revision set of drawings, schematics, BOM, and any customer-approved submittal referenced by the job.

Redline sheets and their resolution (formal revision issued or deviation accepted), cross-referenced to the traveler.

NCR references for any non-conformance discovered and dispositioned during the build (see Non-Conformance / Rework SOP).

Retention period and storage location for closed job packages. TODO: set retention policy and confirm it meets customer contract and UL508A documentation requirements.

8. References

Ordering SOP, Engineering Change Order / Revision Control SOP, Design Checklist / Final Checkoff Gates SOP, Non-Conformance / Rework SOP, Customer Submittal / Drawing Approval SOP, Functional Test / Power-Up Test SOP, Build Reports SOP, UL508A Compliance Documentation SOP.

UL508A — Standard for Industrial Control Panels (documentation and marking basis for controlled drawings). TODO: verify exact clause references before citing.

NFPA 79 — Electrical Standard for Industrial Machinery (as-built documentation expectations, where applicable). TODO: verify exact clause references before citing.

Back to document index