Start with the question you're trying to answer, then work back to the report. This is a decision guide for admins choosing between Admin Reports, Content Analytics, Continu Insights, and Report Builder.

What Are You Trying to Measure?

Continu reporting fragments across four surfaces because different questions call for different tools. Before picking a report, decide what you're actually trying to answer. Most reporting questions fall into one of five categories:

• Compliance — who has and hasn't completed required training. Usually needs a per-row CSV for audit hand-off.
• Program outcomes — how a specific Track, Journey, or Workshop is performing. Usually answered in the analytics tab on that program.
• Engagement patterns — what content is being consumed, where learners drop off, which cohorts are most active. Usually needs interactive exploration.
• Learner behavior — what a specific learner or cohort has done, when, and how far they got. Can go either way depending on the question.
• Executive / board reporting — trends over time, outcomes across the org, dashboards for a leadership review. Usually needs live dashboards.

Pin down which category your question falls into before opening any tool. It saves you from running the wrong report and having to start over.

The Four Reporting Surfaces

Continu has four places to get data. Each does one thing well and other things poorly.

Admin Reports (Admin > Reports). Pre-built CSV reports. Assignment Status, Track Progress, Workshop Attendance, Content Engagement, and more. Use when you have a well-defined question, need per-row data, or need to hand a spreadsheet to compliance / audit / another system.

Content Analytics (the analytics tab on individual Tracks, Journeys, Workshops, and content items). In-context views scoped to that one piece of content. Use when you want the answer for a specific program — "how's this Track doing" — without exporting anything.

Continu Insights (paid add-on — talk to your CSM). Interactive dashboards with filters and drill-down. Use when you want to explore patterns, share a live view with stakeholders, or click from "the number" to "the people behind it." Not a replacement for Reports; a complement.

Report Builder (Admin > Reports > Report Builder). Custom CSV reports built with the fields and filters you pick. Use when the standard Admin Reports don't cover your question but you know exactly what fields and filters you need.

Decision Matrix: Question → Surface → Report

The most useful thing a reporting reference can do is map real questions to real reports. Here's the map. If your question isn't on this list, decompose it — most are combinations of these.

Track Reporting: Which Report Shows What

Tracks are the most common source of "which report do I use?" confusion because three different reports show Track-related data and they don't agree on the numbers — because each is measuring something different. Here's what each measures.

Track Status Report (Analytics on the Track page)

Measures learners actively working through the Track. If a learner hasn't started, they don't appear here at all. Use this for engagement questions: "of the people who've begun the Track, how far along are they?"

Assignments Analytics Report (Analytics on the Track page)

Scoped to the specific assignment instances tied to that Track view. Shows only active assignment recipients — the learners currently assigned via that Track's assignment(s). Use this for "of the learners currently assigned to this Track, what's their status?"

Assignment Summary Report (Admin > Reports)

Aggregates across every assignment instance that has ever included this Track — older assignments, automation-generated assignments, re-assignments, all of them. Use this for "across all times this Track has been assigned, what's the aggregate picture?"

Why the numbers differ

The three reports have different scopes:

• Track Status includes only people who've started.
• Assignment Analytics on the Track view includes everyone in the current assignment(s), whether or not they've started.
• Assignment Summary in Admin > Reports includes everyone across every historical assignment.

If you compare "assigned users" across the three reports for the same Track, you'll see three different numbers — and that's correct behavior.

Which one to run

• "Who hasn't started yet?" → Assignment Analytics on the Track view, filtered to Not Started.
• "Who's actively in progress?" → Track Status Report, filtered to In Progress.
• "How's this Track performed overall, historically?" → Assignment Summary Report from Admin > Reports.
• "Who completed the current cycle?" → Assignment Analytics on the Track view, filtered to Completed.

Pick the report that matches the question being asked, not the report you happened to open first.

How Metrics Are Calculated

Continu computes reporting metrics from assignment state, completion events, and time stamps. Understanding these definitions prevents most report-vs-report reconciliation confusion.

Assignment state — each assigned learner is in one of these states: Not Started, In Progress, Completed, Expired. State transitions on assignment events (created), start events (learner opens the content), completion events (learner meets the completion criteria), and time-based transitions (Expired).

Completion — means the learner met whatever completion criteria the content requires. For an Article, that's typically opening it (or scrolling to the end, depending on config). For a Video, playback percentage. For an Assessment, a passing grade. For a Workshop, attendance. Reports report the completion event; how it was earned depends on the content type.

