Routing Sheet Template: Defining the Operation Sequence Per Part

Why the Same Part Runs Differently Every Time It's Made

Pull the last five jobs for one part number off the shelf and lay their paperwork side by side. On a lot of shop floors, no two of them look the same. One traveler has the deburr step before inspection, the next has it after. One lists three setups on the mill, the next combines two operations because the setup guy that week decided it was faster. Nobody wrote any of this down as a rule — it lives in whoever happened to run the job, and it changes every time that person changes.

This is usually invisible until it costs something. A customer calls asking where their job is, and the answer depends on tracking down whichever operator last touched it. A quarter closes and the margin on a job that should have been profitable came in soft, and nobody can say which operation ate the hours. An AS9102 first-article inspection comes back with a nonconformance because the sequence used for the first article wasn't the sequence used for the sequence used for production. In every case, the root cause is the same: the operation sequence for that part number was never fixed in writing, so it drifted.

A routing sheet is the fix. It's the document that says, for this part number, in this order, these operations happen at these work centers, and here is the time each one should take. Get that structure right once per part number, and it becomes the backbone of every traveler you print from then on. Here's how to build one.

What a Routing Sheet Actually Defines

A routing sheet is not a to-do list — it's a structured, ordered specification. For a single part number, it answers four questions, in order:

1. What operations happen, and in what sequence? Saw, then mill, then deburr, then inspect, then pack — numbered, not implied.
2. Which work center performs each operation? Not "the mill" but a specific, named work center if the shop has more than one of a given machine type.
3. What is the standard time for each operation? Split into setup time (fixed, regardless of lot size) and run time (per piece, multiplied by quantity).
4. What has to travel with the part at each step? Tooling references, fixture numbers, inspection criteria, print revision — whatever the operator or inspector needs without walking to find it.

Once those four answers exist for a part number, they don't need to be reinvented on the next job. That's the entire point of a routing sheet: it converts tribal knowledge about how a part gets made into a reusable, auditable record.

The Core Fields of a Routing Sheet Template

A working routing sheet template needs a small, consistent set of columns — resist the urge to make it more complex than the shop floor will actually fill in. At minimum:

• Op # (sequence number) — the order operations occur, not the order they were dreamed up in.
• Work center — the specific machine, cell, or station, matched to how the shop actually tracks capacity.
• Operation description — plain language: "mill pocket per print rev C," not a part-program filename only the programmer understands.
• Setup time (standard) — the time budgeted before the first good piece, independent of lot size.
• Run time per piece (standard) — the time budgeted per unit once setup is complete.
• Tooling / fixture reference — so the next operator doesn't have to hunt for what the last one used.
• Inspection requirement (if any) — in-process check, final inspection, or first-article hold point.

That's the field list. Everything else — revision control, customer PO reference, material lot traceability — sits at the header level of the sheet, not repeated per operation row.

Notice what's deliberately absent: due dates, machine load, or "who's free today." A routing sheet defines how a part is made, not when it gets scheduled against everything else in the shop. Confusing those two jobs is one of the most common structural mistakes shops make when they first try to formalize this — more on the difference between routing/traveler documents and a router below.

Routing Sheet, Router, Traveler: Getting the Terms Straight

These three terms get used interchangeably on shop floors, which causes real confusion when a shop tries to standardize:

• The routing (or routing sheet) is the master specification per part number — the sequence, work centers, and standard times described above. It's a reference document, maintained once and reused.
• The router, in most shops' usage, is functionally the same artifact as the routing — the ordered list of operations a part must pass through.
• The traveler is the job-specific instance of that routing: the printed or digital document that accompanies one particular job through the shop, carrying the routing's sequence plus whatever gets logged against it — actual times, scrap notes, operator sign-offs, inspection results.

Put simply: you define the routing once per part number, and a new traveler gets generated from it every time that part number gets a new job. If your shop currently rebuilds the sequence from scratch on every job instead of pulling it from a saved routing, that's the gap worth closing first — see the fuller breakdown of the traveler vs. router distinction and a dedicated part routing template for machine shops.

Building the Operation Sequence: A Worked Example

