Documentation / Projects

Review an existing project

Inspect a project without changing its source: schematic, components, outputs, changes, and history.

Level: Beginner
Estimated: 15 min
Instructions updated: 2026-07-13
Product context: Web app / instructions reviewed July 13, 2026

Start task All documentation

Outcome

Build a trustworthy picture of an unfamiliar project while keeping the source unchanged.

Before you start

A Resin account
Viewer or editor access to a populated project
A disposable copy before trying any operation that changes design data, generates outputs, saves snapshots, or restores history

Task record

Time: 15 minutes
Level: Beginner
Instructions updated: 2026-07-13
Product context: Web app / instructions reviewed July 13, 2026

Execution record

Prepare the role, starting state, and evidence record before acting.

Keep these records beside the project state so the task steps can stay focused on the action, passing result, and stop condition.

Step	Required role	Starting state	Evidence to retain
01 / Open the project workspace	Project reviewer with read access to the approved organization and named project	The approved organization, project name, expected version or revision, review scope, reviewer identity, and access role are recorded; no project card has been opened for this attempt.	Attempt ID, organization, active filters, project card name and version, opened workspace heading and tab, access role, opening timestamp, and statement that no edit control was used
02 / Inspect the schematic	Electrical reviewer able to interpret the scoped schematic and distinguish observation from design approval	Step 1 passed; the exact project and version, expected sheets or review scope, target references or nets, and a neutral editor state are recorded.	Project, version, schematic and sheet identities, complete visible sheet inventory, target references and nets, readable canvas capture, exact warning count and text when available, zoom context, and no-mutation statement
03 / Review the component data	Component or BOM reviewer familiar with the project's required fields and source-of-truth rules	Steps 1 and 2 passed; the schematic reference inventory, in-scope component fields, expected grouping behavior, and any approved source comparison are frozen.	Project and version, displayed BOM total, visible-row or group count, active filter and grouping state, in-scope references, values, packages, symbol associations, blank Parity/Verified/Supplier/price fields when shown, exceptions, and capture timestamp
04 / Check output configuration	Release or manufacturing-output reviewer who knows the in-scope receiver requirements	Steps 1-3 passed; the exact project and version, required output families, receiver or review scope, and a prohibition on generation for this read-only attempt are recorded.	Project and version, each in-scope card and category, available or disabled state, exact dependency text, visible settings, required-versus-observed comparison, timestamp, and explicit separation from any generated-file evidence
05 / Inspect changes and history	Configuration reviewer authorized to view project records but not alter the reviewed source	Steps 1-4 passed; the exact project and version, expected working-state owner, read-only review boundary, and prohibition on snapshot or restore actions are recorded.	Project and version, Changes status and complete visible row inventory, History entry identifiers and timestamps shown, separate tab captures, refresh record when used, unexplained differences, and no-action statement

Procedure

Run the documented task in order.

Record an unavailable action or failed assertion; do not infer that the operation ran.

