.png)
Track learner, training, task, performance, and portals progress with detailed reporting, audit-ready records, and CSV exports.
Modules and programs record completions, scores, and certificates as learners work.
Module → learner → item. Find the weak content and the at-risk people.
CSV with timestamps, scores, and certificate dates so audit day becomes a download.
One table for the whole org: every learner, every module they've touched, and how it went.
Per-learner rollup - modules started, completed, passed, certificates earned, average score, last activity
Search by email, sort by any column
Date-range filters - last 7 / 30 / 90 days or all time
Per-module performance shows whether the content works - not just whether people clicked through it.
Completion & pass rates, started vs. finished
Score distribution in 10% bands — spot the too-easy and the too-hard
Certificates issued per module
Click a module for its learner table; click a learner for the full record - including the certificate itself.
Per-learner rows - started, completed, score, pass/fail, time to complete, items done
Certificate viewer one click from the table
Status filters - in progress, completed, passed, failed
Zoom out from single modules to whole onboarding tracks and public-facing portals.
Program progress - per-learner completion against due dates across every enrolled member
Portal analytics - visitor traffic, engagement, and the visit → module-start funnel
Tag rollups - e.g. completion across everything tagged "onboarding"
Two clocks, side by side: how long a card takes once it's moving, and how long it sat before anyone touched it.
Throughput by week - cards finished, not cards opened
Cycle time and lead time apart - a short cycle with a long lead time is a queue problem, not a speed problem
By board and by week, never by person - a task board isn't an employment record, so the per-assignee breakdown doesn't exist
Where every review has got to, how ratings are landing, and whether recognition reaches past the same four people.
Stage by stage - not started, in progress, awaiting a reviewer, returned, approved
Self against manager - the rating gap per department, and which way it leans
Small groups are withheld, totals included - so a team of three can't be identified by subtracting it from the rest
Before the term timetable goes out, filter to who's certified on which class format. The schedule gets built from the completion table instead of from memory.
New menu lands Monday; by Friday you can see which venues finished the training and which didn't, site by site, without ringing round managers.
Check who cleared the independence and AML refresh before busy season starts. One filtered table, exported straight into the file.
Drill from a practitioner's name to the certificate itself when an insurer asks who was cleared to run that device on that date.
Kim
Small Business Owner
Four segments: training analytics (learner progress, module and program performance, quiz scores, pass rates, time to complete, certificates), portal analytics (visitor traffic, engagement, and the funnel from portal visit to module start), task analytics (throughput by week, cycle and lead time, median age of open work by board, never by person) and people analytics (review progress, rating distribution, self-vs-manager agreement, KPI attainment, and recognition coverage). Every metric is computed from timestamped completion records.
It depends on the tab. Training and portal analytics are admin- and manager-only. Task flow is scoped to the boards you can already open, so the people doing the work can see their own team's throughput. People analytics carries its own permission for each of its two sections. performance and recognition, because "the people I review" and "the people I manage" are not the same set.
Yes. Per-module learner tables export as CSV - learner, start and completion timestamps, score, pass/fail, time to complete, items completed, and certificate date. That file is typically exactly what an auditor asks for.
Yes. The per-item breakdown shows completion rate, average score, and pass rate for each item in a module, plus abandonment analysis by last item completed - so you can find and fix the step where learners drop off.
No. Analytics is computed from the completion records Wikidoc already keeps every time a learner works through a module, no tracking snippets, no data pipeline, no configuration.
