Control design & effectiveness.

Join obligations, risks, control ownership and dated test results to review design and operating effectiveness.

Use the shared control register. Fields: id, title, owner, status, reviewDate, notes, obligationId, riskId, classification, effectiveness. Records link by ID to related entities. Validate inputs, assign an owner and set a review date.

Related workflows: regulatory-obligations, audit-readiness, continuous-assurance. Reuse linked records in suite views rather than duplicating facts. The suite and specialist workspace use distinct import formats; export and reconcile records explicitly when crossing between them.

Review required fields, supporting evidence, relationships and decision rationale. Export the suite JSON dataset for handover. This workflow organizes oversight metadata; external collection, recovery testing and regulatory interpretation require separately verified evidence.

Adapt this pattern

Bring the real decision boundary, authorized metadata, evidence available, accountable reviewers and target date. The workflow can then be scoped around explicit outputs and acceptance criteria.

Use the linked source records and assessment dates to review the scenario basis.