Tolerance Stack-Up Documentation: Keep Decisions With CAD

Contents
- Step 1: Name the requirement or fit the stack-up protects
- Step 2: List every contributor with its source in CAD and on the drawing
- Step 3: Record the method and the assumptions behind it
- Step 4: Record the result, the margin and a named owner
- Step 5: Link the stack-up to the requirement, the CAD features and the released drawing
- Step 6: Catch the CAD change that silently invalidates the stack-up
- Step 7: Re-run, re-record and carry the stack-up through review, ECO and baseline
- What to do next: a stack-up documentation checklist
Good tolerance stack-up documentation records the requirement the stack protects, every contributor with its source in CAD and on the drawing, the method and assumptions, the result with its margin, and a named owner. It then links all of that to the CAD features and the released drawing so a later change cannot go unnoticed. The math can live in your own spreadsheet or analysis tool. What fails on medical device and aerospace programs is the record around the math.
This guide follows one stack-up from requirement to released drawing, then shows the CAD change that quietly invalidates it. Prerequisites: a stack-up you already run (worst-case or RSS), a CAD model with the contributing features, and a drawing with GD&T. Tandem does not perform tolerance analysis. It is the context layer that holds the record: cells as live attributes, links to the requirement and CAD features, a 3D diff, and 2D drawings with GD&T generated from CAD files.
Step 1: Name the requirement or fit the stack-up protects
Start with the functional characteristic, not the dimensions. Write one sentence: what gap, fit or clearance must hold, its allowable minimum and maximum, and the condition it applies under (assembled, at temperature, after sterilization, at max load).
Example: a connector housing on a handheld medical device needs a seal compression gap between 0.20 and 0.60 mm. A stack-up with no stated requirement is just arithmetic. Nobody can tell later whether a 0.15 mm result is a failure or a curiosity.
In Tandem, enter this as a requirement with a parent and children, so the gap traces up to the design input it serves. Our guide on design verification traceability in medical device programs covers that chain. For critical-to-safety interfaces, link the requirement to the risk entry too. Tandem's FMEA and risk tables are trace-linked to requirements, so an unacceptable stack condition points at the risk it controls.
Step 2: List every contributor with its source in CAD and on the drawing
A contributor list is only auditable if each row says where the number came from. For every dimension in the loop, record the nominal, the tolerance or limits, the direction (sign) in the chain, the datum, the CAD feature it comes from, and the drawing and revision that call it out.
The common mistake is typing values into a spreadsheet and losing the pointer back to the model. Six months later, someone changes a fillet or a boss height, and nobody can tell which row it feeds.
Keep the table in Excel or Google Sheets, since that is where the team already works. Tandem treats spreadsheet cells as live attributes, so a contributor value becomes something the platform can reference instead of a number buried in a file attachment. Name the part and drawing revision in each row. If the drawing is generated from CAD, the GD&T on the released sheet and the model stay aligned by construction, and your source column can point at both.
Step 3: Record the method and the assumptions behind it
State the method and its conditions in the record, because the same chain gives different answers depending on how you combine it. Worst-case adds the sensitivity-weighted tolerances: every allowed combination of parts must meet the requirement. RSS combines independent contributors statistically and needs a stated coverage level, often plus or minus 3 sigma.
Record, at minimum:
Method (worst-case, RSS, or both) and the tolerance-to-sigma conversion if RSS
Whether contributors are independent, and any known correlation
Process mean and distribution assumptions, and what data supports them
Thermal effects, assembly sequence, and locating datums
Anything deliberately excluded, and why
Treat RSS as a statistical estimate, not a guaranteed limit. For a regulated device, worst-case is usually the defensible default for safety-critical interfaces, with RSS shown where the process data justifies it. Whichever you choose, the assumption is part of the decision. If it isn't written down, the next engineer will assume something else.
Step 4: Record the result, the margin and a named owner
Write down the numbers and the person. The result block needs the nominal stack, worst-case minimum and maximum, the RSS estimate with its coverage, the margin against each limit, and pass or fail against the Step 1 requirement. Add a ranked sensitivity list so the reviewer sees which contributor drives the margin.
Then name one owner. Not a team, a person, with the analysis date, units, drawing revision and the version of the spreadsheet or tool that produced the result. When an audit or a design review asks who signed off on this gap, the answer should take seconds.
In the seal example: nominal 0.40 mm, worst-case range 0.22 to 0.58 mm, margin of 0.02 mm on the low side. That 0.02 mm is the number that matters later. A thin margin tells everyone downstream that a small CAD change can flip the answer.
Step 5: Link the stack-up to the requirement, the CAD features and the released drawing
A stack-up that sits in a folder is a snapshot. A stack-up linked to the requirement, the contributing CAD features and the released drawing is a live dependency.
In Tandem, make three links:
Requirement: the Step 1 gap requirement, verified continuously against live attributes. The result and margin from your spreadsheet cells feed the check, so the requirement shows its own status and nobody has to remember to update it.
CAD features: the contributing parts and features in the SolidWorks, Onshape, CATIA, NX or Fusion model, so the connection from dimension to stack-up is explicit.
Released drawing: generate the 2D drawing with GD&T from the CAD file in Tandem, and release it through Tandem PDM (check-in and check-out, soft revisions, a release workflow; live for SolidWorks) or alongside your existing PLM.
The design intent behind each tolerance, such as why a bore is held to a tight position, sits in the same record. A reviewer needs that when asking whether a tolerance can be loosened.
Step 6: Catch the CAD change that silently invalidates the stack-up
Here is the failure. Three weeks after the stack-up was signed, a designer increases the height of a mounting boss by 0.15 mm to fix a clearance issue with a PCB standoff. The change is sensible locally. It adds directly into the seal gap loop, and the 0.02 mm margin is now negative at the worst-case limit.
No one touched the spreadsheet. The drawing still shows the old value until it is regenerated. The review that approved the stack-up is already closed. The problem surfaces at first-article inspection, or worse, in a verification test.
This is what Tandem's design change view is for. It shows a before and after 3D CAD diff with a plain-language summary and the affected requirements and annotations. Because the boss feature is linked to the seal gap requirement, the change shows up against that requirement the moment it is made, not at inspection. If you ran a similar loop on a robotics program, change impact analysis for robotics mechanical engineers walks through the same mechanism on another product.
Step 7: Re-run, re-record and carry the stack-up through review, ECO and baseline
When the diff flags the stack-up, re-run it in your own tool with the new boss height and update the contributor row. The live attribute updates, the requirement re-verifies, and the record keeps a redlined history of the old value, the new value and who changed it.
Then carry it forward:
Design review: reviewers open the model in the browser 3D viewer, no CAD license needed, and comment on the geometry. Annotations surface inside the CAD tool, so the designer sees the stack concern where the feature lives.
ECO: Tandem generates the ECO or ECN and supporting documentation from the captured CAD change, in your own templates, with the affected stack-up included. See ECOs from CAD changes for medical device manufacturing engineers.
Baseline: when the design freezes, the signed stack-up, linked requirement, CAD revision and released drawing go into the baseline together, so the next change is compared against a known state.
If the margin can't be recovered, the change goes back to the designer with the number, not a vague concern.
What to do next: a stack-up documentation checklist
Take your most critical stack-up and check it against this list: requirement and limits stated; every contributor with CAD feature, drawing and revision; method, independence and sigma assumptions written down; result, margin and a named owner; links to the requirement, the CAD features and the released drawing; a diff that flags changes to any contributor; a re-run step tied to your ECO and baseline. Any gap is where the next silent invalidation will land. Book a demo of Tandem and bring one real stack-up. We will walk it from requirement to released drawing and show what happens when a contributing feature changes.
Visit Tandem
Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.
Get startedSources
Frequently asked questions
What should tolerance stack-up documentation include?
Include the requirement and its limits, a dimension chain with each contributor's nominal, tolerance, sign, datum and CAD and drawing source, the method and assumptions, results with margin, a ranked sensitivity list, and a named owner. Tandem holds this as a linked record tied to the requirement, CAD features and released drawing.
How do I know when a CAD change invalidates a tolerance stack-up?
You only know if the stack-up is linked to the contributing CAD features. In Tandem, the before and after 3D diff shows the change with a plain-language summary and the affected requirements, so a changed contributor is flagged when it is made, not discovered at inspection.
Does Tandem perform tolerance stack-up calculations?
No. Run worst-case or RSS in your own spreadsheet or analysis tool. Tandem keeps the decision record: cells from Excel or Google Sheets as live attributes, links to the requirement and CAD features, and 2D drawings with GD&T generated from CAD files.
Should I use worst-case or RSS for medical device or aerospace stack-ups?
Worst-case is the usual default for safety-critical interfaces because every allowed part combination must meet the requirement. Use RSS only where process data supports independence and distribution assumptions, and state the coverage level. Record the choice and reasoning in the stack-up documentation so reviewers and auditors see it.
Related reading
Written by
Tandem
Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.