The record

Who acknowledged it, who is pending, and when.

An acknowledgement is a named confirmation recorded against a person and a time. It is evidence that the message was confirmed, not proof it was understood or acted on, and the product says so.

AnnouncementUpdated hand-hygiene protocolPublished 1 September
  • Acknowledged178
  • Pending36
  • Of 214 asked83%
The 36

The ones still pending, by name.

Not a percentage to act on later. A list, with a button beside each person, and a limit on how often anybody can be chased.

Nursing84 of 96 · 88%

  • Amelia DawsonRegistered nurseAcknowledged 2 days ago
  • Phoebe GrantEnrolled nurseAcknowledged 2 days ago
  • Simon NaylorRegistered nursePendingRemind
  • Laura KentWard leadAcknowledged 1 day ago
Remind all 36 pending

At most one reminder per person every four hours, so the people who did their part are left alone.

Who it is for

Three people, and what each of them gets.

  • Dr Tessa PalmerHead of clinical governance

    Writes the protocol once and sends it to 214 people. She is one of the two roles that can see the tracker at all.

    Comms Admin
  • Laura KentWard lead, Nursing

    Chases the twelve people on her ward who have not confirmed, by name, instead of sending the whole hospital the same message a second time.

  • Megan NashExternal auditor, eight months later

    Asks what happened. Gets a document that states the rules behind every figure and names everybody counted in neither column.

What it holds

Five things, and the plan each one needs.

  • Per-post record

    Acknowledged and pending, by name, with the timestamp. The count is measured against active users, not seats.

    Every plan
  • Reminders to the people still pending

    Remind everyone pending in one click, or one person at a time, rate-limited to one reminder per person every four hours, so the people who did their part are left alone.

    Every plan
  • Required reading

    Mark a Knowledge Hub document as required, with a due date. Each person sees the document and the acknowledgement together, and late acknowledgements are marked as late.

    Every plan
  • Evidence pack

    For required reading, export who acknowledged what and when, as a printable report and a CSV for the auditor or the board. Every download is recorded against the requirement.

    HQ
  • Catch-Up

    What you missed since your last visit, with the announcements still waiting on you flagged first.

    Every plan
The limits

What the record does not say.

Every line here traces to something in the code, including the parts it would be easier to leave out.

  • It records the confirmation, not the understanding

    Somebody pressed a button and the time was kept. Where a comprehension check is attached, the answers they gave are stored alongside it. Neither is a statement about what a person understood, and Kayden Connect does not describe it as one.

  • Pending is not the same as never asked

    The roster separates three groups rather than one total: confirmed, still outstanding, and in no audience at all. That third group currently means one specific thing, which is that nobody set their department.

  • Only two roles can see it

    The tracker is visible to Super Admins and Comms Admins. Nobody else in the workspace sees who has confirmed and who has not.

  • 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 in one case it declines to produce a document at all: when the recorded population and the computed one disagree, it returns the reason instead of a number it cannot reconcile.

Ready when you are

See what happens after an important message is published.

Kayden Connect is invitation-only before launch. Tell us about your workforce and we will show you the demonstration workspace.

Request early access
  • By nameWho confirmed, and the time they did it.
  • Every planThe record itself. The evidence pack is HQ.
  • ExportableA printable report and a CSV, recorded when taken.