A museum does not merely store information about objects. It runs on that information.
Identity.
Location.
Ownership.
Condition.
Rights.
Use.
Authority.
History.
Documentation planning is how the museum decides which facts, decisions and relationships must remain connected so the institution can still understand its collection years later.
Collections Trust treats documentation planning as the management layer that ensures policies, procedures, systems and backlogs remain coherent across the museum. The point is not to create more forms. It is to make sure the right information is captured once, connected correctly, updated when circumstances change and retrievable when another procedure needs it.
This article owns the documentation architecture. The Catalogue Is Never Finished owns descriptive records. The Museum Has to Know Where Everything Is owns location and movement control. Here the question is how those and many other records become one operating system instead of separate islands.
Quick Read: The Documentation-Planning Mechanism
MISSION + COLLECTION POLICY → INFORMATION REQUIREMENTS → IDENTIFIERS → PROCEDURES → RESPONSIBILITIES → DATA STANDARDS → SYSTEM DESIGN → BACKLOG PRIORITIES → QUALITY CONTROL → AUDIT TRAIL → USER ACCESS → REVIEW → MIGRATION → CONTINUITY.
Documentation Begins With Decisions, Not Software
A new database does not fix unclear policy.
If staff disagree about what counts as an acquisition, a location update or a rights restriction, software merely stores the disagreement faster.
Every Object Needs a Stable Identity
Names change.
Attributions change.
Descriptions change.
A stable identifier allows the museum to update knowledge without losing the continuity of the thing being described.
Identifiers Need Type Boundaries
Entry number.
Accession number.
Loan number.
Image number.
Conservation treatment number.
They should not be confused simply because they are all numbers.
One Fact Should Not Have Five Uncontrolled Versions
Object title in collections database.
Different title in spreadsheet.
Different title on website.
Different title in exhibition checklist.
Documentation planning identifies which system is authoritative for which field and how derivatives stay synchronised.
Authority Files Reduce Vocabulary Drift
“Singapore.”
“Republic of Singapore.”
“SG.”
Controlled names and identifiers help systems understand when different labels refer to the same entity.
Provenance Needs Claim-Level Evidence
Owner from 1932 to 1941.
According to which source?
Strong documentation records not only the claim but also who made it, what supports it and how certain it is.
Current Location Is Operational Data
A beautiful catalogue record is not enough if staff cannot find the object.
Documentation planning separates scholarly richness from minimum controls needed for day-to-day accountability.
Backlogs Need Risk-Based Priorities
Ten thousand uncatalogued objects.
Where to start?
High-value objects with weak location data may outrank fully located objects lacking detailed interpretation.
Documentation backlog is a risk portfolio, not just a queue.
Minimum Documentation Creates a Floor
Identity.
Status.
Location.
Ownership or custody.
Enough information should exist that the museum can account for an object even before deep research is complete.
Documentation Has to Record Change
Old attribution replaced.
Object renamed.
Location moved.
Rights expired.
A system that only stores the latest state can erase institutional history.
Audit Trails Preserve Decision Memory
Who changed the record?
When?
Why?
Audit trails make corrections accountable without pretending records never evolve.
Data Quality Needs Rules
Required fields.
Controlled vocabularies.
Date formats.
Duplicate detection.
Authority review.
Without agreed rules, quality becomes person-dependent.
Data Migration Is a Museum Move
Moving records between systems is like moving objects between buildings: relationships can be lost, identifiers can break and assumptions can change.
Migrations need mapping, validation, testing and receipts.
A New System Should Not Destroy Old Meaning
Legacy field combines maker and attribution qualifier.
New system separates them.
Migration must preserve semantic distinctions rather than flattening data into convenience.
Documentation Permissions Matter
Who may edit provenance?
Who may change current location?
Who may view security notes?
Who may publish sensitive community information?
Access should match role and risk.
Public Data Is a View, Not the Whole Record
The website may show title, maker and image while suppressing exact storage location, donor contact details or sensitive notes.
Documentation planning should define publication layers rather than copying the internal database indiscriminately.
Documentation Has to Survive Staff Turnover
If one registrar’s memory is required to understand the database, the system is incomplete.
Policies, field definitions, workflows and exception rules should be documented independently of individuals.
AI Makes Provenance of Data More Important, Not Less
AI can propose tags, transcriptions, links and summaries. Those outputs should carry source and confidence so machine-generated suggestions do not silently become museum-authored fact.
Documentation Planning Is Also Continuity Planning
What if the vendor disappears?
Can data be exported?
Are identifiers portable?
Are backups tested?
A museum should not outsource its institutional memory without an exit route.
Documentation Failure Tests
| Failure | What Goes Wrong | Repair Question |
|---|---|---|
| Software = documentation strategy | Unclear policy is automated | Which decisions must the system support? |
| Latest value = full history | Previous states disappear | Can change be reconstructed? |
| More fields = better records | Backlog grows without control | What is the minimum operational floor? |
| Spreadsheet = harmless side system | Competing truths emerge | Which source is authoritative? |
| AI suggestion = museum fact | Provenance of claims is lost | Who or what generated this field? |
| Vendor = continuity | Institutional memory becomes trapped | Can the museum export and reconstruct its data? |
Current Evidence and Professional Anchors
- Collections Trust — Documentation Planning for managing documentation systems, policies and backlogs.
- Collections Trust — Documentation Planning: Spectrum Standard for minimum requirements, responsibility and review.
Where This Fits in the Museum Series
How Museums Work remains the canonical root. Documentation Is an Operating System, Not a Filing Cabinet owns the architecture that connects catalogue, custody, location, rights, condition, use and decision history into one coherent institutional memory.
Final Thought
A museum can survive a missing label. It cannot safely survive a documentation system that no longer knows which facts are authoritative, which decisions were made, or how one object’s history connects to the institution responsible for it.