Operational Efficiency
Why Construction Project Managers Shouldn't Be Reviewing Insurance Certificates
Project managers are asked to approve certificates between RFIs and pay apps, with no training in endorsement forms and every incentive to get the sub on site. The fix is not more training. It is moving the review off their desk.
- Published
- Reading time
- 6 minutes
In this article
The review nobody trained them for
Before co-founding Pikorua Security, I ran construction risk for an ENR Top 100 general contractor. Our project managers approved subcontractor certificates the way most project managers do: check the expiration dates, check that the limits look like round numbers, file the PDF and get the crew on site. None of them had been taught to read an endorsement page, and none of them had time to learn.
That is not a criticism of project managers. A complete review of one certificate and its endorsement packet against contract specifications takes 25 to 40 minutes (CFMA Time Study). A project manager with 30 subcontractors mobilizing over a quarter is being asked to find 12 to 20 hours for a task that is not in the job description and is not how anyone measures the job.
When a review is skipped, nobody notices until a claim. A crew from an under-insured subcontractor looks exactly like a compliant one on the jobsite, and the gap stays invisible until a tender is denied or an auditor pulls the file.
What a real review involves
The certificate is the cover sheet. The review happens in the pages behind it, and a complete one covers every item below for every subcontractor, at onboarding and again at each renewal:
- The named insured matches the legal entity that signed the subcontract, not a trade name.
- Every limit meets the exhibit: each occurrence, general aggregate, per-project aggregate (CG 25 03), products-completed operations aggregate, auto combined single limit, employers liability and umbrella.
- Additional insured status covers ongoing and completed operations with acceptable edition dates (CG 20 10 with CG 20 37, or blanket equivalents).
- Primary and non-contributory wording (CG 20 01) and waivers of subrogation on general liability, auto and workers compensation (CG 24 04, CA 04 44, WC 00 03 13).
- Carriers are rated A- VII or better by AM Best, matched by NAIC number.
- No red-flag forms such as CG 21 39 or a carrier action over exclusion.
- Policy periods cover the scheduled work, with every renewal date tracked.
The incentive problem
Project managers are measured on schedule and margin. When a deficient certificate arrives on Monday and the crew mobilizes Tuesday, the rational choice is to let the crew on and chase the paperwork later. Later rarely comes. Resolving one non-compliant certificate by hand takes 28 days on average across the project manager, the subcontractor and the broker (Pikorua Security Benchmark Data), and when tracking lives in spreadsheets, 25% to 35% of active subcontractor policies expire mid-project without anyone noticing (Pikorua Security Benchmark Data).
Finance teams solved a version of this problem long ago with segregation of duties: the person who wants an invoice paid is not the person who approves it. Insurance verification deserves the same separation. The person who needs the sub on site should not be the only person deciding whether the sub is insured.
There is also a knowledge gap that training will not close. ISO revises its forms on its own filing cycle, carriers add manuscript exclusions, and owners add project-specific requirements. A project manager who reviews certificates a few times a month cannot keep that knowledge current, and should not have to.
What the math looks like
Take a general contractor doing $50 million in annual volume with 150 active subcontractors a year. Initial review, renewals and chasing add up to about 4 hours per subcontractor per year, or 600 hours. At a $45 loaded hourly cost for project staff, that is $27,000 a year in administrative payroll, spent mostly by people hired to build.
The quality math is worse. With a 71% first-review defect rate (AGC Risk Committee Audit), about 106 of those 150 subcontractors have a coverage gap in the file. Each one is a potential denied tender, and the average out-of-pocket loss when an additional insured tender is denied runs $150,000 to $450,000 (Commercial Casualty Actuarial Study).
On Pikorua Security Professional at $8,388 a year, the same contractor recovers about 520 of those 600 hours, and the endorsement review happens on every packet instead of only the ones someone had time for.
A better division of labor
Moving the review off the project manager's desk does not remove the project manager from compliance. It gives each role the part it is equipped to own:
- Project managers own the gate. They know when a sub mobilizes, they see one status (Compliant, Deficient or Expiring) inside the project tools they already use, and they never read an endorsement.
- Risk managers own the rules. They translate each contract exhibit into checks once, approve exceptions in writing and work the deficiencies software cannot resolve.
- Accountants own the hold. Pay applications from non-compliant subs route to an exception queue instead of approval.
- Brokers own the fix. Deficiency notices go to the subcontractor's retail broker with the exact endorsement missing and a zero-login upload link.
- Admins own access. Role-based permissions keep each group to its part of the record.
Making the switch without slowing mobilization
The transition is simpler than most teams expect. Upload the certificates you already have and audit them first, because the gaps you find set the priority list. Build rules from your standard subcontract exhibit, then add project-specific overrides for owner-driven requirements. Connect Procore or your ERP so status appears where project managers already look.
Then agree, in writing, who can grant an exception, for how long and for which deficiencies. An exception policy is what lets a project manager mobilize a sub on a Tuesday without quietly becoming the risk manager. If you want to see what your current files look like before changing anything, start by auditing five certificates.
Expect the first month to surface more deficiencies than anyone expected. That is the backlog becoming visible, not the new process creating work, and it shrinks quickly once brokers are receiving specific requests.
Related reading
About the author
Ananya Rao
Co-founder & CEO, Pikorua Security
Ananya co-founded Pikorua Security after working as a construction risk manager for a US ENR Top 100 general contractor, where she reviewed subcontractor insurance packets and tender files firsthand. She studied civil engineering at IIT Madras.
The Risk Transfer Brief explains insurance and contract concepts in general terms. Pikorua Security is software, not a law firm, insurer or broker. For contract drafting, or a coverage position on a specific claim, work with your coverage counsel.