Insurance and legal requirements described here vary by state and by contract, and nothing below is legal advice. A subcontractor requirement decides whose policy answers when something goes wrong. Every way it fails ends the same way: the exposure travels up to whoever hired without checking.
Why this is not a paperwork question
Requirements get treated as administration because they arrive as documents. What they actually do is allocate loss, and the allocation is not symmetrical — it runs uphill.
When a sub carries adequate coverage, a loss arising from their work sits on their policy. When they do not, the loss looks for a responsible party who does. That search does not stop at the sub’s empty file; it continues to the party that hired them, and it arrives with your own general liability limits and your own loss record attached.
That is the whole argument for doing this properly. Not tidiness, and not a lender asking. The requirement set is the mechanism that keeps a loss on the policy that was priced to carry it, and there are a small number of specific ways it fails.
Reading the contract above you before writing the one below you
The requirement you impose downward should start from the one imposed on you. General contractors and owners flow requirements down through the chain, and anything you fail to pass along you have agreed to carry yourself.
Read the contract above you for four things: the coverage parts it names, the limits it sets, the statuses it demands — additional insured, waiver of subrogation, primary and non-contributory — and whether it obliges you to require the same of anyone you engage. That last clause is common and easy to skim.
Then write yours to at least match. Writing a looser requirement downward than the one you accepted upward is the most avoidable version of this whole problem, and it is invisible until a claim arrives at the gap.
The sub who never carried anything
The simplest failure. The sub was hired on a handshake or on a quote, nobody asked, and there is nothing to produce.
It is more common than contractors expect on small trades, on short engagements, and on the day-labor end of a schedule where the work feels too minor to formalize. Loss severity does not scale with engagement size. A one-day operator on your machine can produce the largest claim of the year.
The control is unglamorous: no document, no start date. It works only if it is applied without exception, because every exception becomes the precedent for the next one.
The sub whose policy lapsed mid-job
The second failure is a document that was true when you received it. A certificate reports a policy as of the day it was typed. Nothing about it commits anyone to keeping the policy in force.
Subs on thin margins let coverage lapse, and it happens in the quiet months rather than the busy ones. The certificate in your file still reads perfectly, and the policy behind it stopped some weeks ago.
What answers this is dates rather than documents. Record the term end date of every certificate you hold, and diary it. For engagements running past a sub’s renewal, ask for the replacement before the old term ends rather than after. The mechanics of the document itself, and why it can only report and never promise, are in the certificate a rental yard will accept — the form is the same wherever it is used.
The sub with liability and no workers compensation
The third failure is partial coverage, and it is the one that produces surprises at both ends of the year.
A sub with liability coverage and no workers compensation is covered for what they damage and uncovered for the person who gets hurt doing it. Injury is the more likely event and frequently the larger one, and where the sub has no coverage the claim looks upward exactly as described above.
There is a second consequence, and it is financial rather than legal. At your own premium audit, subcontractor cost that cannot be shown to have carried its own workers compensation for the period of the work is commonly treated as your payroll. The evidence for that is the certificate covering those dates, which is why this is collected before the job rather than reconstructed afterward.
The sub whose policy excludes the work they were hired to do
The fourth failure is the hardest to see, because the paperwork is complete and correct. The sub has coverage, the limits satisfy your requirement, and the policy does not cover what you asked them to do.
Exclusions and classification do this. A policy written around one trade may exclude work at height, work below grade, work on certain structures, or operations involving equipment the sub does not normally run. A classification that describes light work does not silently expand because a bigger job came along.
The check is a conversation rather than a document review: describe the work the sub will actually perform and ask whether their coverage contemplates it. Where they will be operating your machines, the question is sharper still, because responsibility for the equipment itself is a separate matter from liability for the work — that seam runs through rented, leased or borrowed equipment coverage and the rented and leased part.
The sub who is really an employee
The fifth failure is a classification question rather than a coverage one, and it is the reason this subject touches employment and tax law at all.
Whether a worker is an independent contractor or an employee is determined by the facts of the working relationship under state and federal tests, not by what the parties call it or by the existence of an invoice. Direction and control, who supplies the equipment, whether the work is integral to your business, and whether the worker serves other customers all bear on it, and the tests differ between agencies and between states.
The consequences of getting it wrong are not confined to insurance. They reach payroll tax, wage and hour obligations and workers compensation coverage simultaneously. This is the point in the subject where the right move is a conversation with your own accountant and counsel about your specific arrangements, because the answer genuinely depends on facts an article cannot see.
The audit is where all of it surfaces
Most of the failures above stay quiet until one of two events. A claim is the dramatic one. The premium audit is the routine one, and it arrives every year on schedule.
Real-World Scenario: A site contractor runs a good year with two trusted subs, both of whom produced certificates when they started. One of them, a small operator working mostly for him, stops carrying workers compensation in the winter and never mentions it, because there was no claim and nothing to mention. At the audit the auditor asks for certificates covering the periods in question, and the winter months have none. The contractor is not accused of anything and nobody was hurt. The cost of those months is simply reclassified as his own payroll, and the number it produces is the largest single line on the audit.
Nothing about that outcome required a loss. It required a gap in a file, and the gap was in his own file rather than in the sub’s.
The habit that prevents it is small: a folder per sub, a certificate with dates that cover the work, and a review at your own renewal. Reading your own equipment schedule at the same time makes it one afternoon rather than two.
What a workable requirement set looks like
Keep it short enough to enforce and specific enough to mean something. Name the coverage parts, with workers compensation named explicitly rather than assumed. Set limits at least matching what flows down to you, and where your own limits need help above the primary layers, an umbrella is usually the cheaper route. State the statuses you require and treat them as endorsements on their policy rather than as lines on a form. Require the certificate before work starts and a replacement before any term expires. Where a sub will haul or operate machines, address transport explicitly — transit and trailer transport is the part that answers for a machine in motion.
Then apply it the same way to everyone, including the sub you have used for years. That one is the exception every contractor makes, and it is the one that shows up at the audit. Where a sub is renting machines to work your jobs, the compact loader requirement set shows what a yard will ask them for, and the coverage lineup sets out the parts a contractor program is built from. To have your own requirement set read against the contracts you sign, send the detail through the quote form, and who we are explains how we work these reviews.