§ 04
VENDOR COMPLIANCE · BEFORE THEY MOBILIZE, AND AFTER
Vendor compliance that actually blocks something.
A compliance folder nobody reads is not compliance. The point of tracking a certificate is that something downstream refuses to happen when it lapses.
Prequalification
Score the sub before you commit
Score a subcontractor on insurance, bonding, safety EMR and licensing. The criteria auto-fill from what is already on file — their certificates, their bonds including surety A.M. Best rating and expiry, their EMR, their license expiry date — and a reviewer then sets the decision: approved, conditional or rejected, with a next-review date. The score is decision support. The reviewer makes the call. Background reading: the prequalification guide.
Insurance
Certificates by coverage line, with the endorsements
General liability, auto, workers' comp, umbrella, professional and pollution — each with its own limits and effective and expiry dates — plus the endorsement forms that actually decide a claim: CG 20 10 additional insured, CG 20 37 completed operations, CG 24 04 waiver of subrogation. The insurance tracker flags expiring and lapsed certificates against a per-record alert window, with Renew and Create Task on the row.
Extraction
Drop the ACORD, skip the retyping
Upload the certificate PDF and the coverage fields fill themselves — limits, dates, additional insured and waiver-of-subrogation endorsements — instead of an admin keying a dozen-plus fields per sub. Where a Contract Review run exists on the project, the extracted limits are checked against that contract's insurance schedule.
Bonds
Bonds tied to the contract they secure
Performance, payment, bid and warranty bonds recorded against the contract and vendor they cover, with surety name and A.M. Best rating, principal and obligee, bond amount and premium, and effective, expiry and release dates.
Lien waivers
Requested, received, verified — or rejected
Conditional and unconditional waivers tied to the pay application or purchase order they cover, with through-date, amount, stated exceptions, notary detail, and who verified it. A rejected waiver keeps its reason.
Vendor record
One page per vendor
Spend to date and year to date, open commitments, delivered-versus-on-time counts, their certificates, their quotes and their bid history — plus quality, commercial, schedule, communication and safety ratings you set per project.
The gate that has teeth: you cannot release held retainage to a subcontractor while any of their lien waivers is still unverified, while no verified final lien waiver is on file for them, or while their insurance certificate has lapsed. That block is enforced on the server, not in the browser, so it holds no matter which screen the release was attempted from. Overriding it is possible — deliberately — but it requires a written reason, and the reason is stored with the user and the timestamp.
Before you release: choosing Release first lists what is on file and what is missing for that subcontractor on that project — waivers still unverified, waivers that name the subcontractor but are not linked to it (the release check does not see those), whether a final lien waiver is on file, and whether the insurance certificate is current, expiring, expired or missing. The rows marked Checked on release are the three things the gate stops on: a waiver that is not verified, no verified final lien waiver, and an insurance certificate that has lapsed. A certificate that is only expiring, or not on file, does not stop it. Trueleveler does not keep the wage affidavits or certified payroll that subcontractors send you; where labor records show prevailing-wage hours on the project, the list only reminds you to ask for them (shown to people who can see labor wages).