Not built yet

Where this is going, and what we are not promising

Nothing on this page exists yet. It carries no dates, because a date on a public roadmap is a commitment made to someone who has not asked for it. What already ships is on the platform page, and the two are kept apart on purpose.

AI-assisted policy drafting

Draft or adapt an internal policy from a starting point, then review and publish it yourself. The intent is to remove the blank page, not the human — a policy would still be authored, versioned and published by a person, exactly as it is today.

It would touch policy documents only. Harassment complaints, whistleblower reports, data-protection grievances, counselling content and wellbeing data stay sealed and stay outside it — those paths are closed by design, not by configuration.
It would not make compliance decisions. Deadlines, escalations, reattestation and coverage remain deterministic rules, because an auditor is entitled to an explanation that is the same every time they ask.
The privacy notice would be rewritten and reviewed by counsel before the feature reaches anyone. The current notice says the product contains no AI feature; that sentence changes first, or the feature does not ship.

The remaining statutory guides

Each of the nine statutes gets a full written guide — every obligation, deadline, register and penalty beside the provision it comes from. 1 of 9 are signed off and published so far; the rest are deliberately empty rather than filled with plausible text.

This is gated on legal review, not on engineering. A guide appears when a named reviewer has read it, and not before.

A console for partners and consultancies

Advisers who already run compliance for a portfolio of employers — PoSH consultancies, HR advisories, group functions — operating their whole book on the platform under their own brand, with each client isolated from the others.

The multi-brand foundation is built and tested: a client organisation inherits its adviser’s branding, and each one resolves its own privacy policy independently.
What does not exist yet is the console itself. Today a brand and its client organisations are configured by us, because there is no partner login — that is the part still to build, and we would rather say so than imply otherwise.
Client isolation is not negotiable and would not be relaxed to make this easier. An adviser would see their own clients and nothing across them.

More statutes, as configuration

The engine reads a statute as data rather than as code, so covering an additional Act is a content pack rather than a rebuild. That has been done once already without changing the engine.

Which Acts come next is a commercial decision, and we would rather add the ones customers actually carry than guess.

Why this list is short

Because it is the list of things actually being worked on. A longer one would be easy to write and would tell you less — and on a site whose central claim is that we do not publish statutory content we cannot stand behind, publishing product claims we cannot stand behind would be the same failure wearing different clothes.

If something you need is missing, that is worth a conversation rather than a guess on our part. We would rather build the obligation you actually carry.

Reviewed 2026-08-06