SiteVerdict — UK Modern Slavery Statement Registry Search avatar

SiteVerdict — UK Modern Slavery Statement Registry Search

Pricing

Pay per event

Go to Apify Store
SiteVerdict — UK Modern Slavery Statement Registry Search

SiteVerdict — UK Modern Slavery Statement Registry Search

Search the official UK Home Office Modern Slavery Statement Registry (open data, OGL) by company, sector or turnover, score statement completeness, check supplier lists for missing or outdated statements and monitor changes with alerts.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Aman Thakran

Aman Thakran

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Find out in one run which of your suppliers have a current modern slavery statement on the UK Home Office registry, which are missing or out of date, and what each statement actually covers. Then keep watching them on a schedule.

Not legal advice. The registry is self-reported and, for most private companies, submission is voluntary. A supplier that is not on the registry may still have published a compliant statement on its own website. Always check the statement itself before drawing conclusions.

What it does

The Actor reads the official Modern slavery statement registry open data published by the Home Office (one CSV per statement year, updated daily, Open Government Licence v3.0). It never scrapes search pages.

It runs in three modes:

ModeYou giveYou get
searchFilters: organisation name, company number, sector, turnover band, public/private, group submissions, "missing areas", completeness score, updated sinceOne row per statement with the six-area coverage, risks reported, policies, training, audits, grievance mechanisms, links to the registry summary, the statement and the PDF
supplier-checkYour supplier list (name and/or Companies House number)One row per supplier: FOUND_CURRENT, FOUND_OUTDATED, POSSIBLE_MATCH, NOT_FOUND or INVALID_INPUT, how it was matched (company number, exact name, group parent, fuzzy), years on the registry, completeness score and flags
monitorThe same supplier list, run on a scheduleOnly what changed since the last run (new statement, updated statement, now found, no longer found, became outdated, score change), with a Slack / webhook alert

Every statement also gets a transparent completeness score (0–100) and plain-English flags. The score covers what the organisation reported to the registry; it is not a legal assessment.

  • Six areas (72 points). The six areas in s.54(5) Modern Slavery Act 2015 are organisation structure, policies, risk assessment, due diligence, training, and goals/KPIs. Each area covered earns 12 points.
  • Approval date recorded (8 points).
  • Link to the full statement (8 points).
  • Roughly 12-month reporting period (4 points).
  • Specific risks reported (4 points).
  • Progress or ILO indicators (4 points).

The flags are:

FlagMeaning
MISSING_AREASOne or more of the six areas is not covered.
NO_STATEMENT_URLNo link to the full statement on the organisation's website.
NO_APPROVAL_DATENo board or approval date recorded.
LATE_PUBLICATIONApproved more than 6 months after the period end.
PERIOD_NOT_12_MONTHSThe reporting period is not roughly 12 months.
STALE_PERIODThe reporting period ended more than 24 months ago.
NO_RISKS_REPORTEDNo specific modern slavery risks were reported.
VOLUNTARY_UNDER_THRESHOLDTurnover is under £36m, so the statement is likely voluntary.

Who it is for

  1. Procurement and supplier-onboarding teams. Run your supplier master list once a quarter and see who needs chasing.
  2. ESG, sustainability and compliance analysts. Benchmark a sector: for example, retail statements that miss due diligence or training, or companies over £500m with low scores.
  3. Consultancies, auditors and journalists. Pull clean, analysis-ready data with registry links in seconds, instead of downloading and cleaning 18 MB CSVs by hand.

AI agents can use it too, through the SiteVerdict MCP server (see MCP-TOOL.md).

Example: supplier check

Input:

{
"mode": "supplier-check",
"suppliers": [
{ "ref": "sup-001", "name": "Acme Widgets Ltd" },
{ "ref": "sup-002", "name": "Beta Foods plc", "companyNumber": "SC123456" },
{ "ref": "sup-003", "name": "Gamma Holdings PLC" },
{ "ref": "sup-004", "name": "Unknown Supplier Ltd" }
]
}

Before: a spreadsheet of supplier names and a browser tab on the registry search page.

After: one row per supplier (shortened):

refsupplierstatusmatched byyearsareasscoreflags
sup-001Acme Widgets LtdFOUND_CURRENTexact-name2024, 20256/6100–
sup-002Beta Foods plcFOUND_OUTDATEDcompany-number20234/668MISSING_AREAS, STALE_PERIOD, NO_RISKS_REPORTED
sup-003Gamma Holdings PLCFOUND_CURRENTparent-name (group statement)20256/696–
sup-004Unknown Supplier LtdNOT_FOUND––––"does NOT prove non-compliance: check their website"

