Platform · Public and professional liability

Public and Professional Liability Data

£2 million any one claim and £2 million in the aggregate are very different promises. So are claims-made and occurrence.

Public and professional liability data covers the published terms of public liability, professional indemnity and related covers. Two bases decide what a limit means: whether it applies any one claim or in the aggregate, and whether cover is triggered on a claims-made or occurrence basis. Both are recorded with every limit, from the documents. No quote is ever requested with an invented business; individual premiums are not collected.

A liability limit without its basis is a number without a meaning.

Get a free sample See sample data

Free pilot on your own Public and professional liability list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

liability_sample.jsonl LIVE FEED

{"cover_type":"professional indemnity","limit_of_indemnity":2000000,"limit_basis":"any_one_claim","trigger":"claims_made"} {"cover_type":"public liability","limit_of_indemnity":5000000,"limit_basis":"any_one_claim","trigger":"occurrence"} {"defence_costs_basis":"additional","coverage_opinion":null}

illustrative sample rows · GBwhat a limit means · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Public and professional liability or its owners. Public and professional liability and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Public and professional liability at a glance

How we handle Public and professional liability specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Scope: Public liability, professional indemnity, related
Limit basis: Any one claim or aggregate
Trigger: Claims-made or occurrence
So: Both recorded with every limit
Defence costs: Inside or in addition to the limit, as stated
Professional minimums: Where a regulator sets them, as published
Source: Wordings, IPIDs, SME products
Quotes: Never requested with invented businesses

Platform specifics

What a limit means

These are the reasons a Public and professional liability dataset needs its own handling rather than a shared retail schema.

Basis and trigger

Liability wordings set a limit of indemnity and then say how it applies. The same figure can cover each claim separately, or all claims in a year together; it can respond to claims made in the period, or events occurring in it.

limit_of_indemnity with limit_basis — any_one_claim or aggregate — as stated.
trigger — claims_made or occurrence — as stated, with the wording reference.
defence_costs — inside or in addition to the limit — as stated.
Retroactive dates and run-off terms recorded where published.

Professional minimums, and what we do not do

Regulatory minimums

Some professions have minimum cover set by their regulator. Where published, the requirement is recorded as the regulator's, beside product terms, never as a product feature.

Against property cover

Most SME packages combine liability with property — see our commercial property page.

What we do not do

Record a limit without its basis, request quotes with invented businesses, interpret whether a claim would be covered, or collect policyholder or claims data.

Scope

What we collect on Public and professional liability, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

limit_of_indemnity with limit_basis
trigger: claims-made or occurrence
Defence costs basis as stated
Retroactive and run-off terms where published
Regulatory minimums as the regulator's
Excess as stated
Key exclusions with page references
Document versions tracked
No invented quote requests, ever

❌ What we do not, and why

A limit recorded without its basis
Quotes requested with invented businesses
Coverage opinions on any claim
Regulatory minimums presented as product features
Policyholder or claims data

Core Public and professional liability fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
insurer / product / cover_type	As published
limit_of_indemnity	As stated
limit_basis	any_one_claim or aggregate
trigger	claims_made or occurrence
defence_costs_basis	inside or additional
retroactive_terms / run_off_terms	Where published
excess	As stated
key_exclusions	With page reference
regulatory_minimum	The regulator's, where published
doc_version / source_ref	Document and page
observed_at	Timestamp

Use cases

What teams do with Public and professional liability data

Like-for-like limit comparison

Limits compared only on the same basis and trigger.

Professional indemnity benchmarking

Terms across insurers for a profession.

Package product design

How SME packages set liability limits.

Wording change tracking

When bases or exclusions change.

The 24-hour sample — run on your sources, not ours

Send us a Public and professional liability item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Public and professional liability is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Public and professional liability data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what insurance data covers, and a Public and professional liability-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Public and professional liability data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Because any-one-claim and aggregate limits of the same size are very different amounts of cover.

Whether cover responds to claims made during the period or events that occurred in it. We record it as the wording states.

Yes: inside or in addition to the limit, as stated.

No. We record terms, not coverage opinions.

No. We never invent businesses to request them.

It depends on insurers and products.

Talk to us.

See real Public and professional liability data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner