How to test a drawing revision handoff before the next CNC run
Use one changed print and one open CNC job to test which revision reaches planning, machining and inspection, and who can release the work.

At 2:15, the plan and the job packet disagree
In this hypothetical shop, engineering approves drawing C for open job 5821 at 2:15. Planning sees C in the job record. At the machine, the machinist opens the printed packet and finds B. Inspection still has a B worksheet, and parts from the earlier run are already in a tote. Before anyone starts the next run, the team needs to know which units the change applies to and where that decision is recorded.
Quindart’s CNC software approach follows drawing changes alongside the orders, materials, tooling and inspection decisions they affect. For this exercise, start with two documents the team already uses: the work order and the drawing in the packet. Then compare them with the quality record and what is physically staged. You do not need a new system to see where the versions part company. [1]
Write down the decision for this job and quantity
Run the exercise on a training job or duplicate record. Suppose C changes a dimension that inspection checks. Have the person authorized under your procedure record the applicable revision, job number, affected quantity and what to do with units already made under B. Until that last decision is recorded, keep the earlier units visibly on hold. The exercise tests the handoff, not whether a particular part is acceptable.
Ask the planner, machinist and inspector to show the screen or sheet they would actually use. Compare their answers with the disposition record. One person opening the right drawing does not tell you what the other two can see or whether they can distinguish the earlier units from the ones covered by the change.
Leave the older print in the test packet
Run once with the records aligned. On the second pass, leave B in the training packet and keep the B inspection worksheet visible. Give the team the same task: show, from the records at hand, what applies to the next run and what happens to the earlier units. Use the matrix to record what each person can see and where they would send the exception.
NASA’s Systems Engineering Handbook describes configuration change management as including verification that the approved change was actually implemented. It also describes tracking the disposition of discrepancies. That is an example from NASA’s own practice, not a CNC shop requirement. For this exercise, it sharpens one question: can the team demonstrate where C took effect, rather than merely show that C was approved? [3]
| Role | Record in front of them | What conflicts | Who must record or act |
|---|---|---|---|
| Planner | Work order points to drawing C | Packet still shows B | Send the mismatch to the disposition owner. Do not clear readiness from the schedule alone. |
| Machinist | Paper job packet contains drawing B | Work order points to C | Flag the disagreement and show the exact packet used. |
| Inspector | B worksheet and tote of earlier units | C changes a dimension. Earlier units have no recorded disposition. | Keep the units on hold and ask the authorized owner for a recorded decision. |
| Authorized disposition owner | Approved drawing C and the job’s change record | The next run and earlier units may not share the same disposition. | Record which revision and quantities apply, who authorized the decision and what remains on hold. |
Agree on what a pass looks like
In the aligned pass, all three roles should show the same recorded disposition and identify the units it covers. In the stale-packet pass, someone should catch the mismatch before the exercise treats the job as ready. Check that the authorized person’s decision reaches the packet or record actually used at the machine and in inspection. An email delivery receipt is not evidence that anyone found the applicable drawing.
Note where someone first had to leave their usual records to resolve the discrepancy. If the job opens an obsolete file, fix the link or the handoff that maintains it and rerun the test. If all three people see C but the earlier units have no disposition, name the decision owner and fix that gap first. Either result tells you more about what to automate than a demo on a job where nothing changes.