Here's how the fields come together for one part, using round, illustrative numbers for a representative job — not figures from any specific shop:

Part: Bracket, Rev C. Quantity: 50 pieces.

Op #	Work Center	Description	Setup (std)	Run/pc (std)
10	Saw-1	Cut blank to length	0.2 hr	0.02 hr
20	Mill-3	Mill pocket + drill per print	1.0 hr	0.15 hr
30	Deburr	Deburr all edges	0.1 hr	0.03 hr
40	Inspect	First-article + final dimensional check	0.3 hr	0.02 hr

Roll that into a standard job time: setup totals 1.6 hours, run time totals (0.02+0.15+0.03+0.02) × 50 pieces = 11.0 hours, for a standard total of 12.6 hours. That 12.6-hour figure is what a quote gets built against — and it's also the number every actual clock-in on this job will later be measured against, operation by operation, once the job is running. That comparison — actual hours logged at Op 20 versus the 0.15 hr/pc standard — is where a routing sheet stops being paperwork and starts being a costing tool.

This is also where the sequence number matters beyond documentation. If Op 30 (deburr) gets skipped or done out of order on a real job, that's visible against the routing the moment someone logs time against the wrong operation number — not six weeks later at quarter close.

From Routing to Traveler: How the Sequence Reaches the Floor

Once a routing sheet is defined for a part number, it needs a mechanism to become the document operators actually work from. This is the specific gap WorkTickets is built to close: a routing/operation-sequence builder lets a shop define the sequence, work center, and standard time per part number once, and then generate a traveler from it for every new job against that part — either a printed PDF (with an optional barcode or QR code for a physical route sheet clipped to the job) or a digital view pulled up on a shop-floor tablet or phone.

From there, the operation sequence isn't just a reference — it's what the clock-in screen checks against. An operator scanning in at Op 20 is logging time against a named operation with a standard attached to it, which is what makes actual-vs-quoted comparison possible at the operation level rather than only at the whole-job level. Scrap or rework logged during a job gets tied to the specific operation that caused it, not to the job in general — so a recurring defect at deburr shows up as a pattern at deburr, not as vague "job 4471 came in over."

None of that works without the routing sheet existing first, in a consistent format, per part number. The sequence is the foundation everything else — the traveler, the WIP queue view, the actual-vs-quoted report — gets built on top of.

Common Mistakes When Defining the Sequence

A few patterns show up repeatedly in shops formalizing this for the first time:

• Combining operations that belong on separate rows. If two steps happen at different work centers or have meaningfully different standard times, they need separate rows — even if the same operator does both back to back.
• Leaving out setup time as a separate field. Blending setup and run time into one number makes it impossible to see whether a job ran over because of a slow setup or a slow per-piece rate — two very different root causes.
• Skipping the inspection hold points. If a first-article or in-process check isn't written into the sequence, it gets skipped under schedule pressure — and that's exactly the kind of gap an AS9102 auditor or a customer's incoming inspector will find.
• Treating the routing as scheduling. A routing answers "what order do operations happen in," not "when does this job run relative to everything else on the floor." Keep those separate.

Standardizing Routing Sheets Across Your Part Numbers

The pattern above scales the same way whether it's one part number or two hundred: define the sequence once, in a consistent field structure, and reuse it every time that part gets quoted and run again. Shops that skip this step end up rebuilding the sequence from memory on every job — which is exactly the drift this article opened with.

A ready-made shop traveler template and a routing builder walkthrough for defining sequences per part number are good next steps if you're standardizing more than a handful of parts. For a broader view of how routing, traveler generation, clock-in, and actual-vs-quoted costing fit together as a single system rather than separate spreadsheets, the execution-and-costing guide for small job shops covers the full workflow.

If you'd rather start from a built template than a blank spreadsheet, the Traveler & Router Template Starter Pack includes an editable routing sheet structured around the fields above, ready to adapt to your own part numbers. And if you want to see the sequence turn into a live traveler with clock-in and actual-vs-quoted tracking attached, WorkTickets runs a 14-day trial across all self-serve tiers — no separate scheduling module, no inventory system bundled in, just the routing-to-traveler-to-costing layer this article describes.