Availability Is a Governance Principle
Information governance should protect sensitive records without obstructing retrieval of records that do not need special protection.

Governance is easiest to see at the point where access is denied: a record requires special protection, a barrier is placed around it, and the system makes that condition visible. That work matters, but I think it becomes incomplete when the same barriers spread—through caution, habit, or simple convenience—to records that do not require them.
Availability is a direct information-governance principle: governance should not impede retrieval for records without any degree of special protection. The principle does not set availability against protection. It requires a system to distinguish the records that need protection from the records that do not.
This distinction can be tested in a small, practical way. Remove one unnecessary retrieval barrier for records outside the protected category, then measure whether people can find those records more easily. The purpose is proportionate access, which is less exciting than unrestricted access and considerably more useful.
Protection needs a defined object
Special protection has meaning only when the system can identify what is being protected and why. A barrier that applies without that distinction turns governance into general friction. People must navigate it even when the record carries no condition that justifies the delay.
The effect is easy to underestimate because a single obstacle may appear minor, but repeated obstacles change whether people search, whether they give up, and whether they rely on informal routes instead of the system intended to hold the record. Governance has then impeded retrieval without adding relevant protection, an outcome that manages to be both strict and careless.
Availability asks the system to preserve the boundary. Protected records should remain protected. Ordinary records should not inherit the same treatment merely because the system has one convenient access pattern.
Measure the change in retrieval
The suggested intervention does not assume that removing a barrier will improve every use. It asks for a measure. Can people find the records more readily after the change? Does the route become shorter or clearer? Do the records remain available to the people whose work requires them?
Measurement keeps the principle attached to experience rather than preference. A team can compare the earlier and later retrieval path, then see whether the barrier was actually preventing access. If the change does not help, the record gives the team a reason to examine the condition more closely.
The measure can remain plain. Choose a record that an entitled person should be able to retrieve. Note the route, the decisions required, and the point where progress stops. Remove one barrier that serves no protective purpose. Then repeat the attempt with the same kind of user and the same kind of record.
The result may expose a barrier that is not labeled as security. A record may be technically open and practically absent because its description does not support discovery, its location is known only to one group, or its access route demands knowledge that the intended user cannot reasonably possess. Availability concerns the full retrieval condition, including everything before the final permission check.
Entitlement and ease are different questions
The principle does not say that everyone should retrieve everything. It says that governance should not obstruct a record when no special protection applies. A person may still need a legitimate relationship to the collection or the work. Once that relationship exists, ordinary records should not behave like secrets by accident.
This distinction keeps the intervention bounded. First determine whether special protection applies; if it does, preserve the necessary control and improve the authorized route within it. If it does not, ask what the barrier contributes. A control without a protected object is friction in institutional clothing, and the clothing does not make it governance.
Availability is part of responsible governance
Information governance is not fulfilled when a system can deny access. It also has to preserve the availability of information that people are entitled to retrieve. A protected drawer and an ordinary drawer should not become indistinguishable because the system prefers one lock.
The practical question is modest: which retrieval barriers exist for records without special protection, and what happens when one is removed? Ask it of one record, watch an entitled person try the route again, and keep the evidence. That is enough to make availability a working governance principle instead of the pleasant half of an access policy.
