Mersal Nothing important depends on memory.
The situation
A client disputes a fee agreed eight months ago, and separately asks why a filing went in when it did. Both answers are somewhere in the firm's history.
What goes wrong without a system
The answer is assembled from recollection, an email thread someone still has, and a spreadsheet that has been edited since. None of it is evidence.
How it runs in Mersal
Start from the matter
The matter workspace holds its own timeline: what was done, by whom, and when.
Read the ledger
The audit trail is append-only at the database and cannot be amended by any role, so what it says is what happened.
Produce the fiscal record
The invoice, its serial, its issue date and its frozen amounts — plus when the client first opened it and whether they acknowledged it.
Show the conflict clearance
The screen run at intake, its result, and the waiver reason if there was one, with the name of whoever recorded it.
Show the document as filed
Version history identifies the version that was actually sent, not the one edited afterwards.
What it prevents
- Reconstructing a timeline from memory
- A log that a privileged user could have edited
- Uncertainty about which version was filed
The fastest way to judge this is to watch it run against your own way of working.