One set of rules per project: tracking requirements and renewals across active jobs

Why requirements differ by project

A GC's standard subcontract sets a baseline. Each prime contract can raise it. Public owners in particular publish detailed insurance exhibits, and the GC has to flow those requirements down to every trade.

The differences are real. Sonoma County's construction template scales general liability limits by project size, from $1 million per occurrence on jobs under $1 million to $10 million on jobs of $10 million and up, and sets completed operations durations from one to five years by the same tiers. Oregon DOT's subcontractor exhibit names specific additional insured forms and a 30-day notice requirement. Neither matches a typical private job.

Requirements as data

The structure that holds up treats requirements as data, not as a PDF in a folder.

• One record per project. Coverages, limits, endorsements, durations, additional insureds by exact legal name, carrier rating, deductible caps, notice and delivery rules.
• Trade tiers inside the project. Sonoma's template, for example, sets higher limits for framing, mechanical and electrical trades than for other trades.
• A source for every line. Which contract clause each requirement comes from, so a reviewer can answer "says who?"

With that in place, each certificate is checked against the right list automatically, and a change to the prime contract updates one record instead of a hundred emails.

Coverage at the policy level

A trade working three of your jobs has one general liability policy, not three. When that policy renews, it affects all three projects at once. When it lapses, all three are exposed.

So track renewals at the policy level: each trade's policies, their expiration dates, and every project that depends on them. Then a single renewal request covers every job, and a single lapse flags every job.

A renewal calendar that works

1. Diary every expiration date for every policy of every trade.
2. Request renewals 30 days out, certificate plus endorsements, because endorsements don't automatically carry over.
3. Re-check the renewal against every project the trade works on, since the new policy may differ.
4. Escalate on the date. No renewal in hand means no coverage. See our white paper on lapses mid-project.
5. Keep the diary after close-out. Completed operations requirements can run for years. See completed operations.

Where aggregates come in

If a trade's general aggregate is shared across every job it works, a big claim on one project can reduce what's left for yours. That's why some owners require the aggregate to apply per project. See per project aggregate.

The minimum viable version

If you do nothing else: one requirements record per project, one renewal diary per trade policy, and a rule that renewals are checked against every project before the old policy ends.