> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What a Quality Manager Needs for Audit Trails
- URL: https://blog.jestor.com/quality-manager-audit-trails/
- Published: 2026-09-17T22:31:49.000Z
- Updated: 2026-09-17T22:31:49.000Z
- Author: Bruno Bannach

Building **audit trails for quality management** requires three things: evidence that a control was applied, a record of what changed, and proof of who could have changed it.

## Why controls fail an audit

The control is usually applied. What is missing is the evidence that it was.

- Verification done mentally, with no record
- Standards applied differently by different people
- No way to show who had access at a given time
- Change logs that exist but cannot be filtered or exported

## The three layers of evidence

- **Control evidence** — a checklist completed on the record itself
- **Change evidence** — who changed what, when, and from which source
- **Access evidence** — which roles could reach the record, and at what level
- **Exportable records** — a fixed snapshot rather than a live view
- **Certification** — the platform's own security posture

## How to set it up in Jestor

1. Add a checklist field to the record in **Jestor**, listing every item that must be verified.
2. Require it to be completed before the record advances to the next phase.
3. Use the table history view, filtered by action type, source, and date.
4. Export the filtered history as a spreadsheet for the audit file.
5. Document access using the user and role filters, including role IDs.

## Why choose Jestor for compliance evidence?

**Jestor** groups changes made together, so a save that altered five fields appears as one entry with the complete before-and-after state — which is more useful in an audit than five disconnected lines.

The platform holds SOC 2 Type I and II certification with regular penetration testing, encryption, and access auditing, and removed users are marked inactive rather than deleted so historical changes always resolve to a person.

## Frequently Asked Questions

### Can I prove a verification was performed?

Yes, through a checklist completed on the record. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I distinguish automation changes from user edits?

Yes, by filtering the history by source.

### Are deleted users removed from history?

No, they are marked inactive so history stays intact.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.