Assessment workflow & conclusions

1. Select the system

Confirm system, version, purpose, users, affected people, data, action capability, jurisdictions and organisation roles.

2. Review authoritative routing

Confirm Nigerian nexus and work through all 19 NAGF regulatory routes. Resolve conflicts and retain screening where facts are unknown. Complete the decision owner, reviewer, next review and scope rationale, then use Approve authoritative NAGF scope. Initial suggestions are not authoritative until this approval is saved.

3. Verify legal sources

For each applicable legal lane, check the official source, status, effective date, provision, regulated role and current notices.

4. Work through all seven sections

For each of the 108 items:

• Read the source status and proposition.
• Use the assessor playbook.
• Decide Compliant, Non-compliant or N/A.
• Choose depth.
• Record system-specific rationale.
• Link evidence and tests.
• Raise findings.

5. Apply depth

For Non-compliant:

1. Not started.
2. In progress.
3. Near complete.

For Compliant:

1. Ad hoc.
2. Defined.
3. Embedded.

Depth does not change the binary compliance result. Near complete remains non-compliant; ad hoc compliance may be fragile and weakly assured.

6. Approve valid exclusions

Complete the category, legal or operational basis, owner and review date before approving N/A. Unapproved N/A remains in scope.

7. Review evidence and findings

Confirm that compliant claims have current operating evidence, failed tests are adverse evidence, and open findings are reflected in the item result.

8. Complete the current-law conclusion

Choose:

• Assured compliant
• Partially supported
• Material gap
• Not applicable
• Insufficient information

The narrative should state the system scope, applicable binding routes, evidence, material gaps, accepted risks, decision and limitations.

9. Complete the readiness conclusion

Choose:

• Ready
• Partially ready
• Not ready
• Not assessed

This separate narrative covers policy strategy, responsible-AI practice, best practice and proposed legislation. It must not be blended into the current-law result.

10. Confirm

Confirmation requires:

• Complete binding assessment gates.
• Named assessor.
• Named legal or compliance reviewer.
• Both status selections and narratives.
• Evidence cutoff.
• Next review.
• Reassessment triggers.

When all displayed gates are satisfied, use Confirm human assessor conclusion. Confirmation saves the assessor’s current-law and readiness decisions as the human conclusion for the selected system. The AI Assist output remains advisory and does not perform this confirmation.

11. Maintain

Reassess after changes to the model, data, purpose, geography, sector, licence, role, supplier, incident, law, official guidance or regulator status.

Completion checklist

• Correct system selected.
• Nigerian nexus and 19 routes reviewed.
• Official sources verified.
• All applicable items assessed.
• Policy and proposed-law items remain separate.
• N/A decisions are approved.
• Compliant claims have operating evidence.
• Findings and failed tests are reflected.
• Current-law and readiness conclusions are distinct.
• Assessor, reviewer, cutoff and next review recorded.
• Authoritative NAGF scope approved and saved.
• Human assessor conclusion confirmed.