Document Management for Accountable Institutions

One governed place for every record, with permissions, approvals and an audit trail that hold up when they are examined.

HOW IT WORKS

From an arriving file to a governed record

A shared drive stores documents. It does not govern them.

It cannot tell you which version is in force, who approved it, who has read it, or whether the copy in the branch folder matches the one at head office. Each document here goes through four stages that answer those questions by default rather than on request.

01

Capture it wherever it comes from

Upload directly, import in bulk from a spreadsheet, connect Google Drive, Dropbox or OneDrive, index email, or save from the browser without leaving the page.

02

Classify and enrich it

Category, document type, owner and branch are attached on arrival, and dates, reference numbers and parties are extracted automatically. Scanned pages are read so their text is searchable too.

03

Control who can act on it

A record stays private to whoever added it until deliberately shared. Permissions decide who can see, edit and approve, and approvals can require several people rather than any one.

04

Keep it findable and accountable

Status marks what is draft, active or superseded, duplicates are caught on the way in, and every action is recorded in a tamper-evident history.

What it does without being asked

Filing is where document systems fail, because it depends on someone doing it consistently. These run on every document as it arrives.

Automatic renaming

Files arrive named IMG_4471 or scan0032 and are renamed to something a person can recognise later.

Automatic categorisation

Documents are sorted into the right category on arrival instead of waiting for someone to file them.

Metadata extraction

Dates, reference numbers, amounts and the parties named in a document are pulled out as fields.

Renewal and expiry dates

Contract end dates, licence renewals and other deadlines are found inside the document and surfaced before they pass.

Duplicate detection

Repeat copies of the same document are caught on intake rather than accumulating across folders.

Text from scans

Scanned and photographed pages are read in Nepali and English so their contents are searchable.

What a shared drive cannot answer

Every one of these starts with a document that exists and can be opened. The gap is governance: which copy counts, who agreed to it, and who is allowed to see it.

Branch and head office hold different copies

The same agreement exists in a branch folder and in a head-office drive, and they have diverged. One governed record with an explicit status removes the question of which one counts.

  • Customer agreements
  • Branch registers
  • Head-office files

An approval has to be reconstructed

Someone asks who signed off a payment eighteen months ago and on what basis. The approval route, the people on it, and the documents attached at each stage are all recoverable from the record.

  • Approval records
  • Supporting invoices
  • Audit trails

A departing employee leaves files behind

Records added by one person sit in their personal space with no obvious owner once they leave. Governed ownership and administrator access to shared mailboxes mean the institution keeps its own documents.

  • Correspondence
  • Draft agreements
  • Shared mailboxes

A licence expires without warning

A renewal date sits inside a PDF nobody has opened since it was filed. Expiry and renewal dates are extracted from the document itself, so the deadline surfaces before it passes rather than after.

  • Licences
  • Contracts
  • Insurance policies

Technical Details

Intake
Direct upload, bulk import driven from a spreadsheet with progress shown as it runs, connected Google Drive, Dropbox and OneDrive, indexed email including shared organisation mailboxes, and a browser extension for saving and previewing in place.
Extraction
Dates, reference numbers, amounts and named parties are pulled from documents as they arrive. Scanned and photographed pages are read so their text is searchable.
Classification
Category, document type, owner, branch and status, with a reusable catalogue of people, vendors and assets so the same details are not retyped.
Lifecycle
Each document is marked draft, active or superseded. Duplicates are detected on intake rather than accumulating.
Permissions
Private to the person who added it until shared. Separate rights to view, edit and approve. Search results respect them, so a restricted record does not appear to someone without access.
Approvals
Routed through defined stages with named owners, deadlines and automatic reminders when something is overdue. Approvals can require several people to agree.
Audit
Every action on a record is kept in a tamper-evident history. Cases that were closed or rejected can be reopened without starting again.
Tenancy
Each organisation’s records are stored fully separated from every other organisation’s.
In progress
Retention rules applied by document type rather than by folder, and access review reporting for auditors. Being built, not available yet.

Frequently Asked Questions

Do we have to move everything before this is useful?+

No. Connecting Google Drive, Dropbox or OneDrive and indexing email makes existing material searchable where it already sits. Bulk import driven from a spreadsheet is there for when you want to bring an archive in properly, and it reports progress as it runs.

What stops someone seeing a document they should not?+

Documents are private to whoever added them until deliberately shared, and view, edit and approve are separate rights. Search enforces the same rules, so a restricted record will not surface to someone without access, not even as a title in a result list.

How does it know a contract is about to expire?+

Dates are extracted from the body of the document rather than typed in by hand, so contract end dates, licence renewals and similar deadlines are picked up from the file itself when it arrives. That means a deadline buried in a PDF nobody has reopened still surfaces.

Can an approval require more than one person?+

Yes. An approval stage can require several named people to agree before a case moves on, rather than accepting any one of them. Stages carry owners and deadlines, and overdue items generate reminders automatically.

Is this searchable in Nepali?+

Yes. Nepali and English are supported throughout, the interface follows the reader’s language, and scanned Devanagari documents are read so their contents are searchable alongside everything else.

What happens to a case that was closed by mistake?+

It can be reopened without starting again, and the reopening is itself recorded in the history. Cases can also be cancelled or deleted where that is the right outcome, with the same trail.

Can we set retention schedules by document type?+

Not yet. Retention rules applied by document type rather than by folder are in progress. Today retention is handled through document status and access control, so if a fixed statutory schedule is a hard requirement, raise it early and we will be straight about the timeline.