01
Open the project workspace
Action
Sign in to Resin and open Projects. Select the project you intend to review and confirm its name before navigating into design data.
Resin Projects dashboard and project workspace / Projects > search and status filters > exact project card > opened project workspace: Clear or record active filters, compare the card name and version with the approved target, then open that card once without using New Project or Import Project
Pass when
The approved project name and version agree with both the selected project card and the opened workspace, and no engineering data has been edited.
Stop if
Stop when the organization or project identity is ambiguous, duplicate names cannot be distinguished, access is missing, the workspace fails to load, the opened version differs, or an unsaved or edit state cannot be explained.
02
Inspect the schematic
Action
Choose Schematics from the project tabs. Inventory the available sheets, select each in-scope populated sheet, and fit the circuit to a readable view. Review the component references, values, wires, labels, and connections relevant to the task.
Resin schematic editor / Opened project > Schematics > schematic tab > sheet selector > canvas: Use the sheet selector plus fit, zoom, and neutral selection controls; inspect symbols, labels, wires, warnings, and hierarchy without activating placement, wiring, property-edit, or save controls
Pass when
Every visible in-scope sheet is inventoried, the scoped references, values, and nets are readable on the expected sheet, visible warnings are recorded separately, and no object has moved or changed.
Stop if
Stop when project or sheet identity changes, an expected sheet is absent or never loads, the target cannot be read reproducibly, an edit tool remains active, an object moves, or a warning cannot be tied to the captured state.
03
Review the component data
Action
Open Components. Expand Bill of Materials to review grouped component records, then open Symbol Library when the task requires inspection of project symbols attached to the design.
Resin Components workspace / Opened project > Components > Bill of Materials and, when in scope, Symbol Library: Record or clear the component filter, expand grouped records, compare displayed totals with visible rows, and inspect fields and symbol associations without editing or substituting library data
Pass when
The displayed BOM total reconciles with the visible rows and recorded filter or grouping state, every in-scope reference has a disposition for value, package, and required associations, and blank verification or sourcing fields remain explicit findings rather than approvals.
Stop if
Stop the component assertion when totals cannot be reconciled after recording filters and groups, required references are absent or duplicated, the workspace belongs to another project state, a required association cannot be inspected, or resolution would require editing data.
04
Check output configuration
Action
Open Project, then Output & Export. Review the Fabrication, Assembly, Documentation, and Export Settings areas. An available control is not proof that a valid file has been generated for this project.
Resin Output & Export workspace / Opened project > Project > Output & Export > Fabrication, Assembly, Documentation, and Export Settings: Inspect each output card, availability state, dependency message, and relevant visible setting without selecting Generate, Download, or another state-changing control
Pass when
Every in-scope output control has a recorded available, disabled, configured, or not-observed disposition; PCB-dependent requirements are preserved; and no output is marked generated or valid without a separately identified file and inspection record.
Stop if
Stop when the project identity changes, a required area does not load, availability or dependency text is ambiguous, inspection requires generation or configuration changes, or a prior file cannot be tied to this exact project state.
05
Inspect changes and history
Action
From Project, open Version Control. Review Changes for the current working state and History for recorded project states. Do not save, restore, or modify history when reviewing a production project.
Resin Version Control workspace / Opened project > Project > Version Control > Changes, then History: Open Changes and History once each, record their visible rows and status, and refresh once only when a loading state is unclear; do not save a snapshot, commit, discard, or restore
Pass when
Changes and History are inspected independently, visible working changes and history entries are recorded against the same project version, any discrepancy remains open, and snapshot, save, commit, and restore controls remain unused.
Stop if
Stop when either tab belongs to an uncertain project state, loading remains inconsistent after one refresh, visible changes lack an owner, history identity cannot be recorded, a confirmation or restore flow opens, or the two tabs cannot be compared without mutation.

Verification

Do not call the task complete until these checks pass.

Exact project and version confirmed
All visible in-scope sheets and key nets recorded
BOM total, filters, groups, and component gaps reconciled
Every in-scope output control dispositioned without a generation claim
Changes and History inspected independently
No source, output, snapshot, or history mutation performed

Evidence boundary

Keep preparation separate from product proof.

The procedure defines what to run and retain; it does not claim that the task ran successfully on any project.

This guide can establish only what the authorized reviewer observed in the five named Resin surfaces for one recorded project, version, role, product context, and attempt time. The captures on this page are dated interface examples, not evidence that a reader executed the steps. A visible schematic or saved state does not prove electrical correctness, completeness, connectivity, or warning resolution; a BOM view does not prove sourcing or verification; output controls do not prove generation or file validity; and visible Changes or History does not prove repository integrity, recoverability, or production readiness. Preserve unobserved and unsupported claims as unknown.

Failure recovery

Diagnose and recover without hiding the original state.

Preserve the symptom before changing anything, apply one bounded recovery, and repeat the affected assertion against the named project state.

DOC-REV-F01

The approved project is absent, inaccessible, duplicated by name, or opens with a different organization, version, or file tree.

Diagnosis: Record the approved organization, project name and identifier when available, expected version, active search and status filters, account role, complete matching card list, opened heading and tree, timestamps, and exact access or loading message.

Recovery: Close the mismatched workspace without saving, clear and record filters, confirm access with the project owner, and reopen only the uniquely identified approved card under the same attempt or a newly named attempt when identity changed.

Stop or escalate: Escalate when identity remains ambiguous, access cannot be authorized, the expected version cannot be reconstructed, a partial or duplicate project has no owner, or any recovery would create or edit project data.

Evidence: Approval record, card-list and filter captures, role and organization, mismatched workspace capture, exact messages, owner response, attempt IDs, and final selected identity or blocked disposition

Recheck: Repeat step 1 from Projects and require the approved name and version to agree on the unique card and opened workspace before any other surface is reviewed.

DOC-REV-F02

