Platform · Public complaints publications

Insurance Complaints Data

The regulator publishes complaint numbers for large firms. The ombudsman publishes its decisions without the complainant's name. Both are useful; neither is a person.

Insurance complaints data covers published complaints information: the FCA's firm-level complaints data, published half-yearly for firms reporting 500 or more complaints in a half-year, and Financial Ombudsman Service decisions, which name the business but not the complainant. Figures are recorded as published, with the threshold stated, and no attempt is ever made to identify a complainant.

Complaints data is powerful and easy to misuse. Most of the discipline is in what it does not cover.

Get a free sample See sample data

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

complaints_sample.jsonl LIVE FEED

{"source":"fca_firm_level","period":"2025-H2","product_group":"general insurance","opened":1240} {"coverage_note":"firms with 500+ complaints in the half-year only"} {"source":"ombudsman_decision","business_named":"as published","outcome":"upheld","complainant_identified":false}

illustrative sample rows · GBwhat the numbers cover · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Public complaints publications or its owners. Public complaints publications 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 complaints publications at a glance

How we handle Public complaints publications specifically

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

FCA data: Firm-level, half-yearly
Threshold: 500+ complaints in the half-year
So: Smaller firms absent — stated
Ombudsman: Decisions; business named, complainant not
Decisions from: April 2013
Re-identification: Never attempted
Outcomes: As published: upheld or not
Refresh: Each FCA release; decisions weekly

Platform specifics

What the numbers cover

These are the reasons a Public complaints publications dataset needs its own handling rather than a shared retail schema.

Firm-level data, with its threshold

The FCA publishes complaints data for firms that report at least 500 complaints in a half-year, by product group, with opened, closed and upheld figures.

period, firm and product_group as published.
opened, closed, upheld and any rates as published; our own rates are labelled derived fields.
coverage_note on every dataset: firms below the threshold are absent, not complaint-free.
Group reporting recorded as the publication presents it.

Ombudsman decisions, and what we do not do

Ombudsman decisions

The Financial Ombudsman Service publishes final decisions, naming the business but not the person complaining. Recorded: decision reference, date, business, product, complaint category and outcome as published. Decision text is archived for search, not republished.

No re-identification

Decisions can contain details of someone's circumstances. We never attempt to identify a complainant, never join decisions to other data about people, and exclude details that describe an individual's health.

What we do not do

Present absent firms as complaint-free, re-identify complainants, republish decision text, or collect any policyholder data. Regulatory action is covered separately on our enforcement notice page.

Scope

What we collect on Public complaints publications, 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

FCA firm-level figures as published
Threshold stated on every dataset
Product groups as published
Derived rates labelled
Ombudsman decision metadata: reference, date, business, outcome
Decision text archived, not republished
Health details in decisions excluded
Group reporting as presented
Refresh on each release

❌ What we do not, and why

Firms below the threshold presented as complaint-free
Any attempt to identify a complainant
Joining decisions to data about people
Decision text republished
Policyholder data

Core Public complaints publications fields

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

Field	What it is on this platform
source	fca_firm_level or ombudsman_decision
period / firm / product_group	FCA data
opened / closed / upheld	As published
rate_published / rate_derived	As published; labelled
coverage_note	Threshold statement
decision_ref / decision_date	Ombudsman
business_named	As published
product / complaint_category	As published
outcome	Upheld or not, as published
archive_ref	Decision text, for search
observed_at	Timestamp

Use cases

What teams do with Public complaints publications data

Complaints benchmarking

Large firms compared by product group, threshold stated.

Ombudsman outcome analysis

Upheld rates by business and category.

Product risk research

Which product types attract complaints.

Trend tracking

Half-yearly series across releases.

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

Send us a Public complaints publications 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 complaints publications is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Public complaints publications 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 complaints publications-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 complaints publications data scraping: frequently asked questions

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

Firms reporting 500 or more complaints in the half-year. Smaller firms are absent, and we say so.

No. They name the business. We never attempt to identify the person.

No. Metadata is recorded and text archived for search.

Yes, as labelled derived fields beside the published figures.

No, they are excluded.

It depends on sources and history.

Talk to us.

See real Public complaints publications 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