Records Have Neighbors
The archival bond preserves the relationship between a record and the records immediately before and after it.
A key document can look complete when it is opened alone. It has a title, a date, perhaps an author and a clear conclusion, yet a record rarely begins at its first visible word; something came before it and something followed. Remove that sequence and the document may remain perfectly readable while losing part of what it can prove.
Information governance calls this relation the archival bond. It is the relationship linking each record to the previous and subsequent one. The definition is spare, but it directs a practical act: trace the record immediately before and after an important document, then preserve the sequence in classification or metadata.
I am not proposing that every collection become an archaeological dig. The point is to avoid treating a record as an isolated object when its meaning depends on the work that led to it and the action that followed.
A document belongs to a sequence
The record before a key document may establish the question, request, condition, or decision that made the later document necessary. The record after it may show how its contents were received, applied, amended, or superseded. Neither neighboring record automatically settles the meaning of the central document. Together, they make the relation available for inspection.
This is particularly important when a document carries apparent authority. A final-looking statement may have been a response to a narrow earlier request. An instruction may have been followed by a correction. A decision may have been overtaken by later conditions. Reading the central record alone can erase those relations without anyone intending to erase them.
The archival bond offers a way to retain the route. It keeps the record connected to an order of actions rather than reducing it to a detached message.
Classification can preserve the route
Classification and metadata can preserve the relationships that let a later person locate a record in its sequence. They are part of the bond, not labels attached after the fact. If the records immediately before and after a key document remain connected, a reader can trace the chain without relying on memory or an accidental search result.
This is a small intervention. It does not require an account of every possible relation a document might have. It begins with the direct neighbors. That limit makes it practical and protects the integrity of the record order.
The work also helps distinguish sequence from subject similarity. Two records may share a topic while belonging to different actions. A neighboring record may concern a different topic in ordinary language while being essential to the central document’s purpose. The archival bond follows the record relationship, not a broad category of words.
Context is a use condition
Preserving sequence changes how a record can be used. A later reader has more than a conclusion. They can see the condition that produced it and what happened after. That context does not tell the reader what to think. It gives them a firmer basis for deciding what the record can bear.
The same principle applies when information moves through systems. A record retrieved quickly may be useful, but speed does not remove the need for context. A classification that retains the archival bond can make a fast retrieval more responsible because the reader has a route to the adjacent evidence.
Start with one key document
The exercise is deliberately narrow. Choose a key document. Identify the record immediately before it and the one immediately after it. Preserve that order in the record’s classification or metadata.
The result is a small safeguard against treating one document as if it were the whole event. Keep its immediate neighbors close enough for the next reader to see the request that produced it and the action, correction, or supersession that followed; the document may still speak for itself, but now we know who was standing beside it.
