An immutable trail of who changed what and when, written automatically across the platform, so accountability is a fact you look up instead of an argument you have.
Automatic, immutable log entries with before-and-after values and a per-record timeline, across every module.
A log entry on every change, and a history you can actually use.
As work happens across the platform, Relay writes a log entry for each change, the user, the timestamp, and the before-and-after values, so status flips, edited amounts, reassignments, and deletions are all on the record instead of a mystery nobody can explain later.
Every record carries its own history, and user activity reports show what a person did over a period. When a customer disputes a date, a carrier asks for documentation, or something looks off, the answer is already there, not reconstructed from memory.
What changes when every change is on the record.
When every change is on the record, "who moved this job to completed?" is a fact you look up, not an argument.
Customers and carriers question dates, amounts, and scope. An immutable log answers them without a scramble.
Audit entries are written as work happens and are never edited or deleted, so the trail holds up when it matters.
The log is written automatically as people work. Nobody has to remember to record anything.
The audit trail spans every module, so any record’s history is one scroll away.
Changes across the platform, status flips, edited amounts, reassignments, and deletions, with the user, the timestamp, and the before-and-after values.
No. Audit entries are immutable, written as work happens and never changed, so the trail holds up in a dispute.
Yes. Every record carries its own timeline you can scroll, and user activity reports show what a person did over a period.
No. The log is written automatically as people work, so there is nothing to remember to record.
About an hour with a restoration specialist. We'll open a record’s timeline and walk how changes are logged.
