Checkpoints

A checkpoint is a single, verifiable unit of competency within a responsibility’s checklist. Each checkpoint defines something an employee must be able to do: not what they’ve learned, but what they can demonstrably perform.

​

What is a checkpoint?

Every checkpoint is written with one of four fixed prefixes, which sets the type of evidence required: A checkpoint can also include a microlearning: a short video or article that teaches the employee what they need to know before being assessed. Depending on how the checkpoint is set up, it can also have a quiz, an inspection, or both.

​

What checkpoints are used for

Checkpoints are the building blocks of Readiness. Together they form the inspection checklist for a responsibility: the set of criteria a Coach uses to certify that an employee is ready. Checkpoints serve three purposes:

1. Learning: the microlearning prepares the employee before inspection.
2. Assessment: the criteria define exactly what the Coach inspects for.
3. Evidence: once passed, a checkpoint contributes to the employee’s Readiness for that responsibility and becomes part of the permanent record.

Within a responsibility, checkpoints are organized by Readiness level (Apprentice → Proficient → Coach → Architect) and by sequence within each level. Employees progress through them in order.

​

Checkpoint lifecycle

​

Checkpoint operations

​

Create a checkpoint

From a responsibility’s checklist, click + Add Checkpoint. Choose the type of microlearning to attach, or choose No learning content needed for an inspection-only checkpoint. The checkpoint is created in Draft and isn’t visible to employees until you activate it. See Editing a checkpoint for the starting options in detail.

​

Edit a checkpoint

Open the checkpoint in the checklist and click Edit to take the edit lock. While it’s in Draft you can update the criteria, the microlearning, the quiz, and the inspection. Only one person can hold the edit lock at a time. If someone else is editing, the checkpoint shows as locked.

​

Activate a checkpoint

When a Draft checkpoint is complete, click Activate to publish it. It becomes Active and visible to employees and Coaches. Activate is only available when the checkpoint meets all requirements: complete criteria, and microlearning ready if it’s required.

​

Publish changes to an active checkpoint

To update an Active checkpoint, start a draft of your changes, make your edits, then click Publish. You’ll be asked for a short note describing what changed, and whether existing employee inspections should be marked obsolete. See Editing a checkpoint for how proposed changes work.

​

Retire a checkpoint

Retire removes a checkpoint from active use. It’s no longer used in new inspections, but its history is preserved. You can Reactivate a Retired checkpoint.

​

Archive a checkpoint

Archive a Retired checkpoint to fully decommission it. You can Unarchive it back to Retired. There’s no direct path from Archived to Active.

​

Discard a draft checkpoint

Discard Draft permanently deletes a checkpoint that’s still in Draft. This isn’t available while another user holds the edit lock.

​

Move a checkpoint to another responsibility

You can move a checkpoint to a different responsibility while keeping its full history, status, and existing inspection records. Open the checkpoint’s menu and select Move to Responsibility.

​

Change a checkpoint’s level or order

In a responsibility’s checklist, drag and drop checkpoints to reorder them within their Readiness level. To move a checkpoint to a different level (for example, from Apprentice to Proficient), use the level selector on the checkpoint header.

​

Bulk actions

Bulk actions let you apply the same operation to many checkpoints at once, which saves time on large checklists.

​

Select multiple checkpoints

In the responsibility’s checkpoints table, check the box next to each checkpoint you want, then open Bulk Actions. The button shows how many checkpoints are selected.

​

Available bulk actions

​

Related