How to build a useful audit log for internal software
Record decisions and sensitive changes in a form that helps your team reconstruct an incident without collecting unnecessary data.

In short
- Start with approvals, permission changes, deletions and exports.
- Use stable action names and group related entries using a case or request ID.
- Ask someone outside the development team to investigate a reversed approval.
- Next steps
On this page
Choose actions worth recording
Start with approvals, permission changes, deletions and exports. Record the actor, time, object, action and result. A version reference may be enough. Avoid copying entire documents or secrets into the log.
Make events searchable by job
Use stable action names and group related entries using a case or request ID. Distinguish system jobs from human actions. Restrict access to the audit history and set a retention period that fits its purpose.
Reconstruct a real scenario
Ask someone outside the development team to investigate a reversed approval. They should be able to see who decided, when the change took effect and what was sent to a connected system. Improve the events if they still need to find messages elsewhere.
Next steps
Creagrid / actie
Practical checklist
Describe the problem and intended outcome.
Involve the people who use the process every day.
Test the riskiest assumption with a small prototype.
Define tests, ownership and maintenance up front.

