Documentation / Projects
Start a blank Resin project or carry an Altium or KiCad design through Upload, Preview, Options, and Review.
Outcome
Execution record
| Step | Required role | Starting state | Evidence to retain |
|---|---|---|---|
| 01 / Open Projects and choose a path | Project creator authorized for the intended organization | Projects is open; the organization, unique proposed name, blank-versus-import branch, cleanup owner, and disposable status are recorded. | Organization, proposed name, exact-match search result, selected branch, role, timestamp, and Projects capture before creation |
| 02 / Create a blank project | Project creator with permission in the recorded organization | The blank branch is approved, exact-name search returned zero matches, and the approved name is available verbatim. | Pre-submit name, destination, submit timestamp, opened project heading, and post-create Projects search count |
| 03 / Upload an import copy | Import operator authorized to use the source files | The unchanged disposable source copy, format/version, file manifest, counts, and intended destination are frozen before upload. | Source manifest and checksum or immutable identifier, upload mode, detected-file table, format overrides with reasons, and wizard timestamp |
| 04 / Review parsed documents | Electrical or PCB reviewer who can compare the source baseline | Upload reconciliation passed and the source baseline contains expected sheets, counts, dimensions, layers, vias, traces, and board identities. | Preview summary, source-versus-preview comparison, Primary board choice, skipped-board list, warnings, and exact parser messages |
| 05 / Set import options deliberately | Import operator working from an approved mapping plan | Preview is dispositioned; the target stackup, datum, units, hierarchy policy, and permitted transformations are written down. | Complete options table, layer-by-layer map, units and origin, all flag states, mapping source, reviewer, and pre-create capture |
| 06 / Review before creation | Import operator with reviewer-approved settings | Upload, preview, and options records are complete; every warning has a proposed post-import check. | Final review summary, warning count and exact text, approved comparison, create decision, operator, and timestamp |
| 07 / Reopen and verify persistence | Project creator or import operator with access to the destination | Creation reports completion; no repair or second create attempt has been made, and the expected tree is listed in the run record. | Creation result, Projects exact-match count, reopened project heading, visible file tree, missing/unexpected entry list, and reopen timestamp |
| 08 / Record the starting state | Independent project or migration reviewer | Steps 1-7 have observations and evidence references; no import-fidelity or production-readiness claim has been entered. | Signed record linked to source identity, destination project, product context, every step artifact, exception owner, and next verification plan |
Procedure
Open the Projects panel. Use New Project for a blank design, or Import Project for an existing Altium or KiCad design. Do not create a blank project first when you intend to use Import Project; the wizard creates its own destination project.
Resin Projects panel / Projects: Choose New Project or Import Project once; do not activate either control until the destination and name are fixed
Exactly one path is selected and the intended project name is written down before any files are created.
Stop ifStop before either control when the destination is uncertain, create permission is absent, an exact or confusingly similar name exists, or cleanup ownership is blank.
For a new design, choose New Project, enter the project name in Project name..., and press Enter or activate the check control. Skip to the final persistence step after the project opens.
Resin blank-project creation / Projects > New Project > Project name...: Enter the approved name and submit once with Enter or the check control
The named project appears once in Projects and opens without an imported-file tree.
Stop ifStop after one submission when an error appears, a different name or organization opens, no result is shown, or Projects lists other than one exact match.
For an existing design, choose Import Project. In Upload, add the complete Altium folder in folder mode or the required KiCad files in file mode. Confirm every Detected file row and override only a genuinely incorrect format classification.
Resin Import Project wizard / Projects > Import Project > Upload: Add folder for the complete Altium copy or add the required KiCad files; inspect every Detected file row
The detected-file count matches the prepared source set and no required source file is silently absent.
Stop ifStop before Parse and continue when a required file is absent, an unexpected file appears, classification is unresolved, the source changed after inventory, or upload reports an error.
Choose Parse and continue, then use Preview documents to compare schematic count, sheet names, component and net counts, board dimensions, layers, vias, and traces with the recorded source baseline. If more than one board is present, select the intended Primary board and record every board marked Will be skipped.
Resin Import Project preview / Import Project > Parse and continue > Preview documents: Inspect parsed schematic and board summaries; select one Primary board when multiple boards are listed
The preview agrees with the baseline or every mismatch and skipped board is written into the import record.
Stop ifStop in Preview documents when parsing fails, the intended board is absent, a critical count or dimension differs without disposition, or any required board would be silently skipped.
In Import options, set Project name and Destination, review every Layer mapping row, and choose Units and origin. Leave Flatten hierarchical sheets off when hierarchy must be preserved. Enable Regenerate symbols, Import 3D models, or Snap stray elements to grid only when that transformation is part of the pilot plan.
Resin Import Project options / Import Project > Import options: Set Project name, Destination, every Layer mapping row, Units, origin, and each displayed behavior flag
The destination, layer map, units, origin, and each behavior flag have an explicit recorded value.
Stop ifStop when a destination layer or datum is ambiguous, a required hierarchy cannot be preserved, a transformation lacks approval, or the UI cannot represent a release-critical mapping.
In Review and create project, reconcile Source format, Schematics, Board, Layers mapped, and the non-blocking warning count. Choose Back if any value differs from the approved import record; otherwise choose Create project.
Resin Import Project final review / Import Project > Review and create project: Compare the summary with the approved import record; use Back for a difference or Create project once for an exact match
The review summary matches the approved settings, and every non-blocking warning is copied into the post-import checklist.
Stop ifDo not select Create project when any summary value differs, a warning is unrecorded, source identity changed, or the destination name is no longer unique.
After the project opens, return to Projects, reopen the same project, and inspect the project tree. For imports, confirm the expected schematic and PCB entries and retain the original source files under Imported where shown.
Resin Projects and created project tree / Created project > Projects > exact project name > project tree: Return to Projects, search the exact name, reopen the single result, and inspect Schematics, PCB, and Imported entries that are shown
The same project reopens, the expected design files remain available, and no second project with a similar name was created.
Stop ifStop without recreating content when the project is absent or duplicated, identity differs, expected files are missing, save state is uncertain, or reopen reports an error.
Record the project name, creation path, source-file manifest or blank-project state, warning list, and the date. Do not call an import faithful until schematic, board, library, connectivity, and output checks are completed.
Approved engineering run record / Outside Resin > project creation or import record for the named destination: Enter identifiers, branch, manifests, settings, warnings, observed tree, exceptions, owners, and a bounded disposition
Another engineer can reproduce the starting state and distinguish a completed import operation from verified design fidelity.
Stop ifStop publication when an identifier, warning, branch decision, observed result, or owner is missing, or when import completion is presented as schematic, PCB, library, connectivity, or output fidelity.
Verification
Evidence and exercise files
ZIP / 7 source files / GPL-2.0-only, GPL-3.0-only, and MPL-2.0
Provenance: Sanitized source files from three pinned open-source projects, packaged with their license and source records.
Current limit: Use for the import branch only. The package does not represent every Altium version, object type, library system, or production design.
Download fileZIP / 7 KiCad files / GPL-2.0-only, GPL-3.0-only, and MPL-2.0
Provenance: Versioned KiCad files retained as a controlled pilot input with package notes and checksums.
Current limit: No broad KiCad-version or project-fidelity claim is attached; complete the object-level pilot before acceptance.
Download fileEvidence boundary
Failure recovery
A required source file is absent, misclassified, or fails during parsing.
Diagnosis: Compare the frozen source manifest with every Detected file row; record source format/version, missing or misclassified path, upload mode, wizard stage, exact parser message, and whether a destination exists.
Recovery: Keep the source copy unchanged, return to Upload, correct only a verified format classification or rebuild the disposable package from the approved manifest, then start a new import attempt with a new attempt ID.
Stop or escalate: Escalate when the required dependency cannot be identified, parsing still fails from the reconciled package, or recovery would require resaving production source files.
Evidence: Source manifest and identifier, detected-file captures, exact error, attempt IDs, package delta, product context, and migration-owner issue
Recheck: The new attempt detects every required file exactly once and reaches Preview documents; all preview and downstream fidelity checks remain required.
Preview counts, Primary board, layer mapping, units, origin, or behavior flags differ from the approved plan.
Diagnosis: Record each source value, preview or option value, affected board/layer/object class, tolerance where applicable, selected Primary board, and every item marked Will be skipped.
Recovery: Use Back, correct only values resolved by the authoritative source baseline, and regenerate the final review summary without creating a destination.
Stop or escalate: Block creation when the authoritative board, layer purpose, unit, datum, hierarchy policy, or transformation choice remains ambiguous.
Evidence: Source comparison, before/after wizard captures, mapping plan, skipped-board register, warning text, reviewer decision, and issue IDs
Recheck: Every final-review value equals the approved plan and every remaining warning maps to a named post-import check; otherwise Create project remains blocked.
Create project fails, creates an ambiguous destination, or the expected tree does not persist after reopen.
Diagnosis: Record organization, exact name, submit time, final review values, completion/error text, Projects search results, destination IDs when visible, and missing or unexpected tree entries.
Recovery: Do not submit Create project again until Projects is reconciled. Preserve any partial destination, assign its disposition, and retry only with an owner-approved new attempt identifier when no valid destination exists.
Stop or escalate: Escalate when destination identity is ambiguous, duplicate cleanup ownership is unknown, the same state fails twice, or expected content disappears after a reported save.
Evidence: Final review capture, exact result, Projects inventory, destination tree captures, timestamps, role, product context, and owner decision
Recheck: Exactly one intended destination reopens from Projects with the recorded tree; blank or import scope matches the run record, while import fidelity remains explicitly unverified.
Task-specific troubleshooting
Confirm that the signed-in role can create projects. Do not use another person's account or a production workspace to bypass the permission boundary.
Open the existing project or apply the team's naming convention. Do not add an arbitrary suffix that hides whether this is a new pilot or the original design.
Return to Upload, compare the file list with the source manifest, and consult the dated Supported formats matrix before continuing.
Stop at Preview documents, capture both values, and reduce the pilot to the smallest source set that reproduces the mismatch.
Select the intended board before continuing. Record every other board as skipped and import it into a separate project when it must be retained.
Do not guess from layer color. Compare the source stackup and fabrication notes, then set the destination row explicitly.
Preserve the exact error, project name, source format, file count, and current wizard step. Retry only after checking that a partial destination was not created.
Keep the source copy unchanged, record missing sheets or board data, and treat the import as failed fidelity verification rather than repairing it immediately.
Decision gate
Organization and project identity, selected branch, source manifest when imported, upload/preview/options/final-review records, warning register, single-result reopen evidence, visible destination tree, and signed bounded disposition
Project identity is ambiguous, a required source file or board is missing, settings differ from the approved plan, creation/reopen is unresolved, or import completion is being used as object-level fidelity 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.
ContinueBuild a schematic from scratchAdvance only within the scope permitted by the completed decision gate.