Construction safety documentation: what a subcontractor actually has to keep, and who asks for it

First, the disclaimer, and we mean it: this is not legal or regulatory advice. We are not the authority on what any rule requires. Standards come from regulators, your state, your insurer and your own contracts, and the specifics change by state and by scope — your safety consultant and your carrier are who to ask what applies to you.

What we can write about is the part nobody writes about: the operational side. Which documents a commercial specialty sub gets asked for, by whom, when, and what makes the asking painful. That part is an office problem, and it is remarkably consistent from one sub to the next.

The real problem is not authorship. It is retrieval and expiry.

If you are reading this, you probably already have a written program. Somebody paid a consultant for it years ago and it is a PDF on a shared drive. That is not where the pain is.

The pain is a prequal packet with a Friday deadline asking for numbers you have to go find. It is a superintendent stopping a crew because one person cannot produce a current card and the office cannot prove in five minutes that the card exists. It is somebody asking, six months later, what the crew was told about a hazard and who was in the huddle.

Every one of those is a retrieval problem with a deadline, and none of them is solved by writing a better program. They are solved by knowing where things are and when they expire.

Four audiences, four different asks

This is the framing that makes the whole subject manageable. The paperwork is not one pile. It is four piles, and they barely overlap.

1. The GC’s prequal, before you are on the job

This one is a scoring exercise, and it happens before you have a contract. It typically wants:

• Your experience modification rate, usually three years of it, with the year against each figure. Below 1.0 is the figure many prequals look for, and some GCs’ insurance programs set a hard ceiling.
• Recordable incident rates by year — commonly a total recordable rate and a days-away/restricted/transfer rate.
• The annual summary of work-related injuries and illnesses. Which year varies; keep the figure and its year together, because a rate without its year is useless to whoever is scoring you.
• Your written safety program, as a document they keep on file.
• Certificates of insurance with the limits their contract requires, the right endorsements, naming the right entities.
• Who your competent person is for the scopes that call for one.

Two practical notes. The numbers do not come from your safety file — they come from your carrier, your payroll and your own records, so someone has to reconcile them once a year rather than once per prequal. And if you work for eight GCs you will be asked for the same facts eight times in eight shapes. The work is not producing the facts. It is producing them again, correctly, in a hurry.

2. The jobsite, every week you are on it

This is the GC’s site requirements plus your own program, per job. The usual list:

• Toolbox talks, commonly weekly on commercial sites, with the topic, the date and who was there. The attendance record is the part that matters and the part that gets lost.
• A pre-task or hazard analysis for the work being done, often per scope, refreshed when the work changes.
• Site-specific orientation for everyone you bring, including anyone you hire under you.
• Documented inspections of your own work area, at whatever interval your program commits to, plus equipment and ladder or scaffold checks where your scope involves them.
• Current certifications for the people doing work that requires them.

A superintendent will ask for one of these at the worst possible moment, and the only answer that works is one you can produce from a phone.

3. Your insurer, your auditor and your own program

A different need: continuity and proof over time. Training records that outlast the person. Incident records kept for the period your carrier and your program require. Evidence that findings actually got closed — a corrective action with a date, not a note that it got mentioned.

This is the audience that finds the most common gap. Plenty of subs document the finding and nothing documents the fix. An inspection with eleven failures and no record of any being corrected can hurt more than it helps, because now there is a dated record that you knew — an argument for closing findings, not for skipping inspections.

4. A dispute, years later

Back charges, a delay claim, an injury, a warranty argument. What matters here is the ordinary dated record: who was on site, what the conditions were, what was discussed, what got flagged and what was done about it.

So the highest-leverage safety habit is the unglamorous one — the daily log, filled in every day, including the days nothing happened. The record that defends a delay position is the same record that shows a crew was briefed. The field-level version of that is what a foreman’s daily log needs to contain.

The four failures that actually bite

The same four things go wrong, and none of them is a missing document.

The expiry nobody watched. A certification lapsed three weeks ago and nobody knew, because a scan in a folder has no opinion about today’s date. The most common and the most avoidable.

The attendance list that is a photo of a sign-in sheet. It is on somebody’s phone, not searchable, not attached to a job. When you need to prove a specific person was told a specific thing on a specific date, you are scrolling a camera roll.

The COI that expired mid-job. Yours, or worse, one belonging to a sub you hired. The GC’s compliance system can find out before you do, and it can hold a payment.

The loop that was never closed. A failed inspection item with no corrective action and no date.

