Per-learner, per-assignment data — who got what, who completed it, when it was assigned, when it was completed. The audit trail for assignment activity.
The Assignment Summary Report is the per-row record of every assignment in the platform. Use this when you need to verify assignment delivery, investigate who-was-assigned-what, audit overdue assignments, or pull data for compliance evidence.
For the strategic frame on reporting, see Reporting: Which Report Should I Use?.
Date range constraint: Assignment reports can't be pulled for ranges greater than one year without filtering to specific content. For wider ranges, narrow by content.
When to Use This Report
Audit and compliance evidence. Per-learner record of what was assigned and when, with completion timestamps — the data structure most compliance audits need.
Investigating "I never got this assignment" tickets. When a learner reports missing an assignment, the report shows whether the assignment actually fired, who it was assigned by, and when.
Overdue audit. Filter for incomplete assignments past the due date to identify learners who need follow-up.
Column Reference
Assignment ID — Unique ID. Assignments with the same ID are part of the same assignment group (e.g., multiple learners assigned the same content in one action).
Assigner First/Last Name / Email / Job Title / External ID — Who assigned the content (admin or creator who triggered the assignment).
Assigned Date — Timestamp the assignment was created.
Assignment Completed Date — Timestamp the assignment was completed. Empty for incomplete assignments.
Plus learner profile columns — name, email, role, location, department, manager, hire date.
Plus content columns — title, type, ID, and Track membership if applicable.
How to Use This Report Effectively
Filter to one program or cohort. Org-wide assignment reports are too noisy. Filter to the program's content, audience, or date range for actionable views.
Use Assignment ID groupings. When the same Assignment ID appears across multiple rows, those rows are part of a single assignment action (e.g., one bulk-assignment to many learners). Useful for understanding "what was the bulk assignment that ran on this date."
Cross-reference with Manager Summary for follow-up. Overdue assignments are often best surfaced to managers, not learners. Manager Summary provides the aggregate view that lets you brief managers efficiently.
Configuration Pitfalls
Hitting the 1-Year Range Limit. The report won't run for ranges greater than one year without content filtering. Either narrow the date range or filter to specific content to get the data.
Misreading "Assigned Date" as "Visible to Learner Date". Some assignment paths (e.g., Automations with delays) create the assignment before the learner actually sees it. Assigned Date is the creation timestamp, not the surfaced-to-learner timestamp.
Filtering Out Completed When You Should Look at Both. An audit usually needs both completed and incomplete, with timestamps. Don't pre-filter unless you know you only need one slice.
Treating Empty Completed Date as Refusal. Empty completion can mean overdue, in-progress, or just never opened. Cross-reference with assignment progress data or the User Engagement Report for the cause.
Where This Fits
You're here because you need assignment-level data. For aggregated manager views, see Manager Summary Report. For program-level completion, see Content Completion Report.
See Also
- Reporting: Which Report Should I Use? — the strategic anchor.
- Admin Reports in Continu — running and filtering reports.
- Manager Summary Report — aggregated manager view.
- Content Completion Report — content-completion view.
- Managing And Manually Completing Assignments — for admin overrides on assignments.
Filter to a program before reading. Use Assignment ID groupings to spot bulk-assigned content. 1-year range limit unless filtered by content. Empty completion has multiple causes.