TRUST HUB › PROCUREMENT PACKIn preparation
Incident response and reporting
How a school reports a concern, and what Aevum does next.
In preparation
This document is being written, and we have published the page now rather than leave you guessing. A school evaluating us should be able to see exactly what is coming, what it will contain, and what has to happen before it is signed off. Treat this page as the plan, not as the finished document.
01
In preparation
What this document will contain
- How to report a safety or data concern, and who receives it
- Notification to the controller, and to the ICO where required
- How a fix is tracked to closure and communicated
- Post-incident review shared with affected schools
02
In preparation
What we are doing to finish it
We publish this alongside the written procedure and the complaints mechanism the DfE governance standard requires, both of which are next on the list.
03
In place
If you need this now
If your procurement timeline needs this document before it is finished, write to hello@aevumfoundry.ai. You will get a straight answer about where the work has got to, and we will never dress it up as further along than it is.
Last reviewed . What changed and when.Questions: hello@aevumfoundry.ai