Capabilities/Documents & Records
A file is not a record.
A document holds content. A record holds content together with the context, the responsibility and the history that let it be trusted and accounted for. It has to preserve what happened, what changed, who was responsible, and what must remain available — through its whole operational life.
The record problem
Content is the easy part. Everything around it is the record.
Most systems can store a document and hand it back. That is not the hard problem. The hard problem is everything the document cannot say about itself: what it is, how it was classified, which version this is, who was responsible, what it relates to, who may see it, and how long it must be kept.
Stripped of that, a file is just content with a name. It cannot be trusted, controlled or accounted for. A record is the document together with the context, responsibility and history that make it answerable — and those have to be engineered into the system, not remembered by whoever happened to be there.
The record constitution
Content alone is not the record.
A record is not a document with extra fields bolted on. It is constituted from several things held around one identity: the content itself, the context that gives it meaning, the responsibility behind it, its relationships, who may act on it, and how long it endures — with a history that is added to, never rewritten. Read from the centre out.
The record
Current form
The record as it now stands.
Every change appends below — it does not overwrite.
Durable history
Every prior form and action, kept in order and never rewritten.
Content
The document itself — the substance the record carries.
Context
Classification and metadata: what this is, and how it is understood.
Version
Which form this is, and where it sits among the forms before it.
Responsibility
Who created, changed, reviewed and approved — attributed, not assumed.
Relationships
What this record relates to, and the supporting material it stands on.
Access
Who may see it and who may change it — decided elsewhere, enforced here.
Retention
How long the record must remain, when it may be archived, and the governed decision to dispose of it.
The layers are constant; what fills them follows from the record and the institution it belongs to. No classification scheme, retention rule or approval step is fixed here — each is set by the organization the system serves.
Standing
Not every document is a formal record.
The same system holds documents of very different standing. Treating them alike is how working drafts end up governed like evidence, and how records that must endure get cleared away with the clutter. The distinction is deliberate.
Working document
In progress and still changing. It has an owner but no authority yet; it is expected to change or be discarded.
Controlled document
Governed content others rely on — issued, versioned and superseded under control, so everyone works from the form in force.
Institutional record
Evidence of something that happened or was decided. It is fixed as of its moment, attributed, and kept for as long as it must be answered for.
Supporting evidence
Material a record stands on — the sources, attachments and related items that let it be tested later.
Published output
A record released beyond its origin under proper authority. What was issued stays recoverable exactly as issued, apart from the working material behind it.
Versioning
A record changes without losing what it was.
An institutional record is not frozen — it is corrected, re-issued and superseded as the work around it moves on. What it must never do is lose the form it held before. Each change produces a new current version and appends the previous one to the record’s history, with who made the change and why.
So the record always presents one current form, while every earlier form, every supporting item it once relied on, and every relationship it has held remain retrievable behind it. Nothing is quietly overwritten. The history is the part that lets the record be trusted years later.
Through its operational life
Controlled from capture to disposition.
A record is governed for as long as it exists, not only when it is created. The same identity carries these through its whole life.
Capture & creation
A record enters on a defined action, bound to one identity and one responsible owner from the first moment.
Classification & metadata
It is classified and described so it can be found, controlled and understood without opening it — on the institution’s own scheme.
Controlled access
Who may read and who may change a record is enforced on every action, from decisions taken in the identity layer rather than here.
Review & approval
Where a record must be reviewed or approved before it takes effect, that step is recorded against the person and the version it applied to.
Search & retrieval
A record can be found by what it is and what it relates to, and returned in the form the person is permitted to see.
Retention & archival
A record is kept for as long as it must remain answerable, then moved to archival keeping without losing its integrity.
Disposition governance
Removal is a governed decision, taken under authority and itself recorded — a record is never simply deleted.
Audit history
Every creation, change, access and decision is part of the record, so its life can be reconstructed long after the event.
Where this capability ends
Records hold the continuity. Other disciplines hold the rest.
Documents and records own one thing completely: information continuity — that what was recorded stays available, intact and accountable over time. The neighbouring decisions belong to other disciplines, and keeping them separate is what keeps each one clear.
Documents & Records owns information continuity
That the record stays available, intact and accountable through its whole life. This is the capability you are reading.
Workflow & Case Managementowns work progression
How work advances through its states. Records capture what that work produced; they do not drive it.
Identity & Accessowns authorization
Who may see and change a record. Documents enforce those decisions; they do not make them.
Reporting & Business Intelligenceowns interpretation
Turning records into governed operational visibility. Records supply the accountable source; reporting reads from it.
And the organizational structure a record belongs to — the units, roles and entities it is filed against — is read from the same organization model the rest of the system uses, so a record means the same thing wherever it appears.
Bring the records as they are. The system is built to keep them so.
Describe what your institution has to preserve, control and account for — and for how long. The right way to hold a record follows from that, not from a storage product.