AS9100 Design Change Records for Aerospace Quality Engineers

Contents
- What AS9100D clause 8.3.6 actually asks for
- Identifying a design change before it ships: catching the CAD edits nobody filed
- Reviewing impact: from the changed geometry to affected requirements, verification and customer notification
- Controlling the change: release workflow, authorization and configuration management
- Retaining documented information: the change, the review results, the authorization and the reasoning
- How Tandem supports the 8.3.6 record alongside your QMS and PLM
- A pre-audit checklist for one change record
- Make one change record hold the whole story
For AS9100 design and development changes, clause 8.3.6 asks you to identify, review and control each change, then retain documented information showing the change, the review results, who authorized it and what was done to prevent adverse effects. An auditor will pick one change and pull the thread. The records that hold up keep the reasoning, the impact review and the authorization together, not in four systems and one engineer's memory.
This article walks through 8.3.6 the way a quality engineer lives it: one change, one audit sample, and the questions that follow. It also covers where Tandem fits, as the place where CAD changes, requirements, reviews and release get captured while the work happens.
What AS9100D clause 8.3.6 actually asks for
Clause 8.3.6 asks for four things: identify, review and control design and development changes so they do not adversely affect conformity to requirements; notify the customer before implementation when the change affects customer requirements; control the change through the configuration management process; and retain documented information on the changes, the review results, the authorization and the actions taken to prevent adverse impacts.
Two details trip teams up. First, the clause covers changes made during or after development, so a post-release geometry tweak counts the same as a change during detailed design. Second, it does not require full verification and validation for every change. It requires you to assess whether the change affects conformity or invalidates earlier verification and validation results, then do the review, verification or validation that assessment calls for under 8.3.4. The record has to show the assessment was made. A conclusion alone won't pass.
Read it as a sequence an auditor can replay: what changed, who looked at what it touches, who said yes, and what you did to keep it from hurting conformity.
Identifying a design change before it ships: catching the CAD edits nobody filed
The first audit failure is rarely a bad review. It is a change nobody identified as a change. A wall thickness edit made during a supplier call, a fastener swap in an assembly, a tolerance opened up to fix a fit problem: each can alter conformity, and each can happen in CAD without a change request existing.
A quality engineer cannot watch every feature tree. What you can do is make identification a byproduct of the engineering work instead of a filing chore. Tandem's CAD integration includes Watch, which records a CAD session and groups feature-tree actions into described design goals. That gives you a description of what was altered and why it was attempted, captured as the designer worked. When a released design shows a different state than the last baseline, the before/after 3D CAD diff and its plain-language summary give you a defined change to put in front of a review, not a vague sense that something moved.
Tandem works with SolidWorks, Onshape, CATIA, NX and Fusion through direct plugins, so the capture happens in the CAD tool the designers already use. Here's a practical test for your own process: pick a released part, compare its current CAD to its released revision, and ask whether every difference has a change record. If you can't answer that quickly, identification is your weak point.
Reviewing impact: from the changed geometry to affected requirements, verification and customer notification
Impact review is where the 8.3.6 record earns its keep, and where most records are thinnest. A reviewer writes "no impact to form, fit or function" without showing what they checked against. The auditor's follow-up is predictable: which requirements, which verification results, and did the customer need to know?
Build the review around three questions, each answerable from a link instead of a recollection.
Which requirements does this geometry serve? In Tandem, the design change view lists the affected requirements and annotations alongside the before/after CAD diff, so the reviewer starts from the actual trace and not from memory. Requirements carry a redlined change history, so you can also see how the requirement itself has moved over time.
Does the change invalidate earlier verification? Test cases and validation evidence are linked to requirements in the same system. If a requirement is touched, the test cases and evidence tied to it are visible, and you can decide whether prior results still stand or need to be rerun under 8.3.4. Write that decision down. It is the sentence the clause quietly demands.
Does the customer need notification before implementation? This depends on your defined notification criteria, which are yours to set. The record needs a visible yes or no tied to the affected requirements, with the timing shown. A customer requirement in the affected list is a strong signal to stop and notify before release, not after.
Design reviews matter here too. Tandem's browser-based 3D viewer needs no CAD license, so a manufacturing engineer, supplier or quality reviewer can place annotations directly on the changed geometry, with replies and mentions, and those comments surface inside the designer's CAD tool. The review discussion stays attached to the geometry it is about. For a related view of this problem in another domain, see Design Review Audit Trails for Space Hardware Teams.
Controlling the change: release workflow, authorization and configuration management
Control means the change cannot reach release without passing through the gate you defined, and the authorization is attributable. A signature on a PDF in a shared folder does not show that the approved version is the version that shipped.
Tandem includes PDM with check-in/check-out, soft revisions and a release workflow, live for SolidWorks. The release step is where authorization and the actual files meet: the revision that was reviewed is the revision that gets released. Teams that run a PLM can use Tandem alongside it.
Tandem also generates ECOs, ECNs and engineering documentation from captured CAD changes, in your own templates. That matters for 8.3.6 because the change order is built from what the CAD record shows changed, not from an engineer's after-the-fact description. Your QMS still owns the procedure and the controlled documents. What matters is that the change order and the underlying change agree.
For a closer look at how change orders get driven from CAD edits, see How robotics engineers run ECOs from CAD changes.
Retaining documented information: the change, the review results, the authorization and the reasoning
Retention is where scattered systems cost you the most. The clause lists the change, the review results, the authorization and the actions taken to prevent adverse impacts. In practice an auditor also wants the reasoning, because a decision without a rationale cannot be defended two years later when the engineer has moved on.
A change record that survives audit holds these together:
The change: the before/after diff and its summary, not just a drawing revision letter.
The review results: the affected requirements, the annotations and discussion on the geometry, and the verification decision.
The authorization: who approved, when, and against which revision.
Preventive actions: retests, supplier notifications, or added inspection, linked to the change.
The reasoning: why the change was made and why the alternatives were rejected.
The reasoning is the piece that normally lives in Slack threads and email. Tandem is built as the context layer for hardware engineering, so the design intent, review history and validation evidence stay connected to the change and don't get reconstructed for the audit. Requirements approvals and their redlined history give you the requirement side of the same story. For how this looks in a regulated setting, see Design Verification Traceability in Medical Device Programs, and for the broader idea, What Is a Traceable System of Record for Hardware?
Retention periods and record formats come from your QMS and contract flowdowns. Tandem holds the engineering record. Your quality system decides how long and in what form it is kept.
How Tandem supports the 8.3.6 record alongside your QMS and PLM
Tandem is the context layer for hardware engineering. It connects design intent, requirements, CAD changes, design reviews, PDM and validation evidence in one system so the reasoning behind a change survives reviews, ECOs and handoffs. It supports your 8.3.6 record. It does not replace your QMS, and it does not make an organization AS9100 compliant or certified. Your quality system still owns procedures, audits and certification.
Here is how the clause maps to what Tandem captures.
| 8.3.6 expectation | What the record needs | Where it comes from in Tandem |
|---|---|---|
| Identify the change | What changed and why | Watch sessions; before/after 3D CAD diff with summary |
| Review the change | Affected requirements, verification impact | Affected requirements and annotations on the design change; linked test cases and validation evidence |
| Control the change | Authorized release of the reviewed revision | PDM release workflow; ECO/ECN generation in your templates |
| Retain documented information | Change, review, authorization, reasoning | Requirements redline history, review annotations and linked evidence in one system |
Teams can start with one module, such as requirements or design reviews, or adopt the full suite. Deployments include an integration setup phase with Tandem engineers to connect CAD, PDM or PLM, spreadsheets and telemetry. If you want to see this on your own change, book a demo.
A pre-audit checklist for one change record
Pick one released change and test it against the questions an auditor will ask. If any answer needs a hunt through email, fix the record before the audit does it for you.
Is the change identified? A before/after comparison exists and every difference between baseline and release maps to a change record.
Is the reason written down? The record states why the change was made and what alternatives were considered.
Is the impact review concrete? It names the affected requirements instead of asserting "no impact."
Is the verification decision explicit? It says whether prior verification and validation results still hold, and links to the evidence or the retest.
Is the customer notification decision visible? Yes or no, tied to your notification criteria, with timing showing it happened before implementation.
Does the authorization match the revision? The approver, date and released revision line up.
Did configuration management pick it up? The released state in PDM or PLM matches the authorized change.
Were preventive actions recorded? Retests, supplier notices or added inspections are linked to the change.
Can someone else find it all? A reviewer who did not work on the change can follow it from CAD edit to release without asking anyone.
Make one change record hold the whole story
Clause 8.3.6 is a chain: identify, review, control, retain. A chain breaks at its weakest link, and for most teams that link is the reasoning and impact review living apart from the authorization. Take the one change you would least want sampled, run it through the checklist above, and see how long it takes to assemble the answer. Then book a Tandem demo and walk that same change through capture, impact review and release in one system.
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 does AS9100D clause 8.3.6 require for design and development changes?
It requires you to identify, review and control changes so they do not adversely affect conformity, control changes through configuration management, and retain documented information on the change, review results, authorization and actions to prevent adverse impacts.
Does every AS9100 design change need full verification and validation?
Not automatically. You assess whether the change affects conformity or invalidates earlier verification and validation results, then perform the reviews, verification or validation that assessment calls for under 8.3.4. The record should show that assessment. Tandem links requirements to test cases and validation evidence, so the affected results are visible.
What records should a quality engineer keep for one design change?
Keep the change itself, the impact review results, the authorization, the actions taken to prevent adverse impacts, and the reasoning. Tandem holds the CAD diff, affected requirements, review annotations and linked evidence together, so the engineering side of the record is in one place for your QMS to reference.
Can Tandem make us AS9100 compliant?
No. Tandem does not make an organization AS9100 compliant or certified, and it is not a QMS. It supports the 8.3.6 record by capturing CAD changes, requirements, design reviews, release and validation evidence as the work happens, alongside your QMS and PLM.
How do you catch design changes that were never filed?
Capture changes from the CAD work itself rather than relying on filing. Tandem's Watch records a CAD session and groups feature-tree actions into described design goals, and the before/after 3D CAD diff shows what differs from the last baseline, so unfiled edits surface for review.
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.