Mersal Document Management
The problem
"Final_v3_REALFINAL.pdf" is a filing system. So is a shared drive where anyone can overwrite anything and a deleted file is simply gone. Neither survives a question about which version was the one sent.
How Mersal solves it
Documents live in the matter, in nested folders, with full version history. A previous version can be restored, a document can be checked out so two people cannot overwrite each other, and deletion is a recycle bin rather than an ending.
How it works
Versions you can go back to
Uploading a new version keeps the old one. History is visible per document, and restoring a previous version is a normal action rather than a support request.
Check-out, so edits do not collide
A document can be locked while someone works on it, which is the difference between collaboration and two people quietly producing two truths.
Deletion that is reversible until it is not
Deleted documents move to a recycle bin, can be restored, and are only then permanently removed. Categories and confidentiality classifications travel with the document.
The boundary is in the database
Access is filtered by firm and matter at the database, not by hiding buttons, and storage objects are scoped the same way — so a document belonging to another firm is not merely invisible, it is unreachable.
What it prevents
- Overwriting the version that was actually filed
- A deletion that cannot be undone
- Documents reachable outside the firm that owns them
The fastest way to judge this is to watch it run against your own way of working.