What is COPE data in commercial property underwriting?

If you underwrite commercial property, you've filled out the COPE fields more times than you can count, usually from an application that someone else typed up weeks ago.

COPE stands for Construction, Occupancy, Protection, Exposure, the four buckets that drive how a commercial property risk gets priced and whether it gets bound at all. Together they form the underwriting logic sitting underneath the application, the questions that matter even when the form answers them badly.

The four letters, plainly

Construction covers what the building is made of: frame type, roof shape and covering, number of stories, year built, exterior wall material. This is the field most likely to be wrong on the application, because it's the field the applicant has the least reason to get right. A tenant filling out a renewal questionnaire doesn't know if the roof was re-covered with class 4 shingles or standard three-tab. The agent doesn't either, usually.

Occupancy is what happens inside the building: retail, warehouse, light manufacturing, habitational. This one mostly comes from the applicant and the SIC code, and it's usually reliable enough.

Protection is fire protection class, sprinkler status, distance to a hydrant, distance to the responding fire department. Some of this sits in ISO protection class lookups, some of it needs a loss control visit to confirm.

Exposure is everything around the building that could cause or worsen a loss: adjacent occupancies, wildfire interface, flood zone, nearby brush. This leans heavily on external data sources because the applicant isn't going to self-report that the lot backs onto a scrapyard.

Of the four, Construction is the one where imagery actually changes the underwriting file, because roof condition, roof geometry, and story count are things a picture settles that a form can only guess at.

Why the construction field is where the form breaks down

Ask an underwriter where COPE data goes stale fastest and most will say construction, specifically roof age and roof type. A property might have had the roof replaced two renewal cycles ago and nobody updated the SOV. Or the application lists "flat roof" when the structure has a mansard addition over half the footprint. None of this is fraud. It's just that nobody re-inspects every renewal, and paper trails lag physical reality by years.

A COPE underwriting checklist usually asks you to confirm or flag:

• Construction class and primary building material
• Roof shape, covering, and apparent condition
• Number of stories, including any setback or addition not on the original plans
• Protection class and proximity to protection infrastructure
• Site-level exposure: adjacent structures, vegetation, surface water

The first three live in Construction, and they're exactly the fields a desk underwriter can't verify without either trusting the application or sending someone to the curb. Loss control inspections do verify them, but they're slow and they don't scale to every renewal in a book, let alone every new submission.

How imagery fills in the construction field

This is where very high resolution overhead imagery does something a questionnaire can't: it shows you the roof as it exists today, not as it was described at binding five years ago. From imagery resolved fine enough to make out ridge lines, vents, and individual roof sections, you can read roof geometry, get a read on material, and count stories from shadow and footprint, all without waiting on a site visit.

That's the gap Property Characteristics is built to close: it pulls roof geometry, material, story count, and visible site features straight from the imagery and hands back a structured record per address, before you bind, so the construction fields in your file start from what the roof looks like rather than what the applicant typed.

Occupancy, Protection, and Exposure data still come from the application, ISO lookups, and loss control where it's warranted. Property Characteristics focuses on the one COPE field most prone to going stale: it gives you a current, address-level read on construction before the policy is bound, not after a claim shows the gap.

If construction is the field slowing down your file reviews, see what Property Characteristics can confirm before your next bind.