How to manage lower-tier subcontractors when you are the one hiring them

Most of what gets written about managing subcontractors is written for general contractors. It assumes you have a contracts department, a compliance platform that stops a payment when a certificate lapses, and leverage, because you hold the money.

You have none of that. You are a mechanical, electrical or glazing sub with eight people in the office, and the day you bought your first piece of lump-sum work — insulation, controls, test and balance, low voltage, caulking, rigging, a trenching crew — you became somebody’s GC with none of a GC’s tools. You now sit in the middle of the chain: a GC above you holding your money, a sub below you asking for theirs, and a scope boundary between you where the margin leaks out.

Here is how to hold that position without inventing a contracts department.

The scope boundary is where the money actually leaks

Nearly every dispute with a lower tier is the same dispute: you thought you bought something they are certain they did not sell.

The classic boundaries, and they recur on every job:

• Who insulates the duct, and who insulates the hangers and the plenum penetrations.
• Who provides the sleeve, who sets it, who firestops it — and whether safing at the slab edge is in anybody’s number.
• Who pulls and pays for the sub-permit, and whose license it sits under.
• Who furnishes the lift, the hoisting, the scaffold, and the man-lift fuel.
• Who patches, who paints the patch, and who cleans the room afterward.
• Who provides as-builts and O&M data for their portion at closeout, and in what format the GC demands it.

The fix is not a longer contract. It is a scope sheet with exclusions written on it, not only inclusions. Inclusions are what a salesman writes. Exclusions are what an argument is made of. Three lines — “excludes firestopping,” “excludes hoisting,” “excludes final clean” — will save you more money this year than any software decision you make.

Get it on the per-job authorization, not in an email thread. And date it before their crew lands.

You now have two payment clocks, and they do not line up

Your GC pays you 45 to 60 days after a draw that you submitted on the 25th of last month. Your lower tier invoices on the 30th and calls you on the 10th. That gap is not a cash-flow problem you can solve with goodwill; it has to be dealt with on paper, up front.

Three things that work:

1. Tell them your draw date in writing before they start. Not “we pay in 45 days” — the actual mechanics: your billing cutoff is the 25th, their invoice has to be in your hands by the 18th to make that cutoff, and payment follows your GC’s payment to you. A sub who knows the calendar stops calling on the 10th. A sub who finds out on the 10th never trusts you again. Our write-up on the construction billing cycle has the dates on the GC side of the same cycle.

2. Put the flow-down in the agreement, and mean the version you can defend. “Pay when paid” language varies in enforceability from state to state and that part is a question for your attorney, not for a blog. What is purely operational is this: whatever condition sits above you should sit below you, with the same trigger, not a harsher one. If your GC releases retainage on substantial completion plus 30, that is the clock you pass down.

3. Do not hold 10% retainage on a $14,000 scope. You are holding $1,400 of a small company’s money for eleven months to protect yourself against a risk worth less than the goodwill it costs. Flow retainage down where the dollars justify it and waive it where they do not — after checking what your own contract and your state’s rules require. On the other side of that decision, when retainage actually gets released is the same question your sub is asking you.

Their extra always shows up after yours has gone in

This is the sequencing failure that costs the most and gets discussed the least.

The GC’s superintendent asks for something. You open a change event, price it, and submit your change order. Then your insulation sub mentions, three weeks later, that the same change added 40 hours of their work — and your approved change order has no money in it for them. You now eat it or go back to the GC with a revision, which is the single worst look there is.

One rule fixes most of it: no extra work goes forward on a lower tier’s scope until you have your own change event open, with their number in it. Make it a condition of the authorization. Your sub does not get to work on a verbal from your foreman, for the same reason you do not. If the distinction between a change event and a change order is fuzzy in your office, we wrote it up, and the whole change order process from the sub’s seat sits next to it.

And when the extra is time and material, the markup rule is the one that gets packages rejected: no markup on markup. Their invoice already carries their overhead and profit. Yours goes on their total once, at your tier. Pricing a T&M ticket covers the rest.

Backcharges now run in both directions

You already know what it feels like to receive one. The mechanics for issuing one are the same, and so is the discipline: a backcharge nobody documented on the day it happened is a negotiation, not a deduction.

If their crew left debris and your guys hauled it, that is a dated daily log entry with a photo, the hours, and a note to them the same week — not a line item that appears on their final invoice four months later. The exact same evidence standard you want your GC held to. Back charges in construction is the longer version.

The paperwork you are now holding, and the piece everyone forgets

You hold, for every sub you hire: a signed master agreement, a per-job work authorization with the scope and exclusions, a W-9, a certificate of insurance with the right limits and the right additional-insured wording, and their lien waivers.

The piece everyone forgets is expiry. A COI is a snapshot. On an eleven-month job it will lapse mid-job, and when it does, two things happen: your sub is uninsured on your job, and your GC’s compliance system can discover it before you do and hold your payment. Nobody emails you to say a date has passed.

So the COI file is not a folder of PDFs. It is a list with a date per record and something that tells you what lapses in the next 30 days. Same for any certification you require of them. Construction safety documentation covers how to run that list for your own people and for the companies you hire.

On waivers, know which direction you are responsible for. You send waivers up to your GC with your draws. You collect them down from your subs and suppliers — and many GCs will not process a draw, or will not release retainage, without lower-tier waivers in hand. Those are two separate chases with two separate deadlines. Lien waiver tracking walks the up-chain side.

Their records are your evidence

When the job goes sideways and somebody wants a delay claim or an impact argument, you will need to show what happened on the days your lower tier was on site. If their only record is an invoice at the end of the month, you have nothing.

Require daily manpower from every sub you hire: who was on site, how many, what area, what stopped them. It costs them five minutes and it goes into the same pile as your own daily logs. The best way to get it is to stop asking for an email and put it somewhere fixed — at minimum, a line on your own foreman’s daily log for every sub crew on site.

How SubMark handles it

SubMark holds the hiring side, not just your own side of the chain:

• A directory of the subs you hire (an opt-in module) — their COI with its expiry date tracked, whether a W-9 is on file, their contracts, and the jobs they are on. If you also run the opt-in safety module, its dashboard counts the COIs expiring in the next 30 days, so “what lapses this month” is a number on a screen rather than an audit.
• Per-job work authorizations that auto-fill from the project and are tracked from draft to sent to signed, with each sub’s master agreement recorded alongside, so the scope and exclusions sheet is attached to the job rather than sitting in a sent-items folder.
• Invite a sub into the project with scoped access: they see the scope, plans and approved submittals and can log change events, and you choose whether they also see the schedule, update production or file T&M tags. Their daily manpower goes on your foreman’s daily log, which has a line for each sub crew’s headcount and area. Every sub you invite is free, like every field user — pricing charges only for office users beyond the three included.
• Purchase orders for the material you buy, which is the other half of committed cost. The PO process for subcontractors is the long version.

Two honest limits, because they are the first things a reader of this page will assume:

• There is no prequalification questionnaire. COI and W-9 status, not a scored prequal package.
• Lien waiver tracking covers the waivers you send up the chain, not the ones your own lower tiers owe you. Chasing those is still a phone call.

The rest of the office side is on the product page.

What to do this month

1. Add an exclusions block to your standard work authorization. Three lines, the ones that burn you most often.
2. Put every COI you hold on one list with its expiry date, sorted by date. Anything inside 60 days gets handled this week.
3. Send every active lower tier your billing calendar in writing: their invoice deadline, your cutoff, when payment follows.
4. Make “my change event is open first” a rule your PMs cannot skip.
5. Ask each sub for daily manpower, and give them one place to put it.