Property Management Vendor Insurance Requirements

A general contractor manages a subcontractor roster for the life of one job, with one close-out date. A property manager manages a vendor roster — landscapers, HVAC techs, roofers, plumbers, elevator contractors, pest control, pool maintenance, snow removal, security — that never closes out, spread across however many properties are under management, each vendor renewing on its own policy calendar that has nothing to do with any other vendor's.

The baseline coverages are the same ones covered in insurance requirements for subcontractors — general liability, workers' compensation, auto, tiered by risk. That's the correct starting point and this guide won't repeat it. What's different about the property management version of this problem is three things that don't show up on a single jobsite: two entities usually need to be protected, not one; some of the highest-risk vendor categories create liability that outlives the actual work by months or years; and the tracking problem multiplies by the number of properties in the portfolio, not by the number of trades on one job.

This guide covers what to require, who needs to be named, and the endorsement gap that almost every generic vendor-insurance checklist misses because it was written for construction, not for ongoing property operations.

Most vendors working on managed property need three coverages. General liability, commonly $1,000,000 per occurrence and $2,000,000 aggregate, is the floor for anyone doing physical work on or around the property. Workers' compensation is required wherever the vendor has employees performing the work — a landscaping crew, not a solo handyman. Commercial auto, commonly $1,000,000 combined single limit, applies to any vendor that drives onto the property or between properties as part of the job — which in a portfolio context is nearly everyone.

For a real-world reference point rather than a guessed number, the University of Miami's published vendor insurance requirements ask for the same $1,000,000/$2,000,000 general liability baseline, require the certificate at least two weeks before the contract starts, and name the university as both certificate holder and additional insured — and they're explicit that not every vendor needs every policy on the list, only the coverages that match the actual scope of work. That last point matters more in property management than almost anywhere else: a pest control vendor who never drives a company vehicle onto the property doesn't need auto coverage verified, and requiring it anyway just slows down onboarding for no protection gained.

Higher-risk trades — roofers, tree removal, elevator and pool contractors, anyone working at height or with structural systems — commonly need an umbrella policy layered on top of the base limits. A single blanket requirement across every vendor type over-insures the pest control vendor and under-insures the roofer; see the tiering approach in the subcontractor guide for how to structure that without a spreadsheet of one-off exceptions.

This is the first place property management diverges from a standard subcontractor checklist, and it's a mistake worth naming directly: a property management company that only requires vendors to name itself as additional insured, and not the property owner, has protected the wrong scope. If a claim happens, it's common for both the management company and the ownership entity to be named as co-defendants — the plaintiff's attorney names everyone with a plausible connection to the property, and lets the defendants sort out who's actually liable. A certificate that only names the management company leaves the owner standing on their own insurance for a claim the vendor's policy should have absorbed.

Both need to be named specifically, by their correct legal entity name, not a trade name or a shortened version that doesn't match the deed or the management agreement. For a portfolio with several ownership entities — common when properties are held in separate LLCs for liability-isolation reasons — that means the additional-insured language on a vendor's certificate has to match the specific property they're working at, not a generic "the management company and its clients" phrase that a lot of vendors default to when nobody pushes back.

Being listed as certificate holder doesn't accomplish any of this — it only means a copy gets sent to that address. That distinction is covered in full in additional insured vs. certificate holder, and it's worth reading in full if it isn't already clear, because it's the single most common gap found when a certificate is checked after an incident instead of before one.

Here is the piece that generic subcontractor-insurance content, written for a jobsite with a single close-out date, doesn't cover well: additional-insured protection under a vendor's policy can expire before the risk does, and property management is where this actually bites.

The standard ISO additional-insured endorsement, form CG 20 10, covers claims arising from a vendor's ongoing operations — meaning work that's actively underway. In its current version, it stops there. It does not extend to a claim that shows up after the work is finished. A separate form, CG 20 37, covers additional-insured status for the vendor's completed operations — claims that surface after the job is done. Carriers sometimes issue both together on one endorsement schedule; often they don't, and a vendor's certificate shows CG 20 10 with no CG 20 37 anywhere on it.

For a general contractor closing out a single job, that gap is real but bounded — there's a defined project end and a defined statute of limitations to watch. For a property manager, it's a live exposure on exactly the trades that matter most: a roof a contractor installed eight months ago that starts leaking, a pool resurfacing job where a slip happens the following season, an elevator repair that fails after the technician has long since left the property. If the only endorsement on file was CG 20 10, the vendor's insurer has no obligation to defend the owner or the management company for a claim tied to work that's already complete — regardless of how current the certificate looked at the time the work was done.

