Publishing information to your team and knowing your team has received it are two different problems. Most tools solve the first and ignore the second.
A shared document, a Slack message, and an email all deliver information in the sense that the information becomes available. They don’t tell you whether anyone opened it, read it carefully, or understood it well enough to act on it. For casual updates that distinction doesn’t matter much. For a policy change, a safety procedure, or a compliance requirement, it matters a great deal.
This is the problem completion tracking solves.
Why “available” isn’t the same as “received”
When information is published somewhere a team member could theoretically access it, the organization has done half the job. The other half is knowing that the right people actually got it.
The gap shows up most clearly during onboarding. A new hire is given access to a folder of documentation. Two weeks later it becomes clear they missed something important. The documentation was there. Nobody knew it hadn’t been read.
It also shows up with policy updates. A procedure changes. The updated document gets shared. Months later an issue surfaces that traces back to someone operating on the old version. The update was sent. Nobody knew who had seen it.
The common thread is that availability was treated as receipt. The two are not the same.
What completion tracking requires
For tracking to mean anything, three things need to be true.
- The content has to be assigned to specific people. Tracking completion only works if there’s a defined list of who is expected to complete what. A document published to a shared folder has no assigned audience, which means there’s no baseline to measure against.
- Completion has to be an explicit action. A team member reading a document in a browser tab is not a trackable event. Completion tracking requires a moment where the person indicates they have finished, such as a button, an acknowledgment, or a quiz. That action creates the record.
- The record has to be visible to someone. Completion data that exists but isn’t surfaced anywhere doesn’t change how managers operate. The tracking has to produce something a manager can actually see and act on.
How Keystone handles this
Keystone’s Required Modules are built around this problem. Content is organized into Modules and assigned to specific team members. Each Item inside a Module has a completion action like a Mark Complete button, an acknowledgment requirement for documents and policies, or a knowledge check for content where understanding matters. When a team member completes an Item, that completion is recorded against their account.
Managers see completion status at two levels. The Reports page shows completion rates across all Required Modules for the whole team. The Member Profile page shows exactly where a specific person stands by displaying which Modules are complete, which are in progress, and which haven’t been started. Due dates surface when something is overdue.
The result is that “did your team read the new policy” has a factual answer rather than an assumed one.
What this is not
Completion tracking is not surveillance. It doesn’t record how long someone spent on a page or whether they read carefully. It records that a person indicated completion of a specific piece of content. That’s a meaningful signal, not a comprehensive audit trail.
It also doesn’t replace good content. A team member who clicks through a Module without engaging with it will show as complete. Tracking creates accountability; it doesn’t substitute for content worth reading.
For most small teams, that’s exactly the right level of rigor. The goal is to close the gap between “we published it” and “we know the team received it,” not to build a surveillance system.
Getting started
If your team runs WordPress, Keystone adds completion tracking directly inside wp-admin using the user accounts already there. Required Modules handle assigned, tracked content. Reference Modules handle open-access material that doesn’t need that overhead. Both live in the same place.
The features page covers how the assignment and tracking system works in detail.