Per-learner content completion data — who finished what, when. The "did they actually finish" view that complements engagement (views) data.
The Content Completion Report breaks down all content completions per learner. Use this when completion is the question (not engagement), when auditing for compliance, or when comparing actual completion against assignment expectations.
For engagement (views) data, see Content Engagement Report or User Engagement Report. For the strategic frame, see Reporting: Which Report Should I Use?.
When to Use This Report
Compliance and audit. Per-learner record of what was completed and when, with full learner profile data. Most compliance audits ask for completion, not engagement.
Comparing completion vs assignment. Pair with Assignment Summary to see what was assigned vs what was finished. Gaps surface the audience who needs follow-up.
Time-to-completion analysis. The completion date allows you to measure how long learners take to finish — useful for setting realistic due dates on future assignments.
Column Reference
User Internal ID / External ID — Unique learner IDs.
First / Last Name / Email — Learner identification.
Role — User role set within Continu.
Image — Profile image URL.
Language — Preferred language.
Job Title — Job title.
Location (1-3) / Department (1-3) — Hierarchical organization data.
Team / Level / Grade / Groups — Organizational categorization.
Is Manager / Manager Email — Manager status and the user's manager.
Is Collaborator — Yes/No for Collaborator role.
Last Login — Date/time of most recent login.
Hired Date — Date of hire.
Content ID — Unique content ID. Useful for API workflows.
Plus content title, type, and completion date columns.
How to Use This Report Effectively
Filter to a program's content for actionable views. Org-wide completion data is noisy. A specific program's completion against a specific audience is reviewable.
Use completion dates to set realistic due dates. If learners typically take 3 weeks to complete a Track, a 5-day due date is unrealistic. Use historical data to inform future assignment cadence.
Pair with Assignment Summary to find the gap. Completion Report shows who finished; Assignment Summary shows who was assigned. The diff is your follow-up audience.
Cross-reference with rating data for content quality. Content with low completion AND low ratings is the strongest candidate for retirement or rebuild.
Configuration Pitfalls
Treating Completion as Comprehension. A learner who clicked through doesn't necessarily understand the material. Completion is a participation signal, not a knowledge signal. Pair with Assessments for knowledge verification.
Reading Completion Counts Without Audience Context. 500 completions sounds like a lot — until you realize the audience was 5,000 and assignment coverage was 10%. Always contextualize.
Forgetting Manual Completions Show Up. Admins can manually mark content complete. Those completions appear here alongside learner-driven completions. For analytical purity, filter out admin-manual completions when comparing learner behavior.
Comparing Completion Across Content Types Without Adjusting. A 3-minute Article and a 90-minute Track have completely different completion baselines. Filter to comparable content for clean analysis.
Where This Fits
You're here because you need completion data on content. For engagement (views without necessarily completion), see Content Engagement Report. For per-learner platform activity, see User Engagement Report.
See Also
- Reporting: Which Report Should I Use? — the strategic anchor.
- Admin Reports in Continu — running and filtering reports.
- Content Engagement Report — engagement (views) detail.
- User Engagement Report — per-learner activity.
- Assignment Summary Report — pair to find assignment-vs-completion gaps.
- Managing And Manually Completing Assignments — when admins override completions.
Filter to a program before reading. Pair with Assignment Summary to find the gap. Completion is participation, not comprehension — pair with Assessments for the knowledge layer.