← Vetro Attest · Free Art. 12/14 checker · Free EU AI Act tools
EU AI Act for emergency call centres and dispatch
*Engineering guidance, not legal advice. Your legal team decides how the Act applies to your products.*
Where this sector lands
Annex III point 5(d) covers AI systems intended to evaluate and classify emergency calls by natural persons, to dispatch or establish priority in the dispatching of emergency first response services, including police, firefighters and medical aid, and emergency healthcare patient triage systems.
In a public safety answering point that means speech-to-text with incident coding, cardiac-arrest detection during a call, priority scoring, and unit recommendation. An LLM that summarises the call for the dispatcher may be enough to bring the system into scope if its output drives priority.
Most deployers are public authorities or act on their behalf. They must use only systems registered in the EU database (Art. 26(8)) and carry out a fundamental rights impact assessment before first use (Art. 27).
The logging duties that follow
- Art. 12 (providers): automatic recording of events over the system's lifetime, so each classification and priority can be traced.
- Art. 19 (providers): keep logs under your control for at least six months.
- Art. 26 (deployers), the dispatch centre: competent human oversight by call-takers and dispatchers (Art. 26(2)), monitoring and reporting of serious incidents (Art. 26(5)), and logs kept for at least six months (Art. 26(6)).
Timestamps carry unusual weight here: a delayed ambulance is measured in seconds. Record clock source and times at each step, not only at call close. See Art. 12 logging and serious incident reporting.
On timing: the Digital Omnibus agreement moves Annex III high-risk obligations to December 2027 (details and caveats).
What counts as evidence
After a bad outcome, the inquiry asks what the system classified, when, what priority it proposed, and whether the dispatcher changed it.
Abbreviated ledger excerpt (prev, hash and sig omitted):
{"seq":1,"ts":"2026-09-20T02:14:07.412Z","type":"tool.result","data":{"name":"classify_call","output":{"code":"cardiac_arrest_suspected","confidence":0.88}}}
{"seq":2,"ts":"2026-09-20T02:14:07.590Z","type":"tool.result","data":{"name":"priority","output":{"level":"P1","unit_suggested":"ALS-07"}}}
{"seq":3,"ts":"2026-09-20T02:14:19.031Z","type":"tool.call","data":{"name":"dispatch","input":{"dispatcher":"dsp_14","unit":"ALS-07","priority":"P1"}}}
The hash chain fixes the order and timing of events. The countersignature shows the record existed before the inquiry began.
How Vetro Attest fits
Vetro Attest accepts an OpenTelemetry GenAI trace (OTLP/JSON) or a native Vetro ledger, with nothing to install. Verification is free. For 29 USD per ledger, one-off:
- a full EU AI Act report (Markdown and HTML) mapping the run onto the logging obligations, with an explicit list of what the log cannot show;
- an ed25519 countersignature over the ledger digest, event count and timestamp, verifiable by anyone with our published public key.
A practical pattern: countersign every call run automatically at call close, so the attestation exists long before anyone knows which call will be investigated.
Limits, stated plainly: the countersignature proves the log verified clean at a time, not that the classification or priority was right. The report supports a compliance conversation; it is not a conformity assessment. Paid ledgers are deleted after 7 days, and the report and attestation are emailed to you to keep.
Next steps
- Run the free EU AI Act Art. 12/14 checker against your current setup.
- Verify a trace free, then get the countersigned report for 29 USD.
- Compare approaches: vs. WORM storage, vs. RFC 3161 timestamping.
See a sample ledger verified in one click, check your own logs free or get the countersigned EU AI Act report.