Specify triggers, state and permissions
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
A trigger announces that something may need doing; it does not guarantee that the action is still appropriate. Identify the record and check current state before acting. Define required inputs and the system allowed to provide them. Grant the workflow only the access needed for its task. Separate preparing a draft from sending it. Avoid using broad administrator credentials for convenience. State how approvals are linked to a particular version of the content so a later edit cannot silently inherit an old approval.
Worked example
An interview booking triggers pack preparation. Before sending, the workflow checks that the interview is still scheduled, the candidate has not withdrawn and the reviewer approved the current pack version.
Put it into practice
Write trigger and pre-send checks for your workflow.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Include stable identifiers, required fields and current-state validation. Approval should identify what was approved and become invalid if material content changes.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- GOV.UK: Responsible AI in recruitment
UK guidance on procuring and deploying recruitment AI.
- NIST: AI Risk Management Framework
Voluntary framework for organising AI risks and controls.