Feature
Always know which document version is current
A document vault is only useful if it's clear which file is current and which one expired last year. Meridian tracks expiry dates on every document and chains superseded versions together, so 'which one is the real one' is never a question.
The problem
Old versions of a lease, NOC or insurance certificate sitting in the same folder as the current one create exactly the ambiguity that causes someone to act on outdated information.
Why it matters
Acting on an expired NOC or a superseded lease term isn't just an inconvenience — it can undermine a compliance filing or a dispute position built on the wrong document.
How Meridian helps
- Expiry dates tracked per document, feeding directly into the compliance engine's expiry sweeps
- Supersession chains link an updated document to the version it replaces, so history is preserved without ambiguity
- Visibility scoping (org-only, owner-visible, tenant-visible) carries over automatically to the current version
- AI extraction populates expiry dates on upload, for English or Arabic documents
FAQ
What happens to the old version when a document is superseded?
It's kept in the supersession chain for history, but the current version is clearly marked so there's no ambiguity about which one is active.
Does expiry tracking trigger a reminder?
Yes — document expiry feeds into the same expiry-sweep workflow that flags lapsing compliance-relevant documents ahead of time.