An output folder may contain a mixture of newly generated files and older files that the current export no longer produces. Compressing the entire folder can then send contradictory data to the manufacturer. Verify the complete release set rather than assuming that a successful generation message describes every file present.
Altium’s Output Job documentation explains configured outputs and output containers. Review which outputs are enabled and connected to each container. A configured generator that was not run does not produce current evidence simply because an older file has the expected name.
Define the expected release contents
List the required fabrication, assembly, inspection, and documentation outputs for the release. Identify the source project revision, board revision, and variant. Give each output a defined purpose and an expected format so missing or unexpected files are visible.
Generate into a new controlled release directory or another workflow that reliably distinguishes current output from prior runs. Preserve older releases separately. Do not rely only on modification timestamps, which can change during copying and do not explain the source configuration.
Reconcile files after generation
| Observation | Action |
|---|---|
| Expected file missing | Review generator settings and execution results |
| Unexpected layer or report present | Determine whether it is stale or intentionally required |
| Two files describe the same deliverable | Resolve the authoritative version before handoff |
| Output refers to another variant | Regenerate from the correct configuration |
Check the generation log and open representative outputs independently. For fabrication data, inspect layer identity, outline, and drill relationships. For assembly data, verify population and references against the chosen variant.
Control partial regeneration
- Record which design change triggered the new output.
- Identify every deliverable potentially affected.
- Regenerate the necessary set from one controlled source.
- Compare the new package with the previous release.
- Retain a manifest identifying the delivered files.
A changed reference designator can affect several assembly documents even when copper is unchanged. A changed stackup can affect drawings and impedance requirements even when the file count remains the same. Base regeneration scope on dependencies, not only on which editor was last used.
Close the release by reviewing the exact archive intended for delivery. Extract it into a separate location and confirm that its contents match the approved manifest. Check that renamed files still identify their layer or purpose correctly after any packaging script has processed them. The project archive guide addresses reproducibility of the design sources; this output review verifies the manufacturing package actually sent.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist