Documentation / Validation
Run physical checks on a saved board and rule set, inspect each geometry finding, and prove corrections with the same rerun.
Outcome
Execution record
| Step | Required role | Starting state | Evidence to retain |
|---|---|---|---|
| 01 / Record state and rules | PCB editor authorized to run DRC on the controlled copy | Board setup is reviewed; fabrication constraints, rule ownership, known waivers/exclusions, and unresolved setup issues are available before the run. | Project/board saved-state identity, object and zone counts, rule/net-class transcription, exclusions/ignored families, fabrication sources, role, product context, and timestamp |
| 02 / Run DRC | PCB editor with permission to run DRC | Step 1 freezes the saved board/rule context; the DRC surface is ready and any prior result is identified as prior rather than current. | Run start/end, completion or exact failure state, current-state indication, errors/warnings/category totals, timed-out/skipped checks, full Report/export when available, and board identifier |
| 03 / Inspect in context | PCB reviewer authorized to interpret physical rules and geometry | A complete immutable initial report is tied to Step 1; the finding ledger has one row per reported condition and no correction has begun. | Finding ID/rule/severity/message/location, involved objects/nets/layers, coordinates, Properties values, governing requirement, disposition, rationale, owner, and exception authority |
| 04 / Correct confirmed defects | PCB editor authorized to modify the affected geometry or approved rule | Every target finding has unique object identity, known intended geometry/rule, predicted removed rows, rollback method, and edit approval. | Target IDs, before/after coordinates/dimensions/layers/nets, exact edit or rule delta, source/approval, saved-state identifier, connectivity comparison, and predicted impact |
| 05 / Rerun and reconcile | Independent PCB reviewer or correction owner performing a separate comparison pass | Corrections are saved with exact deltas; initial report and rule/exclusion context remain immutable and predicted changes are recorded. | Initial/final board and run identities, rule/exclusion equality, category counts, row-level reconciliation, timed-out/skipped families, new/residual owners, and final disposition |
Procedure
Record project revision and the active physical constraints.
Resin PCB Editor and DRC/rule surfaces / Projects > exact editable copy > PCB Editor > Project > Document > Save; Board Setup/rule context; DRC: Save the board, inventory object counts and zones, record applicable rule/net-class values and exclusions, and identify any timed-out or intentionally unrun family
The saved board, object scope, rule context, exclusions, and intended fabrication constraints can be reproduced.
Stop ifStop before Run DRC when Save is unresolved, board identity or rules are uncertain, zones may be stale, concurrent edits exist, or exclusion authority is unknown.
Run the complete available check and save the initial finding count.
Resin PCB DRC / PCB Editor > DRC > Run DRC: Select Run DRC, wait until Running design-rule checks is absent, then retain severity/category counts, timed-out/skipped families, and all finding rows
Running design-rule checks is absent and a current DRC Report or explicit All checks passed state is retained with category counts.
Stop ifStop when Run DRC is absent/disabled, no board objects are checkable, the run is cancelled/fails/remains active, results report out of date, or any rule/exclusion changes during the run.
Open each finding at the affected geometry and compare against the intended net and rule.
Resin DRC Report and PCB canvas / DRC Report > each finding row > Severity, Message, Location, IDs > affected PCB geometry: Select each row, inspect all referenced tracks/vias/pads/zones/edges and their properties, then compare with the governing rule and engineering intent
Every finding is tied to exact board geometry and assigned Confirmed defect, Intentional condition, Rule issue, or Needs review with an owner.
Stop ifStop the row when geometry/object identity is stale or ambiguous, rule scope/precedence is unknown, the requirement conflicts with the rule, or classification would be selected only to lower the count.
Edit geometry or constraints only when the engineering requirement is known.
Resin PCB Editor / DRC ledger > one approved Confirmed defect row > exact PCB object Properties/routing/placement control > Save: Apply one source-backed geometry correction or homogeneous approved batch; change a rule only through separate rule-owner approval
Each saved correction is source-backed, linked to exact finding IDs, and has no unexplained connectivity, layer, or unrelated-geometry delta.
Stop ifDo not edit when the target or intent is ambiguous, a fixed/mechanical constraint would be violated, rule ownership is absent, the edit expands beyond scope, or Save/connectivity fails.
Rerun the same checks and account for removed, remaining, and new findings.
Resin PCB DRC and final finding ledger / Saved corrected board > PCB Editor > DRC > Re-run or Run DRC: Run the same complete check and reconcile initial/final rows by ID, rule, object, net, layer, and location; inspect side effects
The same-context final report accounts for every initial row and has no unexplained removed, changed, new, timed-out, or skipped condition.
Stop ifStop closure when the rerun fails/is stale, rules differ, a family times out or is skipped unexpectedly, unrelated rows change, a target disappears without cause, or any final row lacks disposition.
Verification
Evidence and exercise files
CSV / finding-level rows / Published evidence record
Provenance: Finding-level export with run, severity, diagnostic code, rule category, message, and available project-object context.
Current limit: The rows are from compact fixtures and do not include a professional routed-board finding corrected and cleared in Resin.
Download fileJSON / 6 runs / Published evidence record
Provenance: Source-bound checker outputs used by the public finding explorer and summary records.
Current limit: A reported condition is not necessarily one independent root cause, and these runs do not qualify another board's rules.
Download fileEvidence boundary
Failure recovery
Run DRC is unavailable, disabled, cancelled, failed, remains active, or returns stale/incomplete results.
Diagnosis: Record board/saved state, role, object count, PCB Editor > DRC and context-menu availability, exact control/error/stale text, rule/exclusion context, progress, timed-out checks, and timestamps.
Recovery: Confirm the intended board is open and saved and the role permits checks, then make one rerun from the unchanged board/rule state after the prior run is terminal.
Stop or escalate: Escalate when an authorized editor still cannot run DRC, the same engine/run-family fails twice, results remain stale, or retry would obscure which state was checked.
Evidence: Board identity, saved state, role, control captures, rules/exclusions, exact errors/progress, attempt IDs/times, timed-out families, and product-owner issue
Recheck: Run DRC reaches a complete current-state DRC Report or explicit All checks passed result with all run-family states retained; otherwise the board remains not DRC-verified.
A finding appears valid but points to stale/wrong geometry, or an apparent exception lacks clear rule scope.
Diagnosis: Preserve finding ID/rule/severity/message/location, all referenced objects/nets/layers/properties, board/rule saved state, navigation result, and the exact requirement proposed for an exception.
Recovery: Save and rerun once without edits; locate objects independently by reference/net/coordinates, then keep the row Needs review until object identity and rule precedence are established.
Stop or escalate: Escalate when the object no longer exists, identical no-edit runs disagree, rule scope is ambiguous, or exception authority/rationale/review date is unavailable.
Evidence: Original/control reports, object captures and properties, rule/requirement sources, no-edit comparison, exception request, owner, and issue ID
Recheck: The row maps to exact current geometry and one governing rule, or remains Needs review/Blocked; no waiver or edit is credited without that match.
A correction creates new findings, changes connectivity, or removes the target without a defensible causal link.
Diagnosis: Diff before/after object coordinates, dimensions, layers, nets, rules, zones, connectivity, initial/final reports, and every unrelated added/removed/changed finding.
Recovery: Undo or restore the controlled copy to the frozen baseline, run a no-edit control DRC, then reapply only the source-backed correction after predicting its exact geometry and row impact.
Stop or escalate: Block closure when baseline restoration is uncertain, identical control runs differ, connectivity changed unintentionally, or new findings cannot be traced to the bounded edit.
Evidence: State/object/rule diff, initial/control/corrected reports, restore evidence, connectivity comparison, target mapping, new rows, and escalation owner
Recheck: The control run reproduces the baseline or every difference is explained; the approved edit removes only predicted rows, preserves intended connectivity, and introduces no unexplained finding.
Task-specific troubleshooting
Confirm a PCB is open, the board has been saved, and the current role permits the check. Record the active file instead of assuming a result.
Verify the exact rule, rule scope, object layers, and net assignments before considering an exception.
Undo or isolate the edit, then compare the exact geometry and rule deltas before proceeding.
Save the board, rerun the same complete check, and compare the object identity and coordinates before escalating.
Do not use appearance as a substitute for a complete DRC result tied to the saved board and known rules.
Still inspect fabrication outputs and mechanical constraints; zero configured DRC findings does not prove manufacturability or receiver acceptance.
Decision gate
Saved board identity and object counts, fabrication/rule/exclusion context, complete initial/final DRC reports and run-family states, finding ledger, source-backed correction deltas, connectivity review, row-level comparison, residual owners, and signed disposition
A run is stale/incomplete, a family is unexpectedly skipped/timed out, a finding lacks object/rule identity or owner, reruns differ without cause, connectivity changes, or zero configured findings is treated as manufacturability proof.
Next decision
Use the evaluation kit to choose a representative input and define the result your team needs.
ExecuteRun the task in ResinUse an approved project or disposable copy and preserve the actual result separately from this guide.
ContinueReview the board in 3DAdvance only within the scope permitted by the completed decision gate.