Hero, locked structure

Healthcare onboarding and compliance, automated.

Automate pre-employment checks, credentialling and ongoing compliance monitoring on one platform built exclusively for healthcare. Platform-managed onboarding drops from 60 days to as few as 5, with external checks running in parallel from day one.

Two changes from the submitted copy. "Exclusively" restored, because the tagline guardrail protects the healthcare-only idea and that is the word carrying it. "An industry average of 60 days" removed, because Messaging Principle 8 requires the platform-managed qualifier and forbids implying total elapsed time.

Open: the number. Messaging House v5 says 5. The 11 July framework says 6, marked provisional, and that is the version Hamish holds. Terence's sourced customer figures support neither directly. If the answer is 6, this line becomes "drops from 60 days to 6" with nothing else changed.

Section 2, title above the four buckets

Healthcare compliance that runs itself.

Documents read and verified, registrations checked daily, requirements built around your roles and sites. The platform does the work, and your team approves what matters.

Option A, and the only approvable option. The tagline guardrail requires every variant to hold both the automation idea and the healthcare-only focus. Option B, "An AI workforce for compliance", drops healthcare and leads on the technology label, which Messaging Principle 4 bans and which was the framing dropped on 11 July as undifferentiated. Option C drops both.

DOCUMENTS AND REQUIREMENTS

Every document read and matched to its requirement.

Drop in a folder and each file is classified, dated and matched to the requirement it satisfies, including DBS, Right to Work and registration with the GMC, NMC and HCPC. What passes is approved. What is missing is listed.

Option A repaired. Title triplet "read, checked and filed" replaced with the matching, which is what actually distinguishes the product. Em dash removed.

AI AGENTS AND CHAT

Agents do the chasing. You approve the decisions.

Agents chase candidates, verify registrations and write the messages. Chat answers questions about anyone on your books, in plain English. Every action is logged, and a person approves anything that counts.

New option D. All three submitted headlines used the banned contrastive construction, so there was nothing to pick. This one leads with what the AI does rather than what it is, per Messaging Principle 4. Tag kept as agents and chat, because those are functions; "AI across the platform" and "AI throughout" describe the technology's presence.

REAL-TIME COMPLIANCE

Registers checked daily, evidence ready for inspection.

The GMC, NMC and HCPC registers and the DBS Update Service are re-checked continuously, with alerts before anything lapses. Every check is logged, so the evidence is ready before an inspector asks for it.

Option A repaired. "Evidence ready always" was inverted and absolute. Options B and C both overclaimed: "You'd never miss an expiry again" is an absolute about a regulated outcome, and "Compliant today, and provably so" asserts the customer is compliant, which the platform cannot warrant.

CUSTOM COMPLIANCE PACKAGES

One package per role, site or client.

Requirements assemble from role and location. Packages stack and cross-reference, so evidence verified once counts towards the next. Toggle anything on or off without rebuilding.

Option A, clean as submitted. Option B's "Your rules, not a template" was contrastive. "Flexible compliance" stays off the tag list, per the 30 July decision.

Open: GPhC and GDC. Registers on this page are GMC, NMC and HCPC only, per Terence. Note that GPhC and GDC are named as live integrations in four places in the locked set, including a Messaging House v5 exemplar sentence. If Terence is right, that needs correcting at source, not just here.

Section 3, heading above the six features

Built around the checks you actually run.

DBS and Right to Work, references, signatures, expiry alerts and audit evidence: the parts of compliance that take up the most time.

Option B, agreeing with the source document. The em dash becomes a colon, which suits the list better than the dash did. The current subtitle promising the full lifecycle should go either way: only one of the six features maps to it, and it repeats "pre-employment checks", which now sits inside bucket 1.

Pre-employment checks

Identity, Right to Work and DBS. The DBS Update Service tracks status from then on. DBS, occupational health and overseas qualification checks run in parallel to their own timelines.

Hyphen added. Final sentence added to carry the Principle 8 qualification where a buyer will look for it.

AI email agent

Emails written for each person, covering what has changed and what they still need to do. Triggered by an expiry, a milestone, or any action you set.

Em dash removed. Not on the v5 live-capability list, so Principle 7 requires product sign-off before it ships as a headline feature.

Multi-site dashboard

Compliance status for every location and organisation in one view.

Unchanged. Covered by the house as a live capability.

eSignature

Documents signed in the platform, with an audit trail. No separate licence.

Renamed from "E-signature" to match the house and the product.

Audit export

Export the evidence for any candidate or date range. Formatted for CQC inspection.

"Approved by Neuven" removed pending written sign-off. Neuven are not on the approved named-customer list.

Reference tracking

Every reference from request to submission to review, with the time taken at each stage.

Unchanged. Reference calling stays out, per Terence, and it is absent from the v5 live list.

Not fixed here, because it is a page-structure question

Pillars 1 and 2 have no section on this page.

The four buckets map to Pillar 3 twice and to nothing twice. Pillar 1, healthcare-only depth, survives only as the words "built exclusively for healthcare" in the hero. Pillar 2, continuous development, does not appear at all. The framework says these two are what build conviction, and that the default sequence for a new visitor is platform first, outcomes second.

The copy-level fix is the word "exclusively", restored above. The page-level fix is the "Built for healthcare" section already agreed on 22 July, placement after Outcomes and before Platform, which was never built.

Still to resolve before this copy is final. One, the onboarding figure, 5 or 6, and whether the named-customer attribution stands. Two, GPhC and GDC. Three, Neuven sign-off in writing on the audit export format. Separately, the live site lists data residency as US, EU and Canada with no UK, while the brand card lists London as an offered region.