Policies, precedents and the reasoning behind past decisions, held somewhere they survive staff turnover.
HOW IT WORKS
When the people who made a decision leave, the reasoning usually goes with them.
The policy survives in a folder somewhere. What is lost is why it was written, what it replaced, and which cases it was applied to. The same questions then get answered from scratch every few years, sometimes differently.
Policies, circulars, precedents and the correspondence around them are indexed in one place, including email, so a decision and the discussion that produced it sit together.
Every document carries a status — draft, active, or superseded — so nobody has to guess whether the copy they opened is the one still in force.
Ask in plain language for a summary, a translation, a comparison between two versions, or a specific detail, and get an answer that cites the document and the line it came from.
Actions are recorded in a tamper-evident history, and access stays governed as people join, move between roles, and leave.
WHY IT WORKS
Most institutions already have somewhere knowledge is supposed to live. The problem is rarely storage — it is that nothing tells a reader whether what they found is still true, and nothing survives the person who wrote it.
Holds everything and vouches for nothing. Three copies of a policy in three folders, no indication which is in force, and permissions set by whoever created the folder years ago.
Accurate the week it was written. Nobody owns a page after the person who created it moves on, and there is no mechanism that surfaces the fact it has gone stale.
Where the actual reasoning lives — and it is private to whoever was on the thread. When they leave, the decision remains but the argument behind it does not.
None of these are storage problems. In every case the document existed and could be produced. What was missing was the reasoning, the currency, or the trail.
One person understood why an exception was granted in 2019 and how the process has been applied since. Holding the decision, its reasoning and its correspondence together means their successor inherits the file rather than the folklore.
Three versions of the same circular exist and the differences matter. An explicit status on each document, plus the ability to compare two versions directly, settles it without a call to head office.
A recurring query gets researched from scratch because last time’s answer was never written down anywhere findable. Asking against the document set returns the answer with the source cited, so it can be reused rather than rebuilt.
Producing the approval is straightforward; producing the reasoning and the sequence of events usually is not. A tamper-evident history plus the correspondence indexed against the record makes the chain reconstructable.
A folder structure tells you where a file sits, not whether it is still in force. Documents here carry an explicit status, the correspondence that produced them is indexed alongside them, and access is governed centrally rather than by whoever created the folder. Good folders are a filing system; this is a record of what the institution currently holds to be true.
A wiki depends on someone remembering to update it. The problem it does not solve is decay — a page that was accurate three years ago looks identical to one written yesterday. Status, version comparison and a citation back to the source document are what separate a maintained record from a stale one.
No. Connected Google Drive, Dropbox and OneDrive folders and indexed email make existing material searchable where it already lives. Bulk upload driven from a spreadsheet is available when you do want to bring an archive in properly.
No. A document stays private to whoever added it until it is deliberately shared, permissions decide who can see, edit and approve, and search results respect those permissions — a restricted record does not appear to someone without access, even as a title.
Every answer cites the document and the line it came from, so the claim can be checked against the source rather than taken on trust. Treat it as a fast way to find and summarise the authoritative document, not as a replacement for reading it when the decision matters.
Retention rules applied by document type rather than by folder are in progress and not available yet. Today, retention is managed through document status and access control; if a fixed statutory schedule is a hard requirement for you, say so early and we will be straight about the timeline.