| Review a new vendor | The questionnaire and the certificate land on one record instead of an inbox. | Renewal dates and subprocessor changes are flagged before they lapse. | The certificate read against your requirements, with the gaps listed. |
| Run a privacy assessment | The assessment sits against the project and the supplier record it touches. | It cannot be signed off while a required section is missing. | Read section by section, with a grade and the reasons. |
| Check a contractor’s insurance | The certificate, the date, and the rule applied sit on the contractor’s record. | A lapsed certificate is flagged the day it happens, not the day it is disputed. | Read against your requirement set as it is uploaded. |
| Answer a regulator’s notice | Every check sits on one searchable record instead of four systems and a folder. | Filtered exports run by site and date, not rebuilt by hand. | Ask your assistant what was verified for a site or a contractor, through MCP. |
| Prepare the modern slavery statement | One verified contractor and supplier record serves procurement, risk, and legal. | Coverage is measured against the whole panel, not a manual sample. | Ask which suppliers are missing a current statement. |
| Respond to a subpoena or discovery notice | Every induction, licence check, permit, and sign-in has a name and a time against it. | Exported for the date range asked for, not searched for by hand. | Ask what a Worker or contractor was checked against, and when. |
| Track a subprocessor change | Every vendor’s subprocessor list sits on the same record as its certification. | A change is flagged the day it is notified, not the day someone asks. | Ask which vendors have changed a subprocessor this quarter. |
| Report to the board | One searchable record instead of a chase across four teams. | Live status straight into Power BI. | Ask in plain English through Claude, Claude Code, or GitHub Copilot; the answer comes from the record. |