System selection in assessments
Framework assessments are system-scoped. The system selector determines whose intake facts, routing decision, scores, evidence and AI Assist output the module loads. Selecting the wrong system can produce a well-formed but irrelevant assessment, so always verify the scope banner before scoring.
What selector states mean
Section titled “What selector states mean”| State | Meaning | Action |
|---|---|---|
| Selectable | The system has the minimum confirmed records required by that module. | Select it and verify the displayed name and scope. |
| Greyed out | The system exists but a prerequisite, route or confirmation is incomplete. | Follow the displayed reason back to intake, ACRS or routing. |
| Not listed | The record is outside the current workspace, unavailable to the user or not eligible for the module. | Verify workspace, role, entitlement and system status. |
| All controls / framework overview | No system-specific record is loaded. | Use for catalogue review only; do not mistake it for a completed system assessment. |
Some frameworks have additional legitimate prerequisites. ACRS confirmation can be required before GTSAF depth is final. ISO/IEC modules require an applicable licence confirmation. ATF is assessed per agent rather than as a generic system catalogue. Legal frameworks may require their authoritative scope gate before a conclusion can be confirmed.
Safe workflow
Section titled “Safe workflow”- Complete and save the AI System Record.
- Complete intake facts and resolve routing-incomplete prompts.
- Review and, where required, approve the ACRS score.
- Open the routed assessment from the plan or use the framework selector.
- Confirm that the system name, scope and assessment status have changed.
- Score, add evidence and run AI Assist only after that confirmation.
If the selector returns to the framework overview, do not continue entering system evidence. Refresh the routing plan and verify the prerequisite records. Results already saved for another system remain associated with that system; they should not be copied merely to make the new assessment look complete.
AI Assist and system scope
Section titled “AI Assist and system scope”AI Assist output is stored against the selected system or agent and assessment item. Switching scope must not present the previous system’s output as current. The output header should identify the analysed system. If it does not, stop and re-establish scope before relying on the analysis.
Troubleshooting checklist
Section titled “Troubleshooting checklist”- Correct client, workspace and system selected.
- Intake save shows a successful state.
- Required authoritative facts are resolved.
- ACRS is confirmed where the route requires it.
- The framework appears in the server-authoritative plan.
- The user’s role and plan both permit the framework.
- The record is active and has not been retired.
See Routing & applicability for how prerequisites affect the assessment plan without changing subscription entitlements.