Blog
What we have learned building dossiers, processes, and the rules that keep them complete.
At volume, the cost of a mistake stops being the document and becomes the repetition. What it takes to scan thousands of files, deliver them to an external system without duplicating anything, and prove months later what was delivered.
Choosing document management software in 2026 is no longer about where files are kept — it is about how much control you want over the processes that depend on them. A buyer's guide with eight criteria, a table and the questions to ask before you sign.
Document AI promises to read files and fill in fields. For an SME the risk is not that the AI gets something wrong; it is that nobody can say where a value came from. Six design rules for speed without losing control.
A document checklist is not a list beside a folder: it is a rule that stops a process from moving on without the right documents in the right state. Per-document statuses, minimum and maximum files, and what a refused submission has to say.
Certificates, insurance and licences have deadlines, and a system that only stores the file discovers expiry too late. What a renewal campaign has to do, why a reminder is not enough, what exists in DOK Genius today and what is on the roadmap.
Receiving files through several channels is the easy part. The hard part is that every arrival ends in the right dossier, as the right document, with nobody retyping data — and that the system stops and calls a person when the match is not clear.
Not every document in a dossier is equally sensitive. Document-level confidentiality lets a person follow the case without seeing every file — and never widens access to anyone who could not open the dossier.
A well-designed document process answers seven questions before a folder exists: which decision, which documents, which data, who decides, what a person reviews, which system receives the result and what evidence remains. How each answer becomes a rule.
When documents sit in folders, dates in a spreadsheet and decisions in email threads, every audit is a reconstruction. What compliance has to prove, and how a governed dossier keeps documents, states, decisions and evidence in one place.
A digital employee dossier knows what is missing, what has lapsed and who may see each document. How to run onboarding, contracts, certificates and training as governed dossiers — what exists today and what is on the roadmap.
A claim arrives in pieces: claim form, policy, photographs, estimate, report. How an insurance process becomes a governed dossier, with expected documents that carry their own status, AI reading, human review, an auditable decision and hand-over to the claims system.
SharePoint is strong at storing, sharing and co-editing documents. When a folder starts to stand for a regulated process — required documents, decisions, confidentiality and evidence — the problem changes. An honest comparison, and when to use each.
An enterprise AI assistant is only as safe as its sources. A prompt asking the model to respect permissions is not a security mechanism: the filter belongs in retrieval, before the model reads anything. What retrieval must prove, and a checklist for evaluating an enterprise RAG.
AI reads, classifies and extracts; a person decides where the risk calls for judgement. What human-in-the-loop means in document processes, why it is neither reviewing everything nor blind automation, and how Quality Review closes the decisions AI should not close on its own.
Finishing a document process is not enough; you have to prove how the decision was reached. What an evidence pack must answer, why proof falls apart when it lives in several tools, and what a governed dossier records by itself.
Every office multifunction printer already has scan to e-mail. Point that button at the right inbox and what comes off the glass stops being an ownerless PDF: it becomes a dossier opened in the right process.
A governed digital dossier is a case of work that knows which documents it expects, what state each one is in, who may open it and what is still missing before it can move on. The difference from a folder, with examples, a comparison table and a FAQ.
In a pension fund, the document that lapses quietly costs more than the document that never arrived. Why validity belongs to the case rather than to whoever is on the phone.
An accident is reported by email, with photos attached. Nobody creates a case, nobody picks a process, nobody retypes anything into the policy system. This is what a complete automation looks like when every step of it is a control rather than a script.
A document process is controlled when four things are true: the rules are enforced by the system, incomplete work cannot advance, decisions are recorded with authority, and the process ends by carrying out the operation. Everything else is a convention people follow until they are busy.
The usual way to collect documents from a customer is an email listing what to send. The better way is a link to the dossier itself — already prepared, already organised, with a place for each thing and a field for each answer.
Document governance is the practice of making an organisation's documents answer four questions — which are required, what state each is in, who may open it, and what has happened to it. Storage answers none of them.
An assistant that reads your documents will answer from whatever it can reach. Three things decide whether that answer is right — what it retrieved, whether the reader was allowed to see it, and whether the document was still current.
In most organisations a case is complete when somebody says so. That is a judgement, and judgements do not scale, do not audit and do not survive the person who made them. Completeness should be a property the system evaluates.
Collecting approvals is easy. What makes them mean something is that each approver had authority, took their turn in order, and decided against a case that could not change underneath them afterwards.
A folder holds whatever you put in it. A dossier knows what it is missing — and that single difference is where the work goes.
An assistant can only answer from documents somebody made findable, current and complete. That work has a name, and it is not artificial intelligence.
Get started
Open a free account, or tell us what your files look like today.
