Gerber Job carries machine-readable thickness, material, finish, and other manufacturing information with Gerber data. It supplements graphics without automatically resolving contradictions elsewhere. If Job states 1.6 mm and the drawing 1.2 mm, confirm approved requirements and revision sources, then reexport the whole package; receivers must not choose whichever value seems reasonable.
Value and boundary of Job file
Ucamco notes that manufacturing information often travels in drawings/text and that Job standardizes its transfer. Partial implementations are permitted, so generating a Job file does not establish complete fields or receiver use. Check current exporter support and actual output.
Job attributes do not replace precise geometry, drilling, BOM, pick-and-place files, or test specifications. Fabrication and assembly files address different objects. A material name does not identify missing PP construction, hole treatment, or assembly requirements; supplement gaps explicitly in same-revision controlled files.
Perform bidirectional verification between fields and files first
| Reference Object | Inspection Method | Frequently Asked Questions |
|---|---|---|
| Document List | Whether referenced files exist and every packaged file has a defined function | References become invalid after renaming, keep old layers |
| Layer structure | Layer count/order against stackup and copper attributes | Inner layer sequence misalignment and side reversal |
| Board Thickness Material | Check item by item against manufacturing drawing and approved stackup | Job retaining old settings while drawings change separately |
| Surface and Special Requirements | Verify processing type and zone description | Default values override actual special requirements |
Trace Job references to actual files and every packaged file back to the list. Finding all references does not catch extra obsolete files that automatic import may treat as current layers.
Configuration handling example for board thickness conflicts
Engineering example: manufacturing drawing R3 specifies 1.20 mm finished thickness, and stackup R3 budgets total 1.20 mm, while Job remains R2 at 1.60 mm. Difference is 0.40 mm, approximately 33.3% relative to 1.20 mm. This only highlights conflict magnitude; it does not determine document precedence.
- Record conflicting fields, values, and revisions without overwriting production-system settings directly.
- Check approvals/change records to determine whether R3 is current or an unapproved draft.
- Obtain the owner's written conclusion and revise controlled sources/export settings.
- Reexport Job, graphics, and manufacturing files, checking mutual consistency.
- Generate a new package/checksum, explicitly supersede the old package, and confirm receipt.
If drawing R3 itself conflicts with the structural budget, changing Job to 1.20 mm does not close the issue. Resolve engineering definitions before their representations to avoid formally consistent but structurally wrong files.
Checks must go beyond valid JSON syntax
Machine-readable files must parse in corresponding tools and meet the adopted format version. Syntax/schema acceptance does not establish truth: layers may be wrong, filenames obsolete, and materials defaulted. Record parseability, structural validity, cross-file consistency, and engineering approval as separate results.
Do not invent keys or units to fill gaps. Use the corresponding specification/tools for manual edits and recheck afterward. This article's comparison table is a work method, not copy-ready Job syntax; actual adopted format versions govern fields.
| Verification Level | What It Proves | What It Cannot Prove |
|---|---|---|
| Parsing Success | File Readability | Field meaning and value correctness |
| Structural Inspection | Comply with constraints supported by the tool | All optional requirements are expressed |
| Cross-Check | Consistency Between Documents | Design requirements are already correctly approved |
| Engineering Approval | Basis for entering current combination into manufacturing | Finished Goods Inspection Completed |
Who confirms the field approval value
Design and manufacturing review jointly confirm thickness/structure; purchasing aligns orders to approved packages; document control manages revisions/distribution. Assign conflict owners and conclusions instead of saying “use latest” in email. Several attachments can share a date, so dates do not replace revision identity.
For proposed copper-weight, width, or dielectric-thickness changes, assess functional impact. Define allowable adjustments in controlled notes and update corresponding files. A field easier to import cannot automatically outrank other approved documents.
How to reissue full package to avoid old reference residue
Regenerate from approved sources, package in a new directory, and check file count/functions before sending. For a six-layer example, identify six copper layers plus applicable mask, legend, drilling, and outline files. Actual counts vary with structure/format; fixed counts do not establish completeness. Archive package revision, contents, and checksum together.
Checksums establish identical sent/received content, not correct thickness. Receivers should acknowledge package identity and closed clarifications. If old packages remain for traceability, mark them prohibited for current production instead of naming both “final.”
Common reasons for errors even after automatic import
Possible causes include partial exporter support, unused production-system fields, or manual overrides. Retain original files, import logs, and final settings for itemized comparison rather than declaring the format invalid. Same-revision drawings can supplement unexpressed special processing, provided instructions agree and are executable.
At first cooperation or software upgrades, regress a known package for layer order, units, and key attributes. Target changed interfaces; copying every historical file is unnecessary to establish tool operation.
How to determine which attributes software actually uses
When establishing delivery, use a known package to check fields supported by exporter, viewer, and production system. Ask receivers which are read automatically, require manual entry, or face default overrides. Tools support partial implementations differently; rely on actual observations.
Supplement unsupported fields with same-revision drawings/lists and verify consistency. Unread fields remain engineering requirements; fields present in a file do not establish shop-floor execution. Follow transfer through to parameters actually used.
After software/export changes, review layer order, units, and key attributes. If imports differ, retain old/new files, settings, and logs to distinguish syntax support, omitted fields, and changed settings. Correct the actual break instead of blaming every issue on format selection.
Give each check layer a clear state, such as parsed, cross-checked, or pending manual input, so one “pass” does not hide unprocessed fields. Production approval references complete requirements, not a green software icon. This makes partial implementations useful while exposing gaps.
Frequently Asked Questions
Does Job naturally take priority over PDF?
The format does not determine approval precedence; resolve conflicts against controlled requirements.
Is an incomplete Gerber Job file still useful?
Yes, with explicit supported and missing scope. Continue to Freeze entire data package, Manufacturing Combination and Delivery List.
Source material and applicable scope
- Ucamco, “Gerber Job — Official Gerber Format Website”; official introduction webpage, not the complete syntax specification; checked on 2026-10-17; relevant sections: manufacturing-characteristic transfer, compatibility, Partial Implementations. Supports Job purpose and partial-implementation boundaries. Conflict handling, numerical examples, and responsibilities are engineering guidance.
