Record retention and document requests for Sutherland public-sector premises

Records held only in a contractor's system are available for as long as the relationship lasts and the system exists. Neither is guaranteed. A contract ends, a business changes its software, a director retires, and a set of records that a public body may still be obliged to hold becomes difficult or impossible to retrieve. The client discovers this only when it needs something, which is usually years later.

The fix is unremarkable: the contractor provides records as they are produced and the client stores them in its own system. That single habit removes the dependency entirely. It also means the records are in the client's format and location rather than in a contractor's report layout that has to be interpreted before it can be filed, which is what causes them to sit unread in an inbox instead.

The scope and any reissued versions, since they establish what was agreed at each point in time. Periodic work completion records with dates, which answer maintenance questions long after the fact. Inspection findings and their closure. Incident and hazard reports. Insurance certificates for each period, including superseded ones. Attendance records where the premises warrants them. Retention periods should follow the organisation's own schedule rather than a contractor's preference.

Superseded documents deserve a specific mention because the instinct is to discard them. An insurance certificate that expired three years ago is evidence of cover during that period, which is exactly what a question about an incident from three years ago requires. Keeping superseded versions in a separate location, clearly marked, costs nothing and occasionally matters a great deal.

Requests for records arrive with deadlines and specific parameters, and the organisations that answer them well are the ones whose records were already organised. That means consistent formats, dates on everything, records stored by site rather than by month, and a naming convention that lets someone find a document without knowing who produced it. Storing the current version alongside superseded ones, clearly labelled, also prevents the common error of producing an outdated document in response to a request.

It also means avoiding records that raise more questions than they answer. A checklist with every box ticked for four years is not reassuring under scrutiny; it reads as a form rather than a record. Honest documentation, including exceptions and their closure, is both more useful operationally and considerably more credible when someone external examines it. Clean Best records findings rather than confirmations for that reason.