REFERENCE ARCHITECTURE · EDUCATION & MEMBERSHIP
Detecting learner disengagement before a refund request
Illustrative design: combine attendance and participation signals so a program lead can review learner disengagement before a refund request.
How to read this evidence
This is a reference architecture showing how the workflow would be designed. It is not presented as an attributed client outcome. (Reference architecture · illustrative targets)
Earlier
Detection than manual review
Illustrative workflow target
Prompt
Flag converted to an owned outreach task
Replaces ad hoc review
One queue
Signals landing where leads already work
No new dashboard introduced
Example context
- A provider running paid multi-week cohorts across Slack, a video platform, and an LMS.
- Program leads managing several cohorts may rely on memory to notice a struggling learner.
Problem to solve
- Attendance, channel activity, and assignment submissions may be separated across systems.
- A delayed signal can leave too little time for a useful intervention.
Possible design
01 · Define
Define one metric: learners re-engaged after a silence flag, per cohort.
02 · Design
A disengagement score combining missed sessions, channel silence, and unsubmitted work, with an explicit threshold rather than a black box.
03 · Build
Connectors into the LMS and community, an orchestration layer that scores nightly, and an outreach task written into the program lead's existing queue.
04 · Measure
Track flag-to-outreach time and whether flagged learners return to the next session.
These are example tools for an illustrative design. The implementation depends on your systems and controls.
Design consideration
Design consideration: test alert thresholds on historical cohorts before asking program leads to act on a live queue.
NEXT STEP
Does this resemble your workflow?
Tell us the goal, systems, and owner. We will suggest an appropriate starting path.