We need a solution to track dropped students that includes a status (last completed course in the learning plan) and/or the reason for the drop (which may Include dropped by instructor or voluntarily dropped by student). We are exploring using an additional field for this however, are hoping there is a more efficient way to capture this information.
Track Reason for Dropping a Course
Userlevel 7
+7
think that’s the closest and best way you can do this.
Userlevel 7
+6
2nd best Loretta? Would be to do something in tangent with the status.
By that I mean sending along an online form to the learner/manager with a notification saying that “we missed you at the last one” or something like that.
Userlevel 7
+3
2nd best Loretta? Would be to do something in tangent with the status.
By that I mean sending along an online form to the learner/manager with a notification saying that “we missed you at the last one” or something like that.
Yeah, it would really come down to what we mean by ‘dropping’ and the process involved for that person to drop since orgs handle this differently. Sounds like your drops are at the LP level, the initial question I would have is the how is the process handled for the dropping, which determines how that field is entered. Is it always going through an admin and just different reasons, or can it just be standard user deciding to drop out. Further, if its the LP level, where is that additional field living? seems an interesting thing to track.
- Webhook triggers on LP removal.
- This triggers recording process somewhere (sharepoint, database, excel, google sheets, somewhere.) gives the LP ID and Username and User ID.
- Off the above info, can use the API to look up course status’s (although typing this now presents another issue of how the unenrollment is being run and if they are being modified on course level too or retaining those records)
- Could also trigger an ‘Exit Program’ email and form to be filled out, which can record more details related to the unenrollment reasons and such.
- All gathered data recorded and added back to the tracking started in second bullet.
Could also manage the whole process to help avoid some of the ambiguity and start with an embedded ‘unenrollment request ‘form type, which would work largely the same way except no webhook to trigger, the form would trigger, and the data collect via email above would be collected upfront.
But yes, outside of system built tools to get there for sure.
Reply
Log in to Docebo Community
Enter your email address or username and password below to log in to Docebo Community. No account yet? Create an account
Docebo Employee Login
or
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.