Documentation / Validation
Run electrical checks on a named saved state, classify every finding, correct confirmed issues, and prove the change with an identical rerun.
Outcome
Execution record
| Step | Required role | Starting state | Evidence to retain |
|---|---|---|---|
| 01 / Record the baseline | Schematic editor authorized to run checks on the controlled copy | The project copy, schematic scope, expected rule policy, known waivers, and owner of unresolved findings are recorded before any run. | Project/revision or saved-state identity, sheet inventory, saved indicator, rule context, waiver baseline, role, product context, and run timestamp |
| 02 / Run ERC | Schematic editor with permission to run ERC | Step 1 identifies a saved state and frozen rule/waiver context; the ERC dock contains no result being mistaken for the new run. | Run start/end, exact completed/failure state, category counts, complete finding rows or Export Report CSV when enabled, and checked-state identifier |
| 03 / Classify findings | Electrical reviewer authorized to interpret the governing rule and design intent | A completed run and immutable row export or transcription are tied to Step 1; the finding ledger has one blank disposition row per result. | Finding ID/rule/severity/message, sheet, reference/net/pin, navigation result, disposition, rationale, source, owner, and waiver authority when relevant |
| 04 / Correct one class | Schematic editor authorized to correct the selected objects | Every target row is a confirmed defect with unique object identity, intended state, authoritative basis, edit owner, and predicted affected findings. | Target finding IDs, before/after object values or connectivity, edit list, saved-state identifier, expected removed findings, and unrelated-object comparison |
| 05 / Rerun and compare | Independent electrical reviewer or correction owner with separate comparison pass | The correction is saved, its exact delta and predicted result are frozen, and initial ERC rows/counts remain available for comparison. | Initial/final run identities, category counts, row-level comparison, removed-target mapping, new/changed rows, rule/waiver equality, residual owners, and final disposition |
Procedure
Save the project state and record the active revision before running checks.
Resin schematic editor and ERC rule context / Projects > exact editable copy > Schematics > in-scope sheet(s) > Save; ERC surface and current rule settings: Save the intended schematic state, inventory in-scope sheets, and transcribe the active ERC configuration before Run ERC
The exact checked state can be identified later.
Stop ifStop before Run ERC when Save is unresolved, project or sheet scope is ambiguous, rules differ from the approved policy, concurrent edits are present, or waiver authority is unknown.
Run the available electrical check without changing rule settings mid-run.
Resin ERC / Schematics > empty canvas context menu > Run ERC > ERC dock: Select Run ERC, wait until Running ERC is absent, then record errors, warnings, info, waived counts, and any last-run failure state
A complete result and finding count are visible.
Stop ifStop when Run ERC is absent/disabled, the run fails or remains active, results are stale, a rule or waiver changes, or no completed-current-state indication can be retained.
Group findings into confirmed defects, intentional conditions, library issues, and needs-review items.
Resin ERC dock and project schematic / ERC dock > each finding row > selected sheet/object; approved finding ledger outside Resin: Open each row in context and assign Confirmed defect, Intentional condition, Library issue, or Needs review without changing the design
Every finding has one disposition and an owner where needed.
Stop ifStop the row when it cannot be tied to one object/context, the governing requirement is unknown, severity or message changes, or classification would be chosen only to reduce the open count.
Fix confirmed design issues in a controlled batch.
Resin schematic editor / ERC ledger > one approved Confirmed defect row > exact schematic object > bounded edit > Save: Apply one source-backed correction or one homogeneous owner-approved batch, record the exact delta, and save without changing ERC rules
Each edit can be tied to a specific finding.
Stop ifDo not edit when the target is ambiguous, intended state lacks a source, another user is editing the object, the change expands beyond the approved batch, or Save fails.
Run ERC again and compare counts and remaining identifiers.
Resin ERC dock and finding ledger / Saved corrected schematic > ERC dock > Re-run or empty canvas context menu > Run ERC: Run ERC with the same rule and waiver context, then reconcile removed, unchanged, changed, and new rows by stable identifiers and object context
Resolved findings are absent and no unexplained new findings appear.
Stop ifStop closure when the rerun fails, rule/waiver context differs, unrelated findings change without cause, a target disappears without causal evidence, or any final row is unowned or undispositioned.
Verification
Evidence and exercise files
JSON / 6 runs / 241 findings / Published evidence record
Provenance: Machine-readable output from four compact-fixture DRC runs and two schematic ERC runs, tied to exact source records.
Current limit: The file proves the published run outputs. It does not include a schematic finding corrected in Resin and cleared by a retained rerun.
Download fileCSV / 6 runs / Published evidence record
Provenance: Flat summary of source identity, check type, severity totals, and run disposition for the published cases.
Current limit: Aggregate totals do not identify root cause or establish rule coverage for another project.
Download fileEvidence boundary
Failure recovery
Run ERC is absent, disabled, fails, remains active, or cannot be tied to the current saved state.
Diagnosis: Inspect the schematic empty-area context menu and ERC dock; record project/sheet, saved state, role, rule context, exact control state, backend/failure text, timestamps, and any stale-results message.
Recovery: Confirm the intended schematic is open and saved and the tested role permits checks, then make one rerun from the unchanged state after the prior request is terminal.
Stop or escalate: Escalate when an authorized editor still cannot run ERC, the same backend state fails twice, results remain stale, or retry could conceal which state was checked.
Evidence: Project/sheet identity, saved state, role, rule context, control captures, exact errors, attempt IDs/times, and product-owner issue
Recheck: Run ERC reaches a completed current-state result with retained counts/rows; otherwise the schematic remains explicitly not ERC-verified.
A finding navigates to the wrong object or cannot be reconciled with one sheet, reference, net, or pin.
Diagnosis: Preserve ID, rule, severity, message, displayed sheet/object/coordinates, selected-row behavior, current hierarchy path, and Find results for the cited identifiers.
Recovery: Return to the recorded run and project state, locate candidates through exact identifiers, and classify the row Needs review without editing until one object-level cause is established.
Stop or escalate: Escalate when identifiers are stale or ambiguous, the project tree lacks the cited sheet/object, or the finding changes across identical no-edit reruns.
Evidence: Original row/export, navigation capture, candidate comparison, project/sheet inventory, no-edit rerun result, owner, and issue ID
Recheck: The retained finding maps to one exact object and governing rule, or remains Needs review with no correction credited.
A target finding disappears after an unrelated edit, or identical reruns add/remove unrelated rows.
Diagnosis: Diff the saved project states, rule and waiver contexts, initial/final exports, target IDs, all unrelated row changes, live-ERC state, and run completion status.
Recovery: Undo or restore the controlled copy to the retained baseline, confirm the rule/waiver context, run a no-edit control ERC, then reapply only the approved correction.
Stop or escalate: Block closure when the baseline cannot be restored, identical runs remain nondeterministic, or the target disappears without a defensible object-level cause.
Evidence: State diff, initial/control/corrected run records, rule/waiver comparison, undo/restore evidence, target mapping, unrelated rows, and escalation owner
Recheck: The control run reproduces the baseline or every difference is explained; the approved correction removes only predicted rows and creates no unexplained new finding.
Task-specific troubleshooting
Confirm a schematic is open and the project is editable. Record the role and active sheet instead of assuming the check ran.
Stop and record the saved project state, active rule configuration, finding counts, and exact sequence for both runs.
Capture the finding text, reference or net, active sheet, and visible object context before escalating.
Undo the edit, return to the recorded baseline, and rerun ERC before classifying the warning as resolved.
Require a reason, owner, exact finding scope, and review date outside the tool if those controls are unavailable.
Still reconcile the checked revision and rule set; zero configured ERC findings is not proof of ratings, function, or compliance.
Decision gate
Saved project/sheet identity, frozen rule and waiver context, completed initial and final ERC rows/counts, finding ledger, source-backed correction delta, row-level comparison, residual owners, and reviewer disposition
A run is incomplete/stale, a finding lacks one object or owner, rules changed, reruns differ without cause, a waiver lacks authority, or zero findings is being treated as proof beyond configured ERC coverage.
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.
ContinueSynchronize schematic and PCBAdvance only within the scope permitted by the completed decision gate.