Skip to main content
Best Answer

Scheduled Reporting Audits

  • Oct 16, 2026 4:24 AM UTC
  • 1 reply
  • 22 views

Hello Docebo Community,

Hope you are doing great. Please provide any ideas regarding Scheduled Reporting Audit strategy acting as a safety net to catch SCORM tracking failures without forcing you to manually monitor live user sessions. Is this something that could work? Thank you for your time. 

Key Benefits of Scheduled Reporting Audits
•    Proactive Anomaly Detection: Identifies users stuck in "In Progress" status before they reach out to support or miss compliance deadlines.
•    Automated Data Delivery: Sends periodic reports (CSV or Excel) straight to admin email inboxes or SFTP servers.
•    Zero Learner Friction: Works silently in the background without affecting learner performance, opening pop-ups, or slowing down course execution.
•    SCORM Failure Isolation: Helps cross-reference spent time against completion status to distinguish between abandons and technical payload failures.

Instructions: Setting Up a SCORM Audit Report in Docebo
1.Navigate to Custom Reports:Admin Access Required.
Log into Docebo as a Superadmin or Power User with reporting permissions. Go to the Admin Menu (gear icon) and select Reports under the E-Learning section.
2.Create a New Custom Report:
Click Create Custom Report in the top right. Select Users - Courses as the report type (or Users - Training Objects to drill down directly into the Articulate Rise SCORM material level). Name it "SCORM Audit: Stuck / Failed Progress".
3.Configure Data Filters:
Under the Filters tab, narrow down the target dataset:
•    Enrollment Status: Select In Progress.
•    Courses: Select specific Articulate Rise courses or select all courses.
•    Time Spent / Progress Threshold: Add a filter for Time Spent > [Estimated Course Duration, e.g., 30–60 mins].
4.Select Data Columns to Display:
Under the View Options tab, include key columns that expose SCORM communication gaps:
•    User Name / Email
•    Course Name / Training Object Name
•    Enrollment Status
•    Course Progress Percentage
•    Score
•    Total Time Spent in Object / Course
•    First Access Date & Last Access Date
5.Schedule Automatic Delivery:
Navigate to the Schedule tab:
•    Enable Schedule this report.
•    Set the frequency (e.g., Daily at 7:00 AM or Weekly on Mondays).
•    Add admin/L&D support email addresses to receive the automatically attached file. Save the report.

Best answer by Moshe.Machlav

In organizations I've worked with, the pattern that holds up best is flipping this from a proactive daily spreadsheet audit to an automated, reactive triage workflow using Docebo Connect (or your ticketing/helpdesk automation calling the Docebo API) the moment a learner actually sends an email or opens a support ticket:

  1. Trigger on incoming learner email/ticket: When a learner emails support claiming they completed a course that still shows In Progress, the recipe triggers automatically and extracts the sender's email and course name (or queries their active In Progress enrollments).

  2. Inspect the enrollment and SCORM tracking data: The workflow looks up the user (Get users / Get Course Enrollments) and pulls their training material tracking details—comparing first_access, last_access, total session time, quiz score (cmi.score.raw), and whether bookmarking (cmi.suspend_data) or completion calls were recorded (see Using the SCORM debugging option).

  3. Send an informed, automated response (or pre-diagnose for the admin):

    • Idle session / incomplete content: If the tracking shows 45 minutes of session time but minimal progression in suspend_data or an unsubmitted quiz, the automation replies immediately to let the learner know which section or quiz is still pending and reminds them to exit via the course's Exit/Close button so the final LMSCommit fires properly.

    • Verified SCORM anomaly: If the data shows a passing score or full progression where the completion payload failed to commit (or hit the 4,096-character suspend_data limit on SCORM 1.2), the workflow can either mark the material complete via API and confirm back to the learner, or flag the ticket with the diagnostic log for a 10-second admin sign-off.

This way, learners who actually run into trouble get an instant, data-backed answer, and your admin team never has to sift through daily spreadsheets of idle browser tabs.

View original

1 reply

Moshe.Machlav
Helper III
Forum|alt.badge.img+2
  • Helper III
  • Answer
  • Oct 16, 2026 6:30 AM UTC

In organizations I've worked with, the pattern that holds up best is flipping this from a proactive daily spreadsheet audit to an automated, reactive triage workflow using Docebo Connect (or your ticketing/helpdesk automation calling the Docebo API) the moment a learner actually sends an email or opens a support ticket:

  1. Trigger on incoming learner email/ticket: When a learner emails support claiming they completed a course that still shows In Progress, the recipe triggers automatically and extracts the sender's email and course name (or queries their active In Progress enrollments).

  2. Inspect the enrollment and SCORM tracking data: The workflow looks up the user (Get users / Get Course Enrollments) and pulls their training material tracking details—comparing first_access, last_access, total session time, quiz score (cmi.score.raw), and whether bookmarking (cmi.suspend_data) or completion calls were recorded (see Using the SCORM debugging option).

  3. Send an informed, automated response (or pre-diagnose for the admin):

    • Idle session / incomplete content: If the tracking shows 45 minutes of session time but minimal progression in suspend_data or an unsubmitted quiz, the automation replies immediately to let the learner know which section or quiz is still pending and reminds them to exit via the course's Exit/Close button so the final LMSCommit fires properly.

    • Verified SCORM anomaly: If the data shows a passing score or full progression where the completion payload failed to commit (or hit the 4,096-character suspend_data limit on SCORM 1.2), the workflow can either mark the material complete via API and confirm back to the learner, or flag the ticket with the diagnostic log for a 10-second admin sign-off.

This way, learners who actually run into trouble get an instant, data-backed answer, and your admin team never has to sift through daily spreadsheets of idle browser tabs.