The pre-mobilization checklist
Before any sub touches your job, pin these:
- Signed subcontract (your standard form, not theirs)
- Current COI naming you as additionally insured
- W-9 on file
- OSHA 10/30 or your prequal record
- Schedule of values pre-priced (so partial pay apps don't blow up later)
- Lien waiver template the sub will sign each pay period
Missing any of these on day one is what turns a routine pay app into a two-week problem later. The two-hour sit-down before mob is the cheapest insurance you ever buy.
COI tracking is a calendar problem, not a judgment problem
COIs lapse on a calendar that no one watches. Build a spreadsheet (or use software) that tracks expiry per sub, sends an automated email at 30 days out asking for the renewal, and locks payment on a sub if their COI lapses.
The lapse is silent — you find out when you need the certificate, or when something happens on site during the gap. That gap is uninsured by definition. Build the expiry list, get the reminder before the renewal date instead of after, and hold payment on a sub whose certificate is stale — it's the only lever that reliably produces a renewal.
Lien waivers — partial vs final, conditional vs unconditional
Conditional partial — the sub waives lien rights for the work paid in this period, conditional on the payment actually clearing. Use this on every monthly pay app.
Unconditional partial — same waiver, no conditions: the sub releases rights for that period whether or not your check clears. Lenders routinely require these, so you will have to ask — ask for the priorperiod, the one the sub has already been paid for. Demanding an unconditional waiver for a period you haven't paid is how you lose the subs you want to keep.
Conditional final — at job close, sub releases all remaining lien rights conditional on final payment clearing.
Unconditional final — total release. Only after payment has actually cleared. Your owner will normally require this before releasing your retention — A201 §9.10.2 lets the Owner designate which releases it wants.
The daily huddle that actually saves time
10 minutes, 7am, on site:
- What did you finish yesterday?
- What are you doing today?
- What are you blocked on?
That's it. The blockers are the gold — if a sub flags “I'm waiting on the architect's answer to RFI #042,” you write the chase email at 7:15. If three subs are waiting on the same answer, you escalate at 7:30.
The sub portal pattern
Modern construction software (including neuroBLDR) ships a magic-link sub portal. Subs don't need a login — they click a link in an email and see only their work on this project. Three things they should be able to do:
- Submit weekly hours (you review and approve)
- Sign the lien waiver tied to the latest pay app
- Acknowledge approved change orders that affect their scope
Everything else (drawings, RFIs, photos, etc.) the sub gets via email, where they already live. Don't make the sub log into a portal to do their daily work; they won't.
The four sub patterns to watch for
1. The over-promiser.Says yes to every schedule and misses most of them. Confront it the first time, in writing, and swap them out before the second miss — the schedule you're protecting isn't yours, it's every trade stacked behind them.
2. The double-booker.On three jobs at once, allocates labor to whoever pays first. Make sure you're paying on time, then ask them weekly which job they're prioritizing.
3. The COI lapser.Always renews after a gap. Lock payments until current; one bad faith renewal and they're off your roster.
4. The lien-waiver dodger.Wants to be paid but doesn't want to sign. Don't cut the check. Period.
How neuroBLDR handles sub coordination
Each sub on a project can use a project-scoped magic-link portal to submit time, sign waivers, and acknowledge approved COs from a phone. Conditional partial waiver records are created from paid pay-app activity where matching sub bills exist. COI expiry stays visible across the roster and can queue a renewal email draft for human approval; it does not contact the sub on its own.