Every change, who made it, and when.
Every edit is logged, so you can show who changed what, and when.
In short
The audit trail logs changes to each incident: who changed what, when, and from which value to which. Approvals, AI-drafted fields and sign-offs are in the history, so a surveyor, auditor or attorney can follow the record from first report to closure.
SAMPLE RECORD · SYNTHETIC DATA
Audit trail
Change history
Field-level changes with the person, the time, and the before and after.
Approvals and signatures
Who attested, who approved and who closed it, with timestamps.
AI use is visible
See which fields Lauren drafted and who approved them.
Role-based access
Role and facility decide who can view or edit a record.
Stronger record locks
Append-only protections (entries can be added, never changed) and closed-record locks are being strengthened on a published roadmap.
Rolling out
From first touch to done.
- Work the recordEvery edit is logged as it happens.
- Review the historyFilter by person, date or field.
- Export with the packetThe trail travels with the incident.
Audit trail: frequently asked
Something we missed? Ask us, and a person answers.
Can records be edited after closure?
An authorized role can reopen a closed record. The reopen and every later edit show in the history. Stronger closed-record locks are rolling out.
Is the audit trail enough for HIPAA?
No. An audit trail is one of several safeguards HIPAA expects. See the HIPAA page for how IncidentKit approaches the Security Rule.
Start with one incident.
Create your kit in about ten minutes and report the first incident the same day. Free to start, no card.