Who has confirmed it. And who you never reached.
An admin can require a Knowledge Hub article to be read and confirmed by a targeted audience with a deadline, and see by name who has confirmed and who has not.
Creating, publishing, confirming, chasing and superseding work on every plan, including the cheapest. The roster CSV and the evidence pack need HQ.
- Confirmed178
- Outstanding36
- In no audience9
Nine people have no department. A requirement targeted at departments never reached them, and nothing else in the product would have said so.
One total hides three different problems.
The roster separates three groups rather than one total: the people who have confirmed, the people still outstanding, and the people who are in no audience at all, so a requirement targeted at departments cannot report full coverage while nobody has noticed the staff it never reached.
223active people. The audience rules selected 214 of them.
- 178ConfirmedPeople who have attested. Anyone who has since left the organisation stays counted.79.8%
- 36OutstandingActive, inside the audience, and no confirmation yet. This is the chase list.16.2%
- 9In no audience at allActive, and selected by none of your rules. Today that means no department is set on them.4.0%
The nine are reported separately because an admin who targets departments, and sees full coverage while nine people have no department, has a number that is true and badly misleading. Chasing the outstanding is one button with a cooldown rather than a mail-merge to everybody.
Three people, and what each of them gets.
- Dr Tessa PalmerHead of clinical governance
Marks the revised protocol as required, picks the audience and the date, and never has to work out by hand who is missing.
Comms Admin - Simon NaylorRegistered nurse
Confirms on his own phone at the end of a shift. He joined with an access code and has no company mailbox, and confirming is open to every member.
- Megan NashExternal auditor, eight months later
Asks which version was in force in August and who confirmed it. The roster carries the period and where each end of it came from.
Five things, and the plan each one needs.
- Require a document, with a date
Point a requirement at a Knowledge Hub article, choose who it applies to, and set the day it is due.
Every plan - Anyone can confirm
Confirming is open to every member, including a frontline worker who joined with an access code and has no company mailbox.
Every plan - Chase only the outstanding
One button for everybody still outstanding, rate-limited, so the people who did their part are left alone.
Every plan - Superseded, never edited
Replacing a policy retires the old requirement and creates a new one, so everybody confirms again against the wording they actually agreed to. It is the single operation that turns a satisfied obligation into an unsatisfied one for everybody at once, and it is recorded as such.
Every plan - The roster CSV and the evidence pack
Export the roster for management, or produce the document you hand an auditor. Every pack is recorded before the file is served.
HQ
What required reading does not say.
Every line here traces to something in the code, including the parts it would be easier to leave out.
- It is a document and a confirmation
A requirement points at one article in the Knowledge Hub and asks a person to confirm they have read it. There are no lessons, no modules and no syllabus, and nothing here is sold as one.
- Two roles author it
Creating, publishing, chasing and superseding are limited to Super Admins and Comms Admins. Everybody else can confirm, and that is all they can do.
- In no audience means one specific thing
Today it means the person has no department set. It is one kind of gap, reported honestly, and not a guarantee that every kind of gap has been found.
- The pack is a record, not an assurance product
There is no hash chain and no signing behind it. It states what the system holds, and it declines to produce a document at all when the recorded population and the computed one disagree.
What sits either side of a requirement.
- The recordThe same confirmation on a single announcement, without an audience rule or a due date behind it.
- Knowledge HubWhere the documents you make required actually live, and where people read them.
- Admin and the audit logWhere superseding a requirement is written down, along with everything else an admin does.
See it against your own policies.
Kayden Connect is invitation-only before launch. Tell us about your workforce and we will show you the demonstration workspace.
Request early access- Every planRequiring, confirming, chasing and superseding.
- HQThe roster CSV and the evidence pack.
- Three figuresConfirmed, outstanding, and never asked at all.