Quick start / eight checkpoints
Use the fictional Atlas fixture to follow one record from project navigation through evidence, readiness, handover output, and final approval. Check each step as you go; the checklist stays in this browser tab only.
Review progress
0/8
local checkpoints reviewed
Start here
Begin at the live Atlas project, then read the hierarchy from project to system, subsystem, and equipment before opening a record.
Expected observation
The overview identifies the project and exposes the live record counts that the rest of this walkthrough follows.
Navigate parent-first
Use the subsystem as the parent context, then open its motor control center. Do not jump straight to an isolated equipment record when tracing a scope.
Open
Expected observation
You can explain where MCC-07-02 sits in the Atlas hierarchy before reviewing its evidence.
Tests & evidence
On the healthy target, start with commissioning tests and confirm that the linked evidence is attached to the same tag. The detail anchors keep each register in view.
Open
Expected observation
MCC-07-02 shows passed tests and approved document evidence rather than a status inferred from the parent scope.
Registers
Use the project register to check certificate requirements and calibration evidence across the same project. A file being present is not the same as being accepted.
Open
Expected observation
Approved evidence satisfies a requirement; in-review, rejected, or missing records remain visible as readiness work.
Defects
Move from SUB-204 to LT-204-003, then read the test, punch, and NCR areas on the tag detail. Follow the record type instead of treating every open item as interchangeable.
Open
Expected observation
The failed point-to-point test, open NCR, and rejected certificate all point to LT-204-003 and explain why that scope is not ready.
Roll up readiness
Open the completion board after reviewing the detail records. Match each scope’s aggregate status to the underlying tests, defects, documents, and handover notes.
Expected observation
SUB-307 is complete; SYS-200, SYS-300, SUB-204, and SUB-301 remain in progress or blocked for the reasons shown in their notes.
Compile handover
Use the healthy MCC-07-02 target to open a tag handover output. This compiles the current register into a reviewable dossier; it does not approve the scope.
Open
Expected observation
The output brings hierarchy, tests, punches/NCRs, documents, certificates, and commissioning records together with an overall status.
Final review
Open commissioning records for the Atlas project, select the HANDOVER record, and review its status. An administrator performs the final Approve handover action after the evidence is ready.
Open
Expected observation
The handover review is complete and resolved before approval; compiling an output and approving a review are separate actions.
The public example project and completion board are readable without a workspace account. Tag detail, evidence registers, commissioning records, and handover outputs require sign-in. Approval controls are available to administrators only.
Failed or blocked tests, unresolved tests, active blocking punches or NCRs, missing, rejected, or in-review evidence, incomplete documentation, and an incomplete or unresolved handover review all keep a scope from approval. A handover output compiles the evidence; only an authorized administrator can use the separate Approve handover action on the HANDOVER record.
Evidence accepted for the linked tag.
Evidence exists but still needs QA or owner review.
An expected evidence record with no approved file; it is not a download.
Evidence is present but does not satisfy the linked requirement.
One useful rule
Follow the tag, then trust the linked evidence.
A complete handover is a relationship: the right equipment, passing tests, resolved defects, accepted documents, and a scope note that agrees with all of it.
Reopen the full overview