Charter the engagement.
A one-page charter establishes project name, client, target standards, validation posture and reviewer. Downstream stages unlock once the charter is saved and approved.
Upload the full register for analysis.
Upload the complete workbook, including source tabs such as FAR reconciliation, so the validator can inspect the full evidence set; the module does not assume uploaded classifications or assignments are correct.
Full-file analysis
Select the workbook first, then choose the standard and sheet. The full file is posted to the validator endpoint; source tabs remain available for reconciliation and the raw input sheet is preserved in the report.
Endpoint: POST /api/hierarchy/validator/hierarchy/validate/export. Admin or manager bearer required. OptimalAI enrichment runs only when the project is licensed for it and the box above is ticked.
Explore the validated hierarchy.
Search, restructure and edit the validated register as a hierarchy. Explicit parent links are honoured first; where the source workbook has no parent, display-only grouping is inferred from the asset tag so the full register can be reviewed without assuming the uploaded classification is correct.
No register loaded yet. Run validation on Stage 2 and the explorer will populate from the validated rows.
Click a node in the tree to see its detail.
Validate the working hierarchy.
This stage validates the exact register carried forward from Build & sort, including local edits made in the hierarchy editor. Validation is performed directly against the working hierarchy register carried forward from Build & sort.
Working register
Run source validation and build the hierarchy before completing this stage.
Findings by severity and standard
The heatmap is computed from the current working register. It carries forward hierarchy edits, open findings and OptimalAI review state already attached to each row.
Approve the hierarchy package.
Approval records the current hierarchy, validation summary and reviewer note as the package that may be handed to downstream OptimalAvailability Studio modules.
Approval checklist
Package summary
Waiting for validation.
Disseminate to the platform.
The manifest below shows which downstream modules can consume the approved hierarchy now, what remains blocked and which export artefacts are available from the current working register.
Live handoff manifest
Approve the hierarchy package to unlock downstream handoff actions.