A live check on 11 Oct 2026 matched "Marks and Spencer Group plc" to the registry entry MARKS AND SPENCER P.L.C. (5 of 6 areas, score 84). It also found Tesco PLC (score 96) and J Sainsbury plc (score 100). 2025 and 2026 together came to 24,788 registry rows, loaded in about 12 s.

Try it free with "sampleMode": true. Sample mode uses a bundled synthetic file with the registry's real column layout, makes no network calls and charges nothing.

{ "mode": "search", "sectors": ["Retail"], "turnoverBands": ["Over £500 million"], "onlyMissingAreas": true, "years": ["2025"] }

Output

  • Dataset. Views: Statements, Supplier check, Changes since last run. Export as CSV, Excel or JSON.
  • Key-value store:
    • REPORT: an HTML report you can share;
    • STATEMENTS.csv or SUPPLIERS.csv;
    • SUMMARY: agent-ready JSON with the years loaded, totals, alert delivery results and the data source and licence.

Monitoring and alerts

  1. Schedule the Actor (for example weekly) in monitor mode with your supplier list.
  2. The first run records a baseline in a named key-value store (stateStoreName).
  3. Later runs report only changes and post them to your Slack incoming webhook and/or an HTTPS webhook (both stored as secrets, never logged).

Pricing (pay per event)

EventWhenProposed price
statement-recordeach statement returned by a search$0.002
supplier-checkedeach valid supplier checked (any status, including NOT_FOUND)$0.01
change-alerteach supplier with a real change in monitor mode (never the baseline)$0.02

Examples:

  • 100 suppliers checked ≈ $1.00.
  • A search returning 500 statements ≈ $1.00.
  • Monitoring 200 suppliers weekly with about 5 changes a month ≈ $8.10/month.

Invalid inputs, failed downloads and sample-mode runs are never charged, and the run stops at your maximum total charge.

FAQ

Is a supplier missing from the registry breaking the law? Not necessarily. Section 54 requires commercial organisations with £36m+ turnover that do business in the UK to publish a statement on their website. Registry submission is voluntary for most companies. Treat NOT_FOUND as "ask the supplier", not as a finding.

How accurate is matching? Company number is exact. Name matching ignores case, punctuation and legal suffixes, then checks group parents. Anything fuzzy is labelled POSSIBLE_MATCH with a similarity score so a human can confirm it. Give company numbers where you can.

Which years are loaded? By default:

  • search: the latest year (if the latest year is still nearly empty, fewer than 1,000 statements, the previous year is loaded too);
  • supplier-check and monitor: the latest 3 years, so older statements show as FOUND_OUTDATED.

Set years to choose your own.

Do you output personal data? The registry publishes the name and role of the person who approved each statement. We drop it by default (includePersonalData: false). Organisation addresses are business addresses.

How fresh is the data? The Home Office regenerates the files daily. Each run downloads the current files, about 8–19 MB per year.

Limits

  • Data is only as good as what organisations submitted. Answers are self-reported and not verified by the Home Office or by us.
  • Fuzzy matching only compares names that share their first significant word. Unusual trading names may need the company number.
  • Each yearly file is downloaded per run, about 1–3 minutes for several years. Use years to limit it.
  • The completeness score is our heuristic, explained above. It is not the Home Office's view and not legal advice.

Sources & compliance

  • Source: Home Office, Modern slavery statement registry open data, from https://modern-slavery-statement-registry.service.gov.uk/download. The files are https://downloads.modern-slavery-statement-registry.service.gov.uk/publicdownloads/StatementSummaries<YEAR>.csv. Checked 11 Oct 2026: the data is updated daily.
  • Licence: Open Government Licence v3.0 (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Every row carries the attribution: Contains public sector information licensed under the Open Government Licence v3.0 (Home Office, Modern slavery statement registry). Commercial re-use is permitted under OGL v3.0 with attribution.
  • Access: we download only the published open-data files, with an honest User-Agent (SiteVerdict/uk-modern-slavery-statements (+aman.thakran@bharatfare.com)). robots.txt is respected, retries are polite and nothing is scraped behind a login.
  • UK GDPR: the approver's name is personal data published by the registry. It is off by default (data minimisation). If you enable it, you are the controller for your use and need a lawful basis, typically legitimate interests for supply-chain due diligence. PECR does not apply: we send no marketing communications.
  • Legal context: see Modern Slavery Act 2015 s.54 and the Home Office statutory guidance Transparency in supply chains: a practical guide.

Made by SiteVerdict, Aman Thakran / BharatFare Travel and Technologies Ltd (UK). Contact: aman.thakran@bharatfare.com.