Percent complete — only meaningful for multi-item content (Tracks, Journeys). Calculated as items completed ÷ items required. Items that aren't required don't count toward the percentage.

Time to complete — measured from first-open to completion event. Not from assignment date. Reports also expose assignment-to-completion for compliance-style questions.

Attendance — for Workshops, calculated from the video conferencing integration's attendance signal. If the integration isn't configured, attendance falls back to registration + manual marking, which is less reliable.

The Anatomy of a Report

Every Continu report has three dimensions worth naming:

Scope — who's included. A report scoped to an assignment includes only assignees. A report scoped to a Track includes anyone who's touched the Track (per report definition). A report scoped to a segment includes everyone matching the segment. The scope drives the row count and is the first thing to check when a number looks wrong.

State filter — which assignment state(s) are included. Not Started, In Progress, Completed, Expired. Most reports let you filter to one or more states. "Completion rate" is scope-dependent: it's completed divided by scope-included, not divided by everyone in the org.

Time filter — the date range applied. Assignment date, completion date, or event date depending on the report. This is where "the numbers changed" investigations usually land — the time filter was different.

When a report's numbers look wrong, walk these three in order: scope, then state, then time. The mismatch is almost always in one of them.

Best Practices

Match the report to the question, not the question to the report. The most common reporting mistake is opening the report you're familiar with and trying to force your question into what it shows. Decide the question first, then pick the report.

Confirm scope before completion rate. A "60% completion rate" is meaningless until you know what 100% is. Check the row count and confirm the scope matches what you're actually measuring.

Use Smart Segmentation as the scope, not manual filters. Smart Segments compose — you can layer segments across reports and get consistent scopes. Manual filters don't compose. If you're going to run the same report shape twice, define a Smart Segment.

Export before presenting to leadership. Numbers in a live tool can change between the run and the meeting. If you're presenting a completion rate to leadership, export the CSV at that moment and reference the export in the deck.

Reserve Insights for exploration, Reports for evidence. When you need to answer "what's the pattern here," Insights gets there faster. When you need to produce a record for an audit, build a Report. Different tools for different jobs.

Cross-check with the Track/Assignment reconciliation. If two reports on the same Track disagree, run the reconciliation logic above — different reports have different scopes.

Common Mistakes

Reading Track Status as a full audit report. Track Status only includes learners who've started. If you're asking "who was assigned but never started," Track Status won't show them — use Assignment Analytics or Assignment Status.

Comparing Assignment Summary to Assignment Analytics without adjusting scope. Assignment Summary aggregates across all historical assignments; Assignment Analytics on a Track view is scoped to the current assignment. Comparing them without knowing this creates ghost mismatches.

Sharing a live Insights dashboard without pinning the filter state. A dashboard with the wrong filter applied looks just as confident as one with the right filter. When you share a link with a stakeholder, double-check the filter state or save it as a personal dashboard with the filters baked in.

Using Report Builder when a standard Admin Report exists. Report Builder is powerful but requires you to know which fields you need. If a standard Admin Report already answers the question, use it — less to maintain, more consistent across your team.

Running the same report at different times and expecting the same numbers. Data changes. Time filters matter. If you need a "snapshot," export at the moment of the snapshot and version it.

Known Behaviors and Limits

Report scope depends on active assignment state at the time of run. If an assignment expires between two runs, learners in that assignment may move from In Progress to Expired — and the "completion rate" will shift even though nothing changed for the learners themselves.

Content Analytics on individual content items scope to that content only. If a Track includes multiple Articles, the analytics on the Track show the Track-level view. Analytics on any individual Article show that Article's view. They're different numbers by design.

Insights refresh cadence varies by account configuration. For the current refresh interval on your instance, check with your CSM — refresh timing is not global.

Workshop attendance requires the video conferencing integration. Without Zoom, Teams, or Google Meet configured, workshop attendance falls back to registration status, which is less reliable.

Historical data depth is your instance's data retention. Reports and Insights can only go back as far as your instance has data. If you've been on Continu for two years, that's your ceiling.

See Also

• Admin Reports in Continu — the pre-built CSV reports.
• Report Builder in Continu — custom CSV reports.
• Continu Insights — interactive dashboards (paid add-on).
• Info / Analytics In Continu — content-level analytics tabs.

Start with the question. Match it to the surface. Pick the specific report. If the numbers look wrong, walk scope → state → time. Reports for evidence, Insights for exploration.