Rig Records: What to Keep, How Long, and Why It Matters in an Audit

Every rig generates paper the way it generates cuttings, and most of it is stacked in boxes that nobody can search. Then an audit happens, or a claim, or a regulator asks for three years of training records, and the question becomes very simple: can you find the record, and can you prove when it was made? The rigs that pass audits are not the ones with the most records. They are the ones that know exactly what they are required to keep and how long, and that keep those records where a stranger can find them.

The retention periods that actually matter

The core set is shorter than most operators fear, and knowing it turns a scramble into a schedule. The OSHA 300 log, the annual summary, and the incident reports: five years, per 1904.33. Training records: the general rule is that training documentation is kept for the duration of the employment plus the term required by the specific standard, which is why the operator has to know which standard applies to which record. Hazard communication data: the SDS library lives at the location for as long as the chemical is there, and the exposure records behind it have their own long tails. Medical records, including audiograms, respirator fit tests, and exposure monitoring, are the long-horizon records, with retention running for the duration of employment plus thirty years under the medical records access rule, which is why they belong in a system that outlives a filing cabinet.

Well records are a different species

Drilling and well records answer a different question: what happened downhole, and who was accountable? The BOP test record, the cement job report, the casing tally, the daily drilling report, the kick records, the H2S training and drill logs, the wellhead inspection records on this site. Regulators on both the federal and state side set retention for these, and the periods are long because the well outlives the rig by decades. The rule of thumb that covers most of it: if the record describes work done to the well, the well's life is the retention period, and the operator's lease file is where it belongs, not the contractor's warehouse.

The failure mode is not missing records. It is unlabeled records: a box of tour reports with no well name, a stack of training certificates with no dates, an SDS binder that stopped being updated when the chemical supplier changed. The auditor's checklist on this site looks at the same things every time: can the record be found, is it legible, and does its date make sense for the work described.

The system that makes retention survivable

The fix is a records register: a list of every record type the operation generates, who owns it, where it lives, and when it can be destroyed. That register is what turns retention from folklore into process. Then the mechanics: a scan-on-creation habit at the location, so the paper is digitized while the crew that signed it is still on site; a naming convention that puts the well, the date, and the record type in the filename; and a review trigger, so the destruction dates are real events and not a legal risk in waiting. The field service software buyer's guide on this site covers the tool side: the right system makes the record the byproduct of the workflow, not an extra chore, so the tour report creates the record at the same moment it is signed.

And the incident reporting records on this site deserve their own shelf: the five-year log, the retained forms, and the analysis behind them are the documents a plaintiff's attorney reads first, and they are the ones that have to be complete, consistent, and unedited.

If your records live in boxes labeled "old files" and nobody can name the retention period for an OSHA 300 log, book a working session with the OpsFlo operations team. Book a call here to see a records register, retention dates, and digitized records built into the workflow that already produces them.