A control fits inside a process. It does not sit in front of one. A control objective says what has to be true. The control is the activity that makes it true. It has a trigger, an owner, inputs and a work product. Assurance is the sample of that work. A control that has none of these is a statement that something was considered.
The tick
A tick treats the control as a line that has been marked. There is no trigger, no owner, no input and no record that shows the control ran against a named system. The same mark can sit on every system in the estate. A tick is a useful reminder. It is not a control. It cannot be sampled. An Information Officer, an assessor or the governing body who asks what happened the last time the control was supposed to fire has nothing to look at except the mark.
This is the difference between a document pack and a quality management system, and between a checklist library and a working management system. A file that describes design control, validation, data management, change control and ongoing monitoring, written after the system was built and without those processes having run, fails the consistency test that appears under the EU AI Act (where it applies) and under POPIA's requirement that the compliance framework be implemented, monitored and maintained. A tick against a line is that file in miniature.
Order of work
Set the control objectives first. Apply the intended-purpose, state-of-the-art and proportionality lens before controls are chosen. Determine the operating, supervisory, administrative and fiduciary controls. Prefer design-time prevention. Embed those controls in running processes. Then map scope. That is the Statement of Applicability. Then choose the assessment type from the environment that actually exists.
A Statement of Applicability is a scope artefact. It records which determined controls apply to which use, and which do not. It is not the system of internal control, and it is not an assessment of that system. Writing a SoA before the controls exist is how the map becomes the territory in the file and nowhere else. Accepting a SoA as proof that controls exist is the same mistake from the other side.
What a control looks like when it is in a process
In a quality management system under EN 18286 (where the EU AI Act reaches the organisation), a life-cycle stage has a gate. The gate checks that the stage's records exist, that verification and validation are done, and that the right roles have signed off before the work moves on. Separation of duties is built in. Whoever prepares a record cannot approve it. That is a control. It has a trigger, the stage being ready to close. It has an owner. It has a work product, the signed record. It can be sampled.
Under POPIA, the control is the ongoing implementation, monitoring and maintenance of the compliance framework, together with the personal information impact assessment and the operator contract. Awareness of an incident starts a clock. A rights request must be answered. A skipped stage is visible. The approved record is locked. That is a control. A field that says "POPIA: complete" is not.
In AICOB, every material outcome has a governing-body role and a management owner. The control serves a control objective. The measure says how the organisation knows. Assurance samples the work product. Depth follows the system. The objectives stay the same. The practices scale.
Controls and the platforms
The platforms embed controls in the process rather than offering them as a library to be ticked. The product name changes with the topic. The method does not. A quality management system, an AI management system, an impact assessment or a governance workbench: each is a set of processes in which controls are assigned, run and evidenced. The fields on a page are the questions the organisation has to answer to operate that process. The people who own the duty fill them. The system keeps the record.
None of this certifies the organisation or declares it compliant. Those decisions sit with the assessor, the Information Regulator, a notified body where the EU AI Act applies, or the governing body itself under King V. The system makes the work visible so the decision can be made on evidence.