This isn't a reason to treat every vendor's certificate as suspect. It's a reason to specifically ask, for any vendor doing structural, roofing, pool, or elevator work, whether their additional-insured endorsement covers completed operations and not just ongoing operations — and to keep that certificate on file for as long as a claim could plausibly surface, not just for the duration of the job.

A certificate is evidence a requirement was met. The requirement itself has to come from somewhere else, and in property management that's usually two documents, not one: the management agreement between the owner and the management company, and the vendor contract or work order between the management company and each vendor.

The management agreement typically obligates the management company to maintain adequate insurance oversight on the owner's behalf — which is where the dual additional-insured requirement above actually gets created as an obligation, not just a good idea. The vendor contract is where that obligation gets passed down: naming the required coverages, the minimum limits, the additional-insured and completed-operations requirements, and a duty to maintain them for the life of the relationship, not just at signing. A property management attorney writing on vendor liability has flagged this specific gap: indemnification and insurance language often sits in boilerplate contract sections that nobody reviews line by line, and a management agreement with vague or missing flow-down language can leave the management company holding a claim that a properly worded vendor contract would have passed to the vendor's own insurer.

If your vendor contracts don't currently name the specific coverages, limits, and endorsements required — rather than a general "vendor shall maintain adequate insurance" clause — that gap is worth closing with your attorney or broker before the next vendor renewal cycle, not after a claim reveals it.

A written requirement that nobody actually checks before dispatching a vendor isn't a requirement — it's a hope. The practice that closes this gap in well-run vendor programs is a hard rule: no current, compliant certificate on file, no work order goes out. Not a judgment call made by whoever's fielding the maintenance request that morning, but a block built into the dispatch or work-order process itself.

That's a harder discipline to hold than it sounds, because the operational pressure always runs the other way — a tenant has an emergency, the usual landscaper's certificate lapsed two weeks ago and nobody flagged it, and the choice in the moment is between an uninsured vendor and an unhappy tenant. The gate only works if it's checked automatically before that moment arrives, not manually in the middle of it.

A single property with a dozen vendors is a manageable spreadsheet. A portfolio changes the math in a way that isn't just "more of the same": every property has its own vendor roster, every vendor renews on a date that has nothing to do with any other vendor's, and a property manager isn't reviewing the same twelve renewal dates every year — they're reviewing a different, unpredictable handful every single week, scattered across every property they oversee.

That's the specific failure mode covered in more depth in who is responsible for tracking certificates of insurance and COI expiration tracking: the check itself is simple, but remembering to run it, for the right vendor, before the right date, dozens of times a week, is where manual tracking actually fails — not because anyone did anything wrong on a given certificate, but because nothing was watching the calendar in the background.

The consequence isn't hypothetical. Courts in a range of states have held that hiring a contractor without verifying they carried adequate insurance can itself support a negligent-hiring claim against the party that did the hiring — separate from whatever the contractor actually did wrong on the job. A property manager who dispatches a vendor without a current certificate on file isn't just skipping paperwork; they're removing the one document that would otherwise show reasonable care was taken in who was allowed on the property.

The financial mechanics of a lapse — what actually gets billed, to whom, and why manual tracking is where it usually goes wrong — are covered with real examples in the real cost of a lapsed vendor policy. The short version: nobody notices a lapsed certificate until an incident forces someone to go looking for it, and by then the vendor's insurer has no obligation to respond.

The patterns that show up repeatedly when a vendor file is examined after something has already gone wrong.

Every piece of this — the dual additional-insured requirement, the completed-operations gap, the hard gate before dispatch, the staggered renewal calendar across every property — is a straightforward check on any single vendor. The difficulty is holding all of it consistently, for every vendor, on every property, permanently, which is exactly where a spreadsheet or a shared drive full of PDFs starts to fail quietly rather than loudly.

CoverSynx gives each vendor a link to submit their certificate without needing an account, reads it, and checks it against the coverages, limits, and endorsements a given property requires — including flagging a certificate that only shows ongoing-operations coverage where completed-operations matters, and a certificate that names the management company but not the owner. It sends reminders ahead of each vendor's own renewal date and surfaces what's expiring across every property in one place. It assists verification; it doesn't certify coverage or replace a call to your broker or attorney on anything that looks unusual for a specific vendor or property. See how to track certificates of insurance for the broader collection and renewal workflow, and COI tracking for property managers for how this applies specifically to a multi-property portfolio.