Use the Knowledge Checks Dashboard to understand how specific users are performing on their assignments and identify who needs follow-up.
Tracking Individual Assignment Performance
Start here when: You want to understand how specific users are performing on their Knowledge Check assignments, identify who needs follow-up, or audit compliance for a specific team or training program.
Knowledge Checks Assigned Table
This table gives you a user-level view of every Knowledge Check assignment. For each record you can see:
- User Name and User Email
- Knowledge Check
- Status (Not Started, In Progress, Passed, or Failed)
- Completed On
- Passed (True/False)
- Published On
- Total Questions Correct
- Total Questions Attempted
- Percentage Correct (with a visual progress bar)
What's the difference between Not Started and In Progress? Not Started means the user hasn't opened the Knowledge Check at all. In Progress means they've begun answering questions but haven't submitted it yet. Neither of these means the user failed — a Failed status only appears once the user has submitted the Knowledge Check and did not meet the passing threshold.
What to look for:
| Pattern | What It Means | Action |
|---|---|---|
| User with Not Started status on a required Knowledge Check | User hasn't opened it yet | Follow up directly — confirm they are aware of the assignment and know how to access it |
| User stuck on In Progress for several days | User started but hasn't submitted — may be stuck or have deprioritized it | Follow up personally to see if they need help or a reminder to finish |
| User with Failed status and multiple attempts | User is genuinely struggling with the content | Reach out personally — review the content together or recommend they revisit the relevant Speks before retrying |
| User with Passed status but low Percentage Correct | User passed but barely — comprehension may be shallow | Consider whether the passing threshold is set appropriately for this Knowledge Check |
| Multiple users failing the same Knowledge Check | A content quality issue rather than individual performance | Review the underlying content and Knowledge Check questions before following up with users |
Pro Tip: Filter by a specific Knowledge Check and sort by Status to quickly surface all Failed, In Progress, and Not Started records. This gives you an immediate action list without having to scroll through all passing results.
Best Practices
- Always check Total Questions Attempted alongside Status — a user with a Failed status who only attempted half the questions may have had a technical issue rather than a comprehension problem. Don't treat all Failed statuses the same.
- Use Published On to confirm users were assigned the most current version of a Knowledge Check before drawing conclusions, and review the content yourself before following up with users about failures — sometimes the issue is a poorly written question.
- Cross-reference users stuck in Not Started against the Activation Dashboard to confirm they are actively using Spekit, and treat a long-stuck Not Started status as urgently as a Failed one — a user who hasn't attempted a required Knowledge Check is still a compliance risk.