> ## 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 read a record's change history as a conversation
- URL: https://blog.jestor.com/read-record-history-as-a-conversation/
- Published: 2026-09-16T18:51:41.000Z
- Updated: 2026-09-16T18:51:41.000Z
- Author: Bruno Bannach

Presenting a **record change history** in chat format makes it readable by people who are not looking for an audit trail. In **Jestor**, a dedicated updates tab on the card shows what changed in a conversational layout, separate from the comment thread.

## Why a technical log is the wrong format for most people

An audit log is designed for investigation: precise, complete and dense. That is exactly right when something has gone wrong.

It is exactly wrong when someone simply wants to catch up on a record before a meeting. They need a narrative, not a table of field changes.

Where the conversational format helps:

- Catching up on a record you have not opened in weeks
- Understanding what happened while you were away
- Handing a record over to someone else
- Reviewing a case before speaking to a client
- Seeing changes and discussion in a similar shape

## Updates tab versus comments

| Aspect     | Updates tab                | Comments                 |
| ---------- | -------------------------- | ------------------------ |
| Content    | What changed on the record | What people wrote        |
| Written by | The system                 | People                   |
| Purpose    | Following changes          | Discussion and decisions |
| Format     | Chat style                 | Chat style               |

## Step by step to enable it

1. **Open the form editor** for the card.
2. **Find the updates option** among the card tools.
3. **Enable it**, since it is not active by default.
4. **Save and open a record** to see the tab.
5. **Change a field** and watch the entry appear in the updates tab.
6. **Keep sending updates to the chat** as well, if your team prefers both.

## Why separating updates from comments is the right call

Mixing system changes into the comment thread makes both harder to read: the discussion gets interrupted by field updates, and the updates get buried in conversation. Two tabs in the same format gives each the room it needs while keeping them equally easy to scan.

- **Dedicated tab:** changes separated from discussion
- **Conversational layout:** readable without interpretation
- **Enabled per form:** you decide where it appears
- **Chat option retained:** updates can still be sent to the thread

## Frequently Asked Questions

### Is the updates tab enabled by default?

No. It is activated in the form editor for the card. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Is this the same as the comment thread?

No. Comments hold what people wrote. The updates tab holds what changed.

### Can updates still appear in the chat?

Yes. Sending updates to the chat remains available.

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