SaaS(DMS/IDP) Operations & Data Governance
Digitised is not the same as governed. A scanned file with no custody trail is a liability with better search.
Document programmes are bought as technology and fail as operations. The scanner works, the OCR is acceptable, the repository is searchable — and yet nobody can say who last had custody of a file, whether a batch was verified or merely marked verified, what the retention rule is for a record class, or on what authority anything was ever destroyed.
In court-record and statutory work the exposure is not commercial, it is legal. A missing chain of custody is not an inconvenience to be reconciled later; it is the whole value of the record. And the failure is almost never at the scanning step, which is the step everybody measures. It is at handover, at exception handling, and at disposal — the three steps with no obvious owner.
The second problem is that quality is measured on throughput because throughput is easy to count. Pages per day tells you nothing about whether the index is right, and an index error is discovered years later by the person who needed the document.
One mandate, in full
CBSL Groups · interim operations mandate · 2024–A two-year fixed-term mandate running the DMS division of CBSL Groups, which delivers court-record digitisation for the Delhi, Tamil Nadu and Telangana judiciaries. Embedded and accountable for the division — IT, software, HR, finance, admin and supply chain — rather than advising someone else who ran it.
A site audit inside the first day.Then Pareto on the failure record rather than on opinion. Scanners and UPS units were burning out repeatedly and stopping production for days at a time; the cause was an equipment earthing fault, not the equipment. A second thread: disk procurement was climbing against a storage trend nobody had read — large volumes of deleted data were sitting in recycle bins and counting against capacity.
Fix the cause, then govern the process that hid it.Earthing corrected and the burnouts stopped. A data-clearance process ended the procurement spiral. SOPs written where there had been practice only — site set-up for digitisation projects, vendor onboarding, vendor payment and HOTO. Site set-up itself moved to a managed-services model — a first for CBSL — taking CAPEX on new court sites to zero.
A weekly review that the division runs itself.A structured weekly review with every project manager and head, and a second review template across the seven internal support functions the division depends on. Both were firsts for the organisation. The cadence is what holds the rest in place: accountability sits with a named person, and the corrective actions it produces are tracked rather than discussed.
Figures are the mandate’s own, and each is tied to the change that produced it rather than reported as a total.
How I work it
Walk the lifecycle end to end — acquisition, preparation, capture, index, QA, exception, storage, retrieval, disposal — and find the steps where custody changes hands without a record.
Workflow and HOTO SOPs with custody recorded at every handover, exception handling with a named owner, sampling-based QA on index accuracy, and a retention matrix the workflow enforces.
A governance scorecard on custody, index accuracy and retention compliance, reviewed monthly, with disposal authorised rather than assumed.
Tools and frameworks
Placed against the stage each one serves, and against the artefact it leaves behind. A framework that produces no artefact is a word.
| Framework or instrument | Analyse | Act | Adhere | Artefact it produces |
|---|---|---|---|---|
| Document lifecycle mapping, acquisition to disposal | ● | ○ | – | Lifecycle map with every custody handover marked |
| Custody and chain-of-evidence design | ○ | ● | ● | Custody log — who held what, when, on whose authority |
| Index accuracy sampling and QA design | ● | ● | ○ | Sampling plan and an accuracy figure that means something |
| Retention and disposal matrix by record class | ○ | ● | ● | Retention matrix the workflow enforces, not a policy PDF |
| Exception and HOTO workflow SOPs | – | ● | ● | Versioned SOP set with a handover that closes |
| Risk oversight framework for document operations | ○ | ○ | ● | Register of control failures by likelihood and consequence |
The responsibility matrix — custody and control
The artefact the Act stage produces. “As found” is what a typical intake looks like — not a description of your operation.
| As found — typical intake | As governed — on exit | |||
|---|---|---|---|---|
| Control activity | Accountable | Evidence | Accountable | Evidence |
| Custody at each handover | Assumed | None | Batch supervisor | Signed custody log per batch |
| Index accuracy verification | Operator self-check | Throughput count | QA lead | Sampled accuracy rate, reported weekly |
| Exception handling | Whoever notices | Operations manager | Exception register with closure dates | |
| Retention rule application | Policy document | Unenforced | Compliance owner | Retention matrix bound to record class |
| Disposal authorisation | Nobody named | None | Compliance owner | Disposal certificate with authority cited |
A scoped, paid review of custody, index quality, exception handling and retention against the record classes you actually hold.
Monthly review of custody, accuracy and retention compliance, with the scorecard run by your own QA team.
What good looks like
The state a completed engagement leaves behind — the definition of done we agree at the start. Not a result already achieved.
| Area | What good looks like | How you would know |
|---|---|---|
| Custody | For any file, you can say who held it, when, and on whose authority it moved. | Custody log |
| Quality | Accuracy is a sampled figure on the index, not a count of pages processed. | QA sampling record |
| Exceptions | Every exception has an owner and a closure date, and the register is empty of anything old. | Exception register |
| Retention | The retention rule is applied by the workflow, not remembered by a person. | Retention matrix |
| Disposal | Nothing is destroyed without a named authority and a certificate. | Disposal certificates |
For any file, you can say who held it, when, and on whose authority it moved.
Accuracy is a sampled figure on the index, not a count of pages processed.
Every exception has an owner and a closure date, and the register is empty of anything old.
The retention rule is applied by the workflow, not remembered by a person.
Nothing is destroyed without a named authority and a certificate.
Thirty minutes, and you will know whether this is worth pursuing
A structured conversation about where your operation is losing money, not a sales call. Mon–Sat, 09:00–18:00 IST, on Google Meet, in English or Hindi. Nothing is required from you in advance.
Book a DMS Governance DiagnosticControl questions across the document lifecycle, acquisition to disposal, that separate digitised files from reliable information — with the custody and retention questions an auditor would actually ask.
↓ Download · PDF, 3 pp