A schematic sheet, target object, BOM record, association, or displayed component total is empty, unreadable, missing, duplicated, or inconsistent with the recorded scope.

Diagnosis: Record project/version, surface and path, sheet selector or component filter/group state, loading state, zoom, exact target references or nets, displayed total, visible rows or groups, missing associations, warning text, and whether any edit tool activated.

Recovery: Keep the project unchanged, return to a neutral selection state, reopen the expected sheet or clear and record the BOM filter, use fit/zoom or group expansion once, and start a new attempt if project state or scope changed.

Stop or escalate: Escalate when expected data remains absent, counts cannot reconcile, the target is ambiguous, a required association cannot be inspected, an accidental mutation may have occurred, or diagnosis would require editing or substituting data.

Evidence: Before and after captures, sheet/filter/group inventories, counts, target list, warnings, exact missing or duplicate rows, accidental-action record, attempt identity, and issue owner

Recheck: Repeat the affected step's full assertion against the same approved project version and compare all unrelated recorded landmarks with the frozen starting state.

DOC-REV-F03

Output availability, Changes, or History is unavailable or ambiguous, the two version-control tabs disagree, or the interface invites generation, snapshot, commit, discard, or restore to continue.

Diagnosis: Record project/version, exact card or tab, availability and dependency text, loading status, visible settings or rows, Changes inventory, History identifiers, prior generated-file identity if asserted, confirmation text, and one-refresh result when used.

Recovery: Do not activate the offered mutation. Close any confirmation, preserve the current evidence, reload the read-only surface once when safe, and ask the release or project owner to explain requirements or state outside this review attempt.

Stop or escalate: Escalate when a required surface remains unavailable, state differs after refresh, working changes lack an owner, output proof cannot be tied to this version, a confirmation cannot be closed safely, or validation requires generation or history mutation.

Evidence: Output-card and version-control captures, exact messages, settings and row inventories, refresh record, prior artifact identity, closed-confirmation evidence, owner response, issue ID, and blocked disposition

Recheck: Reopen the affected surface from the exact project, repeat its assertion without mutation, and confirm the project/version plus previously stable schematic and BOM landmarks still match the starting record.

Task-specific troubleshooting

Resolve these states without changing the evidence boundary.

The project is not listed

Clear the project search and check the Active, Review, and Archived filters. If it is still absent, confirm that your account has access; do not create a replacement project as part of this review.

The schematic appears empty

Check the sheet selector and open the populated sheet, then use the editor's fit or zoom controls. An empty sheet is not evidence that the project has no schematic data.

BOM totals do not match visible rows

Clear the component filter and collapse or expand grouped records. Record both the displayed total and the active filter before treating the mismatch as a data issue.

Output options are disabled

Read the requirement shown on the disabled card. PCB-dependent outputs remain unavailable when the project has no PCB; do not report those files as missing generated outputs.

Changes and History seem inconsistent

Review each tab separately: Changes describes the working state, while History lists recorded commits or snapshots. Refresh once before escalating, and do not save or restore a snapshot during review.

A capture is hard to read

Activate the capture to open the expanded view. Use browser zoom if needed, close with Escape, and rely on the current product UI when it differs from this dated example.

Decision gate

Decide whether the read-only project review is acceptable

Do all five step assertions pass for one exact project and version, with retained evidence, explicit unknowns, owned exceptions, and no source, output, snapshot, or history mutation?

Required evidence

Attempt and reviewer identity, organization and access role, exact project and version, all five starting-state and surface records, sheet and target inventory, warning record, reconciled BOM total/filter/group state, output-control dispositions, separate Changes and History observations, captures or equivalent locators, exception owners, and no-mutation statement

Remain blocked when

Any step assertion failed or was not observed, project/version changed, BOM totals remain unreconciled, an output file is claimed from controls alone, Changes or History is ambiguous, evidence comes only from this page's example captures, an exception lacks an owner, or any mutation occurred or cannot be ruled out.

Next task after this gate passes: Inspect the reference project

Next decision

Carry this result into an owned engineering decision.

Choose the next route only after the task record names the project state, observed assertions, exceptions, evidence custodian, and decision owner.

EvaluateTest this task with your own project

Use the evaluation kit to choose a representative input and define the result your team needs.

ExecuteRun the task in Resin

Use an approved project or disposable copy and preserve the actual result separately from this guide.

ContinueInspect the reference project

Advance only within the scope permitted by the completed decision gate.