Assembly plan, sequenced.
Also called: Work instructions · Build sequence · Assembly SOP · Operator routing
The step-by-step instructions an operator follows to build one correct unit: order of operations, tools, fixings, and a check at each step.
One sheet that turns a pile of parts into a built unit, in a fixed order, with a check before each next step. Get the sequence and the checks right and any trained operator builds a correct unit in a predictable time. Skip it and quality rides on memory.
What an assembly plan is
An assembly plan is the written sequence a person follows to build one unit from loose parts. It names the steps in the order they must happen, the tools and fixings each step needs, and the check that confirms the step is done before the next one starts. Done well, it removes judgement from the bench: the operator follows the sheet, not their memory.
Order is the whole point. Some steps can only happen in one sequence, because a later step blocks access to an earlier one. On the proofing box, the heating element and temperature sensor have to go into the ceramic base before the PCB carrier mounts over them, because once the carrier is in, you cannot reach the element seat. Get that order wrong and the operator either reworks the unit or, worse, ships one that fails its function test. The plan locks the sequence so nobody has to rediscover it under time pressure.
The other half of the job is the check at each step. A good step does not just say “fit the element”; it says “fit the element, then confirm the sensor reads ambient before you go on”. Each check catches the error while it is still cheap to fix, at the bench, rather than at the function test where a buried fault means stripping the unit back down.
Assembly steps, the proofing box
Here is the shape of the plan for the proofing box we ran through the finishing partner, so you can see what a real sequence looks like rather than a generic template.
The two halves below show why the order and the checks belong on the sheet rather than in the operator’s head.
- Hand the operator a pile of parts and a photo of the finished unit.
- No fixed order, so the carrier goes on before the sensor is checked.
- No torque called out; screws done by feel.
- Faults only show up at the final test, when they are expensive to fix.
- One sheet, steps in a fixed, access-driven order.
- Each step names its tools, its fixings, and its torque.
- A check closes each step before the next one opens.
- Most faults are caught at the bench, not at the function test.
How it fits the bigger picture
Assembly plan is activity 09.10.05 in the framework, inside Stage 09 Manufacture. It takes the parts and finishes defined upstream and turns them into a repeatable build. The work instructions it produces feed straight into the PLM system (09.10.06), where the plan, its revisions, and the bill of materials live as controlled documents the whole supply chain works from.
What it can do
It lets a new operator build a correct unit without the original engineer in the room, and it makes build time predictable enough to quote and schedule a batch. The checks at each step catch faults early, when they cost minutes rather than a stripped-down rebuild.
What it can’t do
It can’t fix a design that is awkward to assemble; if a step is genuinely hard, that is a design problem to push back upstream, not a wording problem. And it can’t stay correct on its own. Every change to a part or a finish has to flow back into the plan through the PLM system, or the sheet quietly drifts out of date.
See the full 10-stage process →
Try it yourself
Take one unit and build it slowly, writing down every action as you go. Note where a later step blocks access to an earlier one, that fixes your order. For each step, add the tools, the fixings with their torque, and one check that proves the step is done. Then hand the sheet to someone who has never built the unit and watch where they hesitate. Every hesitation is a gap in the instructions, not in the person.
Building toward your first production run? Start the Free Sprint → and the GPT will help you map the build before you commit to tooling.
Your assembly-plan checklist
Project notes: the sequence that saved the rework
▸ From the notebook · optional reading
Writing the proofing box build sheet with the finishing partner, and the one reordered step that stopped the reworks.
3 min read · click to open
The first build sheet we handed the finishing partner was honest but thin. It listed the seven steps in the right order, but the checks were vague: “fit element”, “fit carrier”, “test”. On the first batch of ten, three units failed the function test, and stripping them back to find the fault ate most of an afternoon.
What the failures had in common
All three had a sensor that read nothing. On every one, the operator had seated the element, dropped the sensor in beside it, then mounted the PCB carrier straight over the top, exactly as the sheet implied. The trouble was the sensor had shifted as the carrier went down, and once the carrier was on, you could not see it. The fault was invisible until the unit was nearly complete.
I asked the operator to walk me through it at the bench, and the gap was obvious in about a minute. The sheet told them what to fit but not what to confirm. So we added one line between two existing steps: “Before mounting the carrier, power the bench rig and confirm the sensor reads ambient. If it reads nothing, reseat it now.”
What the one line bought
- Cost. Ten extra seconds per unit, and one calibrated bench rig already on the bench for the final test.
- Saved. The next batch of twenty had zero sensor failures at the function test. The fault, when it happened at all, was now caught and fixed in seconds, with the carrier still off.
We also timed the corrected sequence properly across that batch and set a target build time per unit, which let the partner quote the next run honestly instead of padding it. The lesson stuck with me: a step on an assembly plan is not “fit the part”, it is “fit the part and prove it before you bury it”.
— Manufacture stage, project notes, 2026