Spec sheet · Takshan-DMS · Document management
Every record gets a lifetime. And a lawful end.
A records platform must do two opposite things well: keep a record exactly as long as the schedule requires, and end it — on time, with a certificate, and never while a legal hold stands. Takshan-DMS was machined around that discipline.
- Designation
- Takshan-DMS
- Class
- Document management
- Status
- In catalogue
- Drawing
- Sheet 01
- One action
- The working session

Station rail — the life of a record
- 01Capture
Records enter once, into one register — and the register is the truth of what exists.
- 02Classify
Every record gets a class, and the class carries the rules: who may see it, how long it lives, how it dies.
- 03Route
Files move on defined routes with defined approvers, and the route survives as part of the record.
- 04Retain
Retention follows the schedule attached to the class, not a clerk's memory. The register shows what is due, and when.
- 05Dispose
When retention expires, destruction is proposed, approved, executed and certificated — a record of the ending, kept after the record itself is gone.
The interlock
A legal hold is a latch, not a memo.
When a hold is placed, disposal is not discouraged — it is blocked. Nothing under hold can be destroyed, by anyone, until the hold is lifted. The interlock is the difference between a records policy and a records system.
What's in the case
- Lifecycle register
- classification with rule-bearing classes
- defined routing and approvals
- retention schedules
- legal hold
- certificated disposal
- role-based access
- audit trail on every action
Provenance
The engineering story of this platform lives on the Synaptron corporate site.
Tolerances
Takshan-DMS is a document management system: the register, the routes, the lifecycle. It is not a digital-asset platform, and optical character recognition is not among its claims — if scanned-paper capture is central to your archive, bring that to the session. Migration from an existing archive and the security specification are session questions until their published sheets land; we would rather say that than imply them.
Deploy
Runs on your infrastructure or ours.

See a record live its whole life.
Thirty minutes on the mechanism itself — the register, the routes, the hold, the certificate.
Book the working session