All four are date problems. Which is why the fix is a list with dates that something checks for you, not a better-organized folder.

A system a 15-person office can actually run

If you build nothing else, build these five.

One roster, with every certification attached to a person and an expiry date. Not a folder of scans — a list that can tell you what expires in the next thirty days. Subs you hire belong on the same list, by company, with their COI expiry and whatever prequal status you gave them.

Toolbox talks as a topic library plus delivered records. Write a topic once, deliver it many times. Each delivery gets a date, a job and the people who were there. On a mixed crew, record the language it was given in — covering a topic in both English and Spanish in one huddle is a real thing and it belongs in the record.

Inspections from a template, scored, with findings that close. Reuse the checklist so results are comparable month to month, record pass, fail or not-applicable per item, trend the score, and put a corrective action with an owner and a date on anything that failed.

One place for things that go wrong, separated by seriousness. A PPE observation corrected on the spot and a serious hazard are not the same record, and lumping them together destroys the only useful signal — whether the same category keeps coming back on the same job.

A once-a-year reconciliation of the prequal numbers. Rates, the annual summary, the program’s revision date, your certificate. Do it in January and every prequal afterwards is copy-and-paste instead of a scramble.

How SubMark handles it

Safety in SubMark is an opt-in module, switched on per company — not a document store — and it sits beside the jobs it belongs to.

Toolbox talks are a topic library plus delivered talks. A topic has a title, a category, a body, key points, discussion questions and a reference field for the standard it relates to; some topics come shared rather than written by you. A delivered talk is attached to a job or marked company-wide, with a date, a location, a language — English, Spanish, or both for a mixed crew covered in one huddle — and an attendee list signed off person by person. The talk carries its attendee count, so an incomplete roster is visible now rather than discovered later. Superintendents and PMs can run and record a talk from a phone.

Inspections are template-based: build a checklist once as a list of items and reuse it, so results are comparable month to month. Each item is recorded pass, fail or not applicable, the inspection carries a 0–100 score and a count of failed items, and it is attached to a job. Corrective actions are tracked, which is the closing-the-loop half.

Certifications and compliance is one list, with the thing the folder cannot do: an expiry date per record, and a status that changes on its own as the date approaches and passes. A certification has a type, a person — one of your workers, or a named person at a company you hired — a certificate number, issue and expiry dates, and the document attached. The safety overview counts what expires in the next thirty days, certifications and COIs separately, so the answer to “what lapses this month” is a number on a page rather than an audit.

The same page holds subcontractor qualification for the subs you hire: a qualified or not-qualified status, their experience modification rate with its year, recordable and days-away rates, the year of their annual summary, a qualified-through date and their safety program document. That is the prequal packet you receive, filed in the shape you will be asked for it.

Violations are recorded per job, by category — personal protective equipment, fall protection, electrical hazard, ladder and scaffold, housekeeping, other — with a severity from minor through moderate, serious and willful, the person and company involved, and the action taken, from a verbal warning or corrected-on-site through written warning, sent home, suspended or terminated. Your safety lead can file them from a phone on site, which is the only time anybody actually files them. The overview breaks them down by category and severity and counts each worker’s moderate-or-worse violations as strikes against a threshold (three in a rolling year by default), so a pattern surfaces as a pattern. Incidents are a separate record with their own severity scale and corrective actions.

Honest limits. SubMark is not a regulatory compliance service. We hold your records; we do not interpret the rules, file anything with anyone, or generate your written program or any government form. The reference field on a talk topic is a field you fill in, not a citation we vouch for. Incident recordability is a judgment you and your carrier make — the app records what you tell it.

Safety sits in safety and the back office with the worker roster the certifications hang off, and the schedule deciding who is on the job in the first place is crew scheduling for commercial subcontractors. Field users are free and unlimited on every plan, which matters here specifically: the people who run the talks and the inspections are exactly the ones you would never buy seats for. See how pricing works.

Where to start if this is all in a binder today

Do the expiry list first. It takes an afternoon and it is the one that stops a crew getting sent home. Every person, every certification they hold, the date it expires, sorted by date. Anything inside sixty days gets handled this week. Then the same for every COI you hold — yours and your subs’.

Second, pick one job and put four weeks of toolbox talks into a real record with real attendance. Not because four weeks proves anything, but because it tells you how long it takes, which is the number that decides whether this stays a paper process.

Third, write your prequal answers down once, with the year against each figure. The next packet becomes an hour instead of a day, and that hour is the whole return on doing any of this.