> ## 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.

# How to make an approval chain auditable
- URL: https://blog.jestor.com/audit-an-approval-chain/
- Published: 2026-09-16T18:52:31.000Z
- Updated: 2026-09-16T18:52:31.000Z
- Author: Bruno Bannach

To **audit an approval chain**, four things have to be recoverable for every decision: who approved, when, on what basis, and whether the action came from a person or a system. In **Jestor**, that record is produced by the process itself rather than assembled afterwards.

## Why approval evidence is usually reconstructed

Most companies can tell you a purchase was approved. Proving it means finding an email thread, matching it to an invoice and trusting that the person who wrote the email was authorized at the time.

Reconstruction works until it is questioned, and by then the people involved have moved on.

What an auditor typically asks for:

- Who approved this specific amount
- Whether they were within their authority
- What justification was given
- Whether anything was changed after approval
- Whether an automation or a person made the entry

## What the trail must contain

| Element           | Why it is required        | Where it comes from      |
| ----------------- | ------------------------- | ------------------------ |
| Approver identity | Establishes authority     | The user who acted       |
| Timestamp         | Establishes sequence      | Recorded automatically   |
| Justification     | Establishes reasoning     | Required field per level |
| Attachments       | Supporting evidence       | Quotes and documents     |
| Change history    | Shows post approval edits | Record history           |
| Action source     | Person, automation or API | Audit log                |

## Step by step to make it auditable

1. **Make justification required** at each approval stage, not optional.
2. **Require supporting attachments** where the amount warrants it.
3. **Lock fields after approval**, so the approved values cannot be edited quietly.
4. **Enable the record history**, filtered per table.
5. **Confirm the log distinguishes** a user from an automation or the **API**.
6. **Export a sample** and check it is readable by someone outside the team.
7. **Test the trail** by asking someone to prove one approval end to end.

## Why locking fields after approval matters most

The weakest point in most approval trails is not who approved. It is that the amount could have changed afterwards. Making approved fields read only once the decision is recorded closes the one gap that makes everything else questionable.

## Why choose Jestor

**Jestor** records author, date and justification per approval, keeps attachments on the record, supports read only states after a decision, and offers a history view filtered per table that identifies whether a change came from a user, an automation or the API, exportable when needed. Certifications include **SOC 2** Type I and II.

## Frequently Asked Questions

### Can I prevent edits after an approval?

Yes. Fields can be set read only once the decision is recorded. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Does the log show whether an automation made a change?

Yes. It identifies a user, an automation or the API as the source.

### Can the trail be exported for an audit?

Yes. The filtered history can be exported.

## Video Tutorial: Step by Step

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://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.