A contractor can have a clean safety record on the rig and still lose a bid because they could not produce the paperwork to prove it. It happens across the Permian Basin, the Eagle Ford, and every play where operators run formal contractor qualification programs. The contractor with the stronger documentation package often wins the contract, not the one with the lower incident rate.
Knowing which safety records operators require is the difference between walking into a prequalification review ready and assembling documents under a two-day deadline. Safety performance has improved across much of the industry. The ability to prove that performance on short notice, with the right fields filled in, still separates contractors who win work from those who get passed over.
This guide covers three things: which record categories operators request, what each record must contain to pass review, and how long to keep each record type. For file formats, signatures, and metadata requirements, see our guide to the digital safety documentation operators expect.
The contractor documentation stack operators ask for
Major operators do not just want your TRIR. They want the documentation behind the number. When a company like Chevron or ConocoPhillips runs contractor prequalification, they are checking whether your safety program is real and documented, or whether it exists only on paper. Six record categories show up consistently.
OSHA 300/300A logs
The last three years at minimum. Operators cross-check these against your TRIR, DART, and EMR submissions, so all of them need to agree.
Incident logs
Full narrative detail, not just summary statistics. Each entry needs a root cause, the corrective action taken, and an OSHA recordability classification.
Job Safety Analyses
Completed in the field for specific tasks. Reviewers flag generic templates copied across jobs as evidence crews are not doing real hazard analysis.
Hot work and confined space permits
Pre-job checklists, responsible-party signatures, fire watch documentation, and closeout. Dated, site-specific, signed by the crew that did the work.
Safety audit reports
Internal or third-party. Each report needs a date, the auditor's name, findings with severity ratings, and an assigned owner for every finding.
Corrective action records
Records that show closure, not just identification. Close-out dates, the specific action taken, and verification the hazard was resolved.
TRIR and DART scores are the entry point, but operators use them as a filter, not a final answer. Experienced reviewers treat a zero-incident rate paired with sparse documentation as a recordkeeping problem rather than a genuinely clean history. The documentation behind your metrics is what gives those metrics credibility. If you want to check your own numbers before a review, run them through our TRIR calculator.
Founder-led setup
See how your current safety forms become operator-ready records.
Bring a JSA, permit, inspection form, or training matrix. We will map it to BasinCheck and show the smallest rollout that gets one crew generating usable documentation.
What each record must contain to pass review
Generic or incomplete records get rejected. An incident log that lists a date and the word "laceration" does not satisfy an operator reviewer. A JSA that looks identical across twenty different jobs signals that your crew is checking a box, not doing a real hazard analysis. Here is what each record type needs.
Incident logs
Every incident entry needs the date, location, names of the personnel involved, and a clear narrative of what happened. The narrative must include a root cause determination and the specific corrective action taken, not a general note that the issue was "addressed." Each entry also needs an OSHA recordability classification: first aid, recordable, or lost time.
Operators routinely cross-reference your incident log against your submitted OSHA 300 data. Inconsistencies between the two can trigger reviewer concern or disqualification, depending on client policy. If your 300 log needs work first, start with our OSHA 300 log template.
JSAs and permit records
A JSA that survives operator review names the specific job task, lists the hazards for each step, and documents the exact controls applied. Boilerplate language copied across jobs is easy to spot and routinely flagged. Operators and ISNetworld auditors look for site-specific detail: the work location, crew sign-in with names and signatures, supervisor sign-off, and a stop-work authority briefing confirmation. If your JSAs need that structure, our JSA builder walks through it step by step.
Hot work permits need a pre-job checklist, the responsible party's signature, and fire watch documentation. Both permits and JSAs must be dated, site-specific, and signed by the crew who actually performed the work.
Audit reports and corrective action closure
Internal audit reports need a date, the auditor's name, a findings list with severity ratings, and an assigned owner for each finding. The corrective action record tied to each finding must show the close-out date, the specific action taken, and verification that the hazard was resolved. Revised procedures, training sign-in sheets, and photographs of corrected conditions all count as closure evidence.
Timely corrective action closeout, often within weeks, is a requirement of many clients on ISNetworld. Close-out discipline matters as much as the initial documentation. A corrective action tracker with due dates and owners keeps items from sitting open until an auditor finds them.
ISNetworld, Veriforce, and where contractors get disqualified
Most small contractors know they need to be registered on ISNetworld or Veriforce to work with major operators. Fewer understand how these platforms score them, or why their grade falls short when they believe their documentation is complete. The grading mechanics matter: a score below the operator's threshold means you do not get considered, regardless of your actual safety record. For platform options that handle the uploads, see our guide to the best software for ISNetworld compliance.
How ISNetworld grades your safety documentation
ISNetworld grades contractors on a combination of safety statistics, written safety program quality, and HSE questionnaire responses. The RAVS process reviews your submitted programs and verifies that they meet OSHA standards. Missing programs, unverified EMR data, or gaps in OSHA 300 submissions all pull your grade down. Many oil and gas clients require a minimum "B" grade, and those with higher-risk work classifications set tighter thresholds. The three-year average matters here: one bad year follows your score for three years.
What the Veriforce questionnaire asks for
Veriforce focuses heavily on written safety programs, training documentation, and incident history verification. Contractors must upload proof of programs, not simply confirm they exist. Annual requalification means your documentation has to stay current. A program uploaded two years ago will not satisfy a requalification cycle if the content is outdated or the OSHA log data has not been updated.
The documentation gaps that kill contractor scores
Three patterns show up repeatedly across contractor disqualifications:
- The OSHA 300A annual summary was never submitted, or was submitted with missing entries
- Corrective action records show a hazard was identified but never documented as closed
- The JSAs on file are clearly generic forms with no site-specific detail; auditors flag these immediately as evidence that crews are not completing them in the field
Any one of these gaps can drop your grade below an operator's threshold.
How long to keep each record type
Retention requirements vary by record category. Keeping records too briefly leaves you exposed during audits. Keeping the wrong records in disorganized systems makes retrieval under deadline nearly impossible.
OSHA 300 log, 300A summary, Form 301
Five years following the end of the calendar year they cover (29 CFR 1904.33).
Exposure records (chemical, noise, silica)
Duration of employment plus 30 years.
Medical surveillance records
Duration of employment plus 30 years, same as exposure records.
Operator training records
Show current certification. Forklift certifications must be renewed at least every three years; many operators ask for the full training history of the assigned crew.
JSAs and permits
Operators commonly request 12 to 24 months of records for active projects.
Corrective action records
All open items regardless of age. Closed items typically retained for two to three years.
The five-year rule for OSHA 300 logs, 300A summaries, and Form 301 reports is the federal mandate under 29 CFR 1904.33. See the official OSHA recordkeeping guidance for full details. For operator training records such as forklift certifications, the requirement is to show current certification, renewed at least every three years under OSHA's powered industrial truck rules. Many operators ask to see the full training history for the crew assigned to their work. If training is not documented, an auditor treats it as if it never happened, and the burden of proof sits with the employer.
Operators add their own requirements on top of the federal minimums. Most prequalification programs want three years of OSHA 300 data, and higher-risk classifications often push that to five. For active projects, JSAs and permit records commonly need to go back 12 to 24 months. Corrective actions follow a different logic: every open item regardless of age, plus closed items for two to three years. Your five-year OSHA retention and your ongoing corrective action tracking need to run in parallel, in a system that makes both retrievable on short notice.
Building a system that keeps these records retrievable
Understanding what is required is step one. Building a system that generates, stores, and retrieves those records without adding workload for your crew is the part most contractors get wrong. The documentation stack above is only an asset if you can produce it when a prequalification request arrives.
Why paper records fail operator prequalification
Paper logs get lost, get rained on, and are reliably incomplete when someone needs to pull three years of audit history under a two-day deadline. Operators increasingly request digital copies or direct uploads to prequalification platforms. Paper does not transfer cleanly into those systems, and it signals a disorganized safety program before the reviewer reads a single entry. Field crews completing JSAs on paper often skip fields or abbreviate details that operators specifically look for. The form was never designed to be fast in the field.
How BasinCheck handles the documentation burden
BasinCheck is built around the workflows oilfield crews actually use: a JSA builder designed for rig operations, a hot work permit workflow with pass/fail checklists and photo evidence, incident reporting with automatic OSHA classification suggestions, and a corrective action tracker with due date alerts. Every completed record is timestamped, signed, and stored with the field data that makes it credible when a reviewer looks at it. Nothing gets filled in back at the office after the fact.
OSHA 300/300A exports generate in minutes, formatted for upload to ISNetworld or delivery to a prequalification auditor. The platform works offline, so crews on remote well pads complete records in the field and sync when connectivity returns. If you are weighing a general file system against purpose-built software, see BasinCheck vs SharePoint for safety documentation.
Pricing is flat and company-based, with tiers starting at $149/month and unlimited users, so there is no per-seat penalty as your crew grows and no enterprise IT project to deploy it (see current pricing). For context on how BasinCheck compares to other options, see the best oil & gas safety software ranked.
Your documentation is your proof of performance
A strong safety culture without the records to back it up does not get you on the approved contractor list. The checklist is clear: OSHA 300 logs retained for five years, incident logs with full narratives and documented closure, site-specific JSAs with crew signatures, hot work permits with pre-job checklists and fire watch documentation, audit reports with severity ratings and owners, and corrective action records that show close-out. Every record needs the right fields, the right signatures, and a retention period managed somewhere more durable than a filing cabinet in a portable office.
Digital safety documentation operators expect
The formats, signatures, and metadata your records need before an operator or portal reviews them.
Operator audit guide: Chevron & ConocoPhillips
How major operator audits run and what reviewers look for on site.
Prequalification toolkit
Templates and checklists to assemble a complete prequalification package.
Founder-led setup
See how your current safety forms become operator-ready records.
Bring a JSA, permit, inspection form, or training matrix. We will map it to BasinCheck and show the smallest rollout that gets one crew generating usable documentation.
Safety records operators require: FAQ
Common questions from contractors preparing records for operator prequalification.