Turning Safety Week Into a Subcontractor Compliance Reset

Safe + Sound Week is voluntary. OSHA invites organizations to participate and recognize workplace safety and health programs. It does not require a COI audit, and a certificate review is not an OSHA condition of participation.

A contractor can still use the week as a calendar prompt to reconcile the active subcontractor roster, clean up insurance records, and assign old follow-ups. That COI reset belongs to the contractor's own contract and risk-management workflow.

Start with the crews on the job

Pull the active subcontractor roster from the people who know the work. Compare the office list with the current schedule, site access records, purchase orders, and project team's knowledge. You are looking for mismatches:

• a crew working under a trade name that does not match the agreement
• a subcontractor added after the last roster review
• a company that finished but remains marked active
• a lower-tier subcontractor your process requires someone to address
• a vendor scheduled to return with an old record

Identify the companies and work that the project is managing before you count PDFs.

The roster review may uncover safety onboarding, training, equipment, or site-access questions too. Route those to the safety program. A COI does not prove that a worker is trained, that a job hazard has been addressed, or that a safe-work procedure is being followed.

Keep safety records and insurance evidence in their lanes

OSHA's Safe + Sound Week focuses on management leadership, worker participation, and a systematic approach to finding and fixing hazards. Those are workplace safety subjects.

A COI serves a different purpose. It provides information about coverage in force when issued. It is not the policy, does not amend coverage, and does not create additional-insured status. Policy terms and endorsements control.

The two workflows can share a roster and an owner without pretending they are the same review. A subcontractor may have a current COI and an open safety item. Another may have completed orientation while an endorsement request remains unresolved. Keep those statuses separate so one green field does not hide a different open question.

Reconcile each active insurance record

For every active subcontractor covered by your process, confirm:

• the legal entity matches the agreement and the company performing the work
• the certificate on file is the current version received
• required policy dates have been checked
• listed limits were compared with the applicable written requirement
• any required policy provision or endorsement was requested and reviewed
• open items have an owner and follow-up date
• exceptions show the approver, reason, scope, and next action

Certificate-holder status is not additional-insured status. If the agreement requires an endorsement, a description or check mark on the COI should not close that review. Request the applicable policy provision or endorsement and send uncertain language to the person responsible for insurance or contract review.

Use the week to repair ownership gaps

Old COI issues often persist because everyone can see the problem and nobody owns the next move. "Waiting on sub" is not an owner. Name the person who will send the request, the date of the next follow-up, and the person authorized to resolve an exception.

Check vacation and field coverage too. If the normal reviewer is unavailable, can a backup see the request history and understand what remains open? If accounting or the project team needs a status, can they find it without messaging the person who happens to remember the file?

Make the queue small enough to work. Sort it into items that need a document, items that need human review, and items that need an authorized decision. Those categories lead to different actions.

Do not invent automatic consequences

A paperwork reset may reveal an expired date, a missing certificate, or an endorsement still under review. That discovery should trigger the approved escalation path, not an improvised order from the tracker.

Stop-work, payment, site-access, owner, audit, and public-work requirements vary by contract, law, and risk program. Confirm the facts, apply the governing process, and send close calls to the responsible reviewer. A COI alone does not decide whether work stops or payment is withheld.

Record the eventual decision. The next reviewer needs to know who made it, what it covered, and whether follow-up is still due.

Give the team a shared record

COI Compass can import the subcontractor roster, draft ACORD 25 fields with AI for human review, accept files through no-login upload links, send renewal reminders, and preserve record history. That helps the office, project, and risk team work from the same queue.

The software does not decide whether a certificate meets a contract, automatically verify an endorsement, or make a coverage decision. A human reviewer applies the written requirements and policy documents.

If your process is still a disciplined spreadsheet, keep using it. The tool matters less than the shared habits: current roster, explicit status, named owner, visible follow-up, and a record of decisions.

Close the reset with a short meeting

At the end of the week, bring the project, safety, accounting, and insurance-review owners together long enough to answer four questions:

• Which active subcontractors were missing from a system?
• Which COI items still need a document or human review?
• Which safety items belong in the safety program rather than the insurance record?
• Who owns each next action and due date?

Publish the queue where the approved team can reach it. Then schedule the next roster reconciliation based on your workload and project needs.

Use the week as a voluntary calendar prompt, then keep the safety program and insurance review in their proper records.