A manufacturing panel may reference a separate board document rather than contain an independent frozen copy. That is convenient during design, but it creates a release dependency: changing the source board can change the panel representation. Verify every embedded source before generating panel outputs.
Altium’s panelization documentation explains that an embedded board array references a PCB design file. The referenced file therefore belongs in the panel’s release definition.
Trace references beyond the visible panel
List each embedded array or board instance, the resolved source path, the intended board revision, and its orientation. If the panel combines different boards, record each source separately. A panel filename cannot communicate all of those identities reliably. Also identify whether alternate source variants share the same outline but differ in copper or assembly content, since visual panel previews may not reveal that distinction.
Open the referenced board and confirm its release state. Check for a similarly named development copy in another directory. The file that the panel actually resolves matters more than the path a designer remembers selecting earlier.
Review changes at panel scale
After updating a source, regenerate or refresh the panel representation using the software’s supported workflow. Compare features near the board edges, rail interfaces, tooling locations, and separation features. A small outline or copper change can affect panel-level relationships without changing the array count.
| Source change | Panel consequence to inspect |
|---|---|
| Board outline | Spacing and separation geometry |
| Edge component | Rail and neighboring-board clearance |
| Fiducial or tooling feature | Panel alignment and manufacturing documentation |
| Layer or stack revision | Consistency of the combined fabrication package |
Check the generated manufacturing set
Inspect exported copper, mask, profile, and drilling data as a panel. Confirm that the repeated board features correspond to the intended source revision. Use a deliberately identifiable changed feature when validating the update process; an unchanged region cannot prove freshness.
Compare panel drawings and quantity information with the exported geometry. A drawing regenerated from one source state and fabrication files from another create an ambiguous package even if each file opens normally.
Archive the panel document together with its referenced board sources and release manifest. If the workflow intentionally freezes or packages references, verify the resulting package on a separate location where development paths are unavailable.
When the source board changes after panel approval, treat the panel as affected until reviewed. The release evidence should show which board revision was repeated, how the panel was refreshed, and that the final outputs represent the reviewed combination of board and panel features.
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