LEARN
What is an append-only audit log?
An append-only audit log is a record of system activity where entries can only be added — never edited, never deleted. When a job status changes, an inventory count is adjusted, or an invoice line is corrected, the log gains a new entry that says who made the change, what it was, and when. The previous state stays in the record. Nothing is silently lost.
Most business software works the other way: an edit overwrites the old value, and the old value is gone. For a service business, that difference decides whether a billing dispute, an insurance claim, or a compliance question is settled by the record or by memory.
Append-only means the past cannot be rewritten
Ordinary software stores the current state of a record. Edit a field and the old value is replaced. Some tools bolt on an edit history, but it is usually partial — a few tracked fields, a feed that truncates after ninety days, a log an administrator can purge. A history that can be trimmed is not a record. It is a courtesy.
An append-only log inverts the design at the write path itself. The system can add entries; it cannot rewrite them. A correction is a new entry that supersedes the old one, and the old one stays where it was. The question is never "what does the record say now" — it is "what has the record said, in order, since the beginning."
Why business software needs an audit trail
Service businesses run on claims about the past. The client says the equipment came back Tuesday; the technician says Thursday. An invoice line is disputed six weeks after the job closed. An adjuster asks who authorized the extra days on site. If the software only holds current state, every one of these becomes a memory contest between people with opposite incentives.
With an audit trail, they become lookups. The record shows the status change, the timestamp, and the member who made it. There is nothing to reconstruct and nothing to argue about, because the system never had the ability to forget.
Immutable record keeping for disputes, claims, and compliance
Disputes: a scope or billing disagreement is resolved by reading the entries in order — what was requested, what was changed, who changed it. The side with the record usually stops needing the argument.
Insurance claims: adjusters want timelines, not summaries. When work and equipment movements are logged as they happen, the claim file writes itself from the record. Documentation of what happened and when is the difference between a paid claim and a denied one.
Compliance: many obligations are not about current state but about how you got there — who accessed what, who approved what, what the value was before it changed. An append-only log answers those questions without a reconstruction project, because the answers were written down at the moment they happened.
What a complete audit log captures
Not every feature labeled "activity log" clears the bar. A record you can take into a dispute needs all of the following, and most tools quietly skip one or two.
- Who made the change — a named, signed-in member, not a shared login
- What changed — the field, the value before, the value after
- When it changed — a timestamp the user cannot set
- Entries that cannot be edited or deleted, by anyone, at any permission level
- Coverage across the whole system, not just one module
- A record you can actually search when the question arrives
How Vercid handles it
Vercid keeps an append-only audit log across each workspace. The spreadsheet-style inventory grid feels like the spreadsheet your team already uses, with one difference: a changed cell is logged as a new entry, not overwritten, so the silent-overwrite failure mode of a real spreadsheet does not exist here. Full-text search runs over the record, so finding an entry from months ago is a query, not an excavation.
Every workspace is isolated with Postgres row-level security, and every action ties back to a member with a defined role and seat. The result is a single live record of the operation — the version of events you hand to a client, an adjuster, or an auditor without flinching. One record. Nothing lost.
What you get
- Append-only audit log across the workspace — entries are added, never rewritten
- Full-text search over the audit record
- Inventory changes logged as new entries, not overwrites
- Actions attributed to named members with defined roles
- Per-tenant isolation with Postgres row-level security
Common questions
What is the difference between an audit log and an activity feed?
An activity feed is a summary for humans: recent events, often truncated, often deletable, rarely complete. An audit log is the system of record: every change, attributed and timestamped, retained whether or not anyone is watching. A feed tells you what happened lately. A log proves what happened, period.
Can an administrator edit or delete entries in an append-only audit log?
No. Append-only means the write path can only add entries — there is no edit or delete operation to grant, so no permission level includes one. In Vercid, a correction is made by adding a new entry that supersedes the old one, and the original stays in the record.
How does an append-only audit log help with insurance claims?
It produces the timeline an adjuster asks for without reconstruction: when the job status changed, when equipment was placed and retrieved, who recorded each step. Because entries were written at the moment they happened and cannot be revised afterward, the record carries weight that after-the-fact notes do not.
If you want to see what an append-only record looks like against your own operations, we will walk you through one.
Book a walkthrough