Compliance gating means a subcontractor can't start work, or can't be paid, until specific documents are in. Keep two separate gates: a mobilization gate for insurance, onboarding and site requirements, and a payment gate for certified payroll, lien waivers and current coverage. Tie every hold to the exact missing document and a named reviewer. Buildalytic shows what is missing, and Brody follows up with the sub until it arrives.
What to take away
- Mobilization and payment are different gates with different documents.
- A hold should name the exact missing item, not just say the sub is non-compliant.
- Hold only what the contract allows, and release it as soon as the item clears.
- Log who approved each hold and each release.
Why gates get messy
Most general contractors gate subcontractors somehow: no certificate of insurance, no mobilization; no lien waiver, no check. The trouble starts when everything goes into one bucket marked non-compliant. A sub whose certified payroll for week six is missing gets its whole pay application held with no explanation, or a sub with an expired auto policy is allowed on site because the payment team cleared it last month.
Separating the gates, and tying each hold to a specific document, fixes most of this. It is also easier to defend when the sub asks why they haven't been paid.
The two gates
Typical items. Your subcontract and the project's requirements decide what actually applies.
| Gate | Typical items | Blocks | Usual owner |
|---|---|---|---|
| Mobilization | Certificate of insurance with required endorsements; signed subcontract; prequalification; safety plan and orientation; site-specific training; worker authorization records where required | Starting work on site | Project manager with risk or insurance reviewer |
| Payment | Current insurance; certified payroll for every week worked on prevailing wage jobs; conditional and unconditional lien waivers; lower-tier waivers; apprenticeship and participation records where required | Release of a payment | Project accountant with compliance reviewer |
On public work, the stakes are higher
On federally funded construction covered by Davis-Bacon, the contract clauses in 29 CFR 5.5 let the agency withhold accrued payments to cover unpaid wages, and allow it to suspend further payment when required payroll records aren't submitted. That pressure flows down: a prime contractor that can't show complete certified payroll for every tier risks its own payment. That's why many GCs make certified payroll a payment gate for each subcontractor.
Sources: eCFR: 29 CFR 5.5, contract provisions and related matters
Worked example: one subcontractor, two gates
Illustrative status for an electrical subcontractor on a public project, pay application for October.
| Item | Gate | Status | Effect | Reviewer |
|---|---|---|---|---|
| Auto liability policy | Mobilization | Expired 2026-10-31; renewal certificate requested from broker | No new crews on site until the certificate is received | Risk manager |
| Additional insured endorsement | Mobilization | Received and accepted | None | Risk manager |
| Certified payroll, week ending 2026-10-11 | Payment | Missing | October payment held as the subcontract allows, pending the payroll | Compliance reviewer |
| Certified payroll, weeks ending 10-04, 10-18 and 10-25 | Payment | Accepted | None | Compliance reviewer |
| Conditional progress waiver, October | Payment | Received | None | Project accountant |
| Unconditional waiver, September payment | Payment | Received | None | Project accountant |
| Supplier waiver, wire supplier | Payment | Not received | Payment can't be released until received | Project accountant |
Reading the example
The sub can keep working with its existing crews, because only the auto policy renewal is open on the mobilization side, and new crews wait for it. On the payment side, two specific items are holding the October payment: one week of certified payroll and one supplier waiver. Everyone can see exactly what clears the hold, and who decides.
Compare that with a status of non-compliant, payment held. The sub doesn't know what to send, the project manager doesn't know whether crews can mobilize, and the accountant fields the same phone call every day.
Rules that keep gates fair
Hold only what the contract and the law allow. Many subcontracts and state prompt-payment laws limit what can be withheld and for how long; check yours before setting the default.
Release as soon as the item clears. A hold that lingers after the document arrives costs the sub money and costs you goodwill.
Log every hold and release with the reviewer, date and document, so an audit or a dispute has a clear record.
Don't let mobilization approval imply payment approval, or the reverse. They are separate decisions.
Cross-checks that catch real problems
Payment gates are a chance to compare records that are usually checked in isolation. Compare the workers on certified payroll with the workers signed in on site, the classifications reported with the work described in daily reports, apprentice counts with registered program records, and fringe payments with the wage determination. A mismatch isn't automatically a violation, but it is the question to ask before money moves.
Build the requirement list once per subcontract
Gates work only if everyone agrees what each sub owes. When the subcontract is signed, list the requirements for that sub on that project: insurance limits and endorsements from the subcontract, certified payroll if the job is prevailing wage, waiver types and forms from the payment terms, apprenticeship or participation reporting from the prime contract, and any owner-specific site requirements. Mark each one as a mobilization or payment requirement, with its frequency: once, monthly, weekly or at renewal.
A sub with no prevailing wage obligation shouldn't be chased for certified payroll, and a sub working only off site may not need site orientation. A list built per subcontract stops the gate from asking for things that don't apply.
Common mistakes
Holding the whole payment for one small missing item when the subcontract allows a proportionate hold. Releasing payment because the item was promised rather than received. Letting an insurance certificate lapse mid-job because nobody tracked the renewal date. Accepting a certificate without the endorsements the subcontract requires. Treating a lower-tier supplier's missing waiver as the sub's problem alone, when it is your lien exposure too. And keeping the reason for a hold in someone's email instead of on the job record.
What to measure
Track the number of subs on hold at each gate, the average days an item stays open from first request to acceptance, holds released within one business day of the document arriving, and payments delayed past the scheduled date because of a compliance item. The goal isn't zero holds; it's holds that are specific, short and fair.
Follow-up is most of the work
Most holds clear when the right person at the subcontractor gets a specific request: the payroll clerk for the missing week, the broker for the certificate, the supplier for its waiver. Request the exact item, give the date it is needed, remind after three business days, call after a week, and escalate to the sub's owner after two. Keep every message on the job record.
How Buildalytic helps
Buildalytic keeps mobilization and payment requirements separate for each subcontractor, shows the exact missing document behind each hold, and logs who approved each hold and release. Brody requests certificates from brokers, missing certified payroll weeks from the sub's payroll contact and lien waivers from suppliers, by call, text and email, until each item is in. Payroll checks run against the wage determination before payment.
Common questions
What is compliance gating in construction?
Blocking a subcontractor from starting work or being paid until specific required documents are received and accepted, such as insurance certificates, certified payroll and lien waivers.
Can a GC hold payment for missing certified payroll?
Often, if the subcontract allows it. On federally funded Davis-Bacon work, the contract clauses in 29 CFR 5.5 let the agency suspend payment when required payroll records aren't submitted, which is why many GCs gate payment on them.
Should an expired insurance certificate hold payment?
It depends on the subcontract. Many GCs treat it as a mobilization gate first, blocking new work on site, and some also hold payment until coverage is current.
How do you avoid holding too much?
Tie each hold to a specific document and the amount the contract allows, and release it as soon as that document clears.
Sources and editorial notes
- eCFR: 29 CFR 5.5, contract provisions and related matters
- Buildalytic: certified payroll audit
- Buildalytic: COI tracking
Prepared with AI assistance. Reference date: 2026-11-14. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.
How we prepare and update field notesSee exactly what is holding each sub.
Bring one public project. See mobilization and payment gates side by side, with the missing document behind every hold.
Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.
See compliance checks Explore the relevant capability


