Cohort Communication Cadence

A cohort starts together and then spreads out. By week three there is a front group who are ahead, a middle group keeping pace, and a tail who missed one session and never caught up. The tail is where the non-completions, the refund arguments and the bad reviews come from, and it forms silently. Nobody is tracking who missed last week's live class, who has not opened a module in nine days, who skipped two assignments. The tutor notices in week six, which is three weeks after it could have been fixed with a two-line message.

The communication that exists is usually one of two failures. Either it is manual - the tutor writes a weekly email when they have time, which means irregularly, and sends individual nudges to whoever they happen to remember. Or it is a fixed drip built once, identical for every cohort and every student, which carries on cheerfully sending week-four content to somebody who dropped out in week two and congratulating people on assignments they never submitted. The first does not scale past one cohort; the second actively damages trust.

What a scheduled program actually needs is two layers running at once. A cohort layer that keeps everyone to the same rhythm - the week-ahead briefing, the session reminders, the deadline warnings, the midpoint check, the final-weeks push - all merged from the cohort record so one build serves every intake. And an individual layer watching engagement per student, firing a specific, human-sounding nudge when somebody slips, and escalating to the tutor only when the automation has had its two attempts. Done properly, the cohort gets a rhythm it can feel, the tutor gets a short list instead of a vague worry, and nobody receives a message that contradicts what they actually did.

Pipeline and stages

One pipeline, Cohort Progression, with a card per student per cohort. Unlike a sales pipeline, cards here move on program position, not on persuasion, and a card can move backwards when a student recovers.

• Week 1-2 - Settling
• On Track - attending, submitting, logging in; the stage most of the cohort should sit in.
• Slipping - one engagement signal missed; automated nudges running, no human needed yet.
• At Risk - two or more signals missed, or one missed twice; tutor owns the card.
• Intervention Active - a human has made contact and agreed a plan with a review date.
• Recovered - back to pace after an intervention, tracked separately so the provider can see that interventions actually work.
• Final Stretch - the last two weeks, where a different cadence applies.
• Completed and Completed with Distinction - closed-won variants if the program grades.
• Withdrawn, Deferred to Next Cohort, Lapsed - No Contact - three closed-lost variants, because they need different follow-up and different reporting.

Calendars

• Live Class Sessions - the recurring cohort schedule, with reminders and attendance tracking per session rather than per course.
• Tutor Office Hours - recurring weekly slots open to the cohort, with a hard capacity so they stay useful.
• Catch-Up Clinic - a weekly slot released only to students tagged slipping or at-risk. Being behind should have an obvious, low-shame route back.
• Midpoint One-to-One - a short review booked with every student at the halfway mark, whether or not they are struggling.
• Assessment or Submission Review - slots for feedback conversations after a graded piece of work.
• Study Group - optional peer slots the cohort books itself, where the program supports it.

Custom fields

• Cohort Code, Course Name, Start Date, End Date, Total Weeks, Current Week Number, Tutor Assigned, Timezone
• Next Session Date, Next Deadline, Next Deadline Title - the three merge fields that let one email template serve every week of every cohort
• Sessions Held, Sessions Attended, Attendance Rate, Consecutive Sessions Missed
• Modules Released, Modules Completed, Progress Percent, Days Since Last Login
• Assignments Due, Assignments Submitted, Assignments Late, Assignments Missing
• Engagement Score - a weekly 0-to-3 count of attendance, login activity and submission. The one field the whole individual layer reads.
• Engagement Trend - improving, steady or declining, derived from the last three weekly scores. A declining 3 matters more than a steady 2.
• Slip Reason, Intervention Owner, Intervention Plan Agreed, Review Date, Intervention Outcome
• Midpoint Review Done, Completion Forecast (on track, borderline, unlikely) set by the tutor, never by an automation
• Certificate Issued, Alumni Opt In, Testimonial Given

Tags

• cohort-{{code}}, course-{{slug}}, week-{{n}} - the week tag is rewritten each week so a single send can target the current week of every running cohort
• on-track, slipping, at-risk, recovered
• session-attended-{{n}}, session-missed-{{n}}, two-missed-running
• assignment-submitted-{{n}}, assignment-late, assignment-missing
• inactive-7, inactive-14, inactive-21
• catch-up-booked, office-hours-attended, midpoint-done
• intervention-open, intervention-closed, plan-agreed
• final-stretch, completed, withdrawn, lapsed
• alumni, review-requested, testimonial-given, next-course-interest

Forms and surveys

• Weekly Pulse - two questions, every week, thirty seconds: how is the pace for you, and is anything blocking you. Short enough to actually get answered, and the single best early-warning instrument in the build.
• Session Absence Reason - one question sent after a missed live class: could not make the time, technical problem, fell behind, personal reasons, no longer continuing. The answers route to completely different branches.
• Midpoint Review - a reflective form before the halfway one-to-one: what is working, what is not, what do you want from the second half.
• Catch-Up Plan - completed with the tutor during an intervention: what is outstanding, what the student commits to, by when, and what support is being provided. Writes Review Date.
• End of Program Feedback - the full evaluation at completion, plus the testimonial and review consent question.
• Exit Survey - sent to anyone withdrawing, with an honest route to say the course was not what they expected.

Memberships and content release

• Drip release of modules tied to the cohort week rather than to the individual signup date, so the whole cohort is genuinely looking at the same material in the same week.
• A catch-up path: previously released modules stay open, with a short summary at the top of each so a returning student can re-enter without rewatching everything.
• Cohort community space with a weekly discussion prompt posted automatically, tied to that week's module.
• Progress tracking and submission events feeding Modules Completed, Progress Percent and the assignment fields.

BO's role and guardrails

• BO answers the recurring logistics questions all cohort long: when is the next session, where is the recording, what is due and when, how do I submit, where is the reading, how do I book office hours. Answered from the cohort record, in the student's timezone.
• BO books catch-up clinic, office hours and midpoint slots, sends recordings to anyone who missed a session, and collects the absence reason.
• BO may not grant a deadline extension, agree a catch-up plan, give academic feedback on work, comment on whether a student will pass, discuss fees, refunds or withdrawal, or vary any assessment requirement. All route to the tutor or program manager.
• BO never delivers bad news about progress. A student asking whether they are behind gets an honest, neutral statement of what is outstanding and an immediate offer of the catch-up clinic - never a judgment.
• Any disclosure of illness, bereavement, a mental health difficulty or personal crisis is acknowledged in one warm line and handed to the named support contact within the hour. BO asks nothing further and records no detail.
• Every automated nudge in this build is written so that a student who reads three of them in a row does not feel pursued. Two attempts, then a human.

Numbers and channels

• The student services number used for session reminders, deadline warnings and individual nudges, kept separate from any marketing number.
• Email as the primary channel for the weekly briefing and anything with detail; SMS reserved for time-critical reminders and short nudges. A weekly SMS cap per student so the cadence never becomes noise.
• Web chat in the course area and the cohort space.
• Calendar sync for tutors, and the video platform for sessions, with per-session attendance flowing back - attendance data per session, not just per course, is what makes the whole individual layer possible.
• LMS connection for login, module completion and submission events, and a review platform connection for the completion-stage review request.

1. A student arrives from the onboarding build tagged fully-onboarded. A card is created in Cohort Progression at Week 1-2 - Settling, carrying Cohort Code, Total Weeks, End Date, Tutor Assigned and Timezone. Engagement Score starts at zero and is recalculated weekly.
2. Every Sunday evening the cohort-week scheduler rewrites Current Week Number and the week-{{n}} tag for every active cohort, and refreshes Next Session Date, Next Deadline and Next Deadline Title from the cohort schedule.
3. Monday morning the week-ahead briefing goes out to the whole cohort: this week's module, the live session with time in each student's own timezone, what is due and when, the discussion prompt, and the office hours link. One template, every cohort, merged from the record.
4. Thursday the student attends the live session. Per-session attendance syncs back, Sessions Attended increments, and session-attended-4 is tagged.
5. Friday evening the Weekly Pulse arrives: two questions. She answers that the pace is fine and nothing is blocking her. The card stays at On Track.
6. Sunday the engagement calculation runs. Attendance yes, logins yes, assignment submitted yes - Engagement Score is three, Engagement Trend steady. No individual messaging fires at all, which is the correct outcome for most of the cohort most weeks.
7. In week five she misses the live session. Within two hours the recording arrives with a timestamp index and the Session Absence Reason question. She answers could not make the time, so she gets the recording path rather than an intervention.
8. Week six: she misses the session again and has not logged in for nine days. Consecutive Sessions Missed hits two, inactive-7 is tagged, Engagement Score drops to one and the trend flips to declining. The card moves to Slipping and the catch-up clinic link is released.
9. Two automated nudges go out across four days - specific, short, naming exactly what is outstanding, offering the clinic. She does not respond to either.
10. The card moves to At Risk, Slip Reason records two missed sessions and nine days inactive, and a call task lands on the tutor due the same day. Automated messaging on this thread stops - the next contact is a human voice.
11. The tutor calls, finds out she has had a work deadline, and completes Catch-Up Plan together: two modules and one assignment by a date they agree. The card moves to Intervention Active, Review Date is set, and a reminder is scheduled for both of them.
12. She hits the plan. On the review date the tutor marks the outcome, the card moves to Recovered and then back to On Track, and the normal weekly cadence resumes with no reference to the episode.
13. At the halfway point every student in the cohort - including the ones who never slipped - gets the Midpoint Review form and a one-to-one booking link. The tutor sets Completion Forecast on each card afterwards.
14. With two weeks left the cards move to Final Stretch and the cadence changes: what is outstanding per student, the submission checklist, the assessment dates, and what happens after the program ends.
15. On completion the card moves to Completed, the certificate is issued, End of Program Feedback goes out, and a strong score routes to a review request while a weak one routes to the program manager. She is tagged alumni and enters the alumni and next-course sequence.

1. Cohort Week Advance and Schedule Refresh

Trigger: scheduled weekly, Sunday evening, for every cohort whose End Date has not passed.

• Increment Current Week Number. Remove the week-{{n-1}} tag and apply week-{{n}} to every active card in the cohort.
• Read the cohort schedule and rewrite Next Session Date, Next Deadline and Next Deadline Title. Release this week's module in the course area and post the week's discussion prompt to the cohort space.
• Increment Sessions Held for any session that took place in the week just ended, then recalculate Attendance Rate.
• Branch - Current Week Number equals Total Weeks minus 1. Apply final-stretch and move cards to Final Stretch.
• Branch - the schedule has no session or deadline for the coming week (a reading week or a break). Suppress the Monday briefing's session section and send the break notice instead. Without this branch the build confidently announces a class that does not exist.
• Failure alert: if the job does not run, or Current Week Number does not change, notify the internal channel immediately. Every message in the build merges from these fields, so a silent failure sends the whole cohort the wrong week.
• Exit: cohort End Date passes.

2. Weekly Cohort Briefing and Session Reminders

Trigger: Monday morning, to tag cohort-{{code}}, excluding cards in Withdrawn, Deferred and Lapsed.

• Email the briefing: "Week {{current week}} of {{total weeks}}. This week: {{module title}}. Live session {{next session date}} at {{local time}} - {{join link}}. Due: {{next deadline title}} by {{next deadline}}. Discussion prompt is up in the cohort space, and office hours are {{office hours}} - {{booking link}}."
• Branch - card is in Slipping or At Risk. Append one extra line only: "You have {{outstanding items}} still open from earlier weeks. The catch-up clinic is there for exactly this: {{link}}" The student still gets the normal briefing - never replace it with a warning.
• 24 hours before each live session, email with the agenda and joining link.
• 2 hours before, SMS: "{{Course}} session at {{local time}} today: {{link}}"
• 10 minutes before, SMS to anyone not yet joined: "Starting now - {{link}}"
• 48 hours before Next Deadline, email to students with that assignment not yet submitted: "{{Next deadline title}} is due {{next deadline}}. If you need longer, say so now rather than after - reply and we will sort something out."
• Exit: cohort ends, or the card reaches a closed stage.

3. Weekly Engagement Calculation

Trigger: scheduled weekly, after the week advance, per active card.

• Score three signals for the week just ended, one point each: attended the live session (or watched the recording within 72 hours), logged in at least once, submitted whatever was due. Write Engagement Score.
• Compare against the previous two weeks and write Engagement Trend as improving, steady or declining.
• Update Days Since Last Login, Consecutive Sessions Missed, Assignments Missing, Progress Percent.
• Branch A - score 3, or score 2 with a steady or improving trend. Stage stays or returns to On Track, tag on-track, and no individual messaging fires. This is the correct outcome for most of the cohort and the build must be silent here.
• Branch B - score 2 with a declining trend, or score 1. Tag slipping, move to Slipping, write the specific gaps to Slip Reason, release the catch-up clinic link, and hand to workflow 5.
• Branch C - score 0, or Consecutive Sessions Missed of 2 or more, or Days Since Last Login above 14, or 2 or more assignments missing. Tag at-risk, move to At Risk, and hand straight to workflow 6 without further automated messaging.
• Branch D - first two weeks of the program. Calculate and record but do not escalate; settling-in noise is not drift.
• Exit: card reaches a closed stage.

4. Missed Session Recovery

Trigger: a live session ends and attendance shows the student absent.

• Tag session-missed-{{n}}, increment Consecutive Sessions Missed.
• Wait 2 hours. Email the recording with a timestamp index and one question: "Missed you at tonight's session - here is the recording with timestamps so you can jump to what you need. Quick one so we know how to help: what got in the way? {{absence form link}}"
• Branch A - could not make the time. No escalation. Confirm the recording counts, and if the pattern repeats three times, offer an asynchronous track or a schedule conversation with the tutor.
• Branch B - technical problem. Send the tech troubleshooting page and a Catch-Up Clinic slot, and notify the technical contact with whatever detail the student gave.
• Branch C - fell behind. Send the catch-up path: which modules are outstanding, the short summaries, and the clinic booking link. "Falling behind is the most common thing that happens on a course like this, and it is fixable. Here is exactly what is outstanding, and the clinic is a 20-minute reset with your tutor: {{link}}"
• Branch D - personal reasons. No automation beyond an acknowledgement. Route to the named support contact within the hour, tag intervention-open, record no detail.
• Branch E - no longer continuing. Route to the program manager same day, send the Exit Survey, and never send a retention sequence in place of a human conversation.
• Branch F - no answer to the absence question within 48 hours. Treat as a signal in its own right and let workflow 3 pick it up on the weekly calculation.
• Exit: recording watched, a reason recorded, or the card escalates to At Risk.

5. Slipping Nudge Sequence

Trigger: tag slipping applied.

• Condition: the card is not in Intervention Active and the student has not been nudged in the last 5 days. The anti-fatigue check runs first, every time.
• Wait 12 hours. SMS, short and specific: "{{Preferred name}}, you have {{outstanding items}} open from week {{n}}. Twenty minutes with your tutor at the catch-up clinic will clear it: {{link}}"
• Wait 48 hours. Email with the actual path rather than encouragement: list each outstanding module and assignment with its direct link and a realistic time estimate for each. "This is everything outstanding and how long each piece should take. Start with the first one - the rest follows more easily than it looks."
• Wait 48 hours. Stop automated messaging entirely. Two attempts is the limit; a third message from a system a student is already avoiding does harm. Escalate to workflow 6 instead.
• Branch - clinic booked or any outstanding item completed. Tag catch-up-booked, exit the sequence immediately, and let the weekly calculation return the card to On Track when the score supports it.
• Branch - a reply of any kind arrives. Exit the sequence and assign the reply to the tutor. A student who answers deserves a person, not the next scheduled message.
• Exit: engagement recovers, escalation to At Risk, or the card reaches a closed stage.

6. At Risk Intervention and Catch-Up Plan

Trigger: tag at-risk applied, or card moved to At Risk.

• Suppress all automated messaging to this student except the Monday cohort briefing. From here the contact is human.
• Write the specific gaps to Slip Reason, set Intervention Owner to the tutor, and assign a phone call task due the same working day, with the card's engagement history attached so the tutor opens the call informed.
• Notify the tutor and the program manager in the internal channel: student, cohort, week, score, trend, and the exact items outstanding.
• On the call, the tutor completes Catch-Up Plan: what is outstanding, what the student commits to, by when, and what support is provided. This writes Intervention Plan Agreed and Review Date, moves the card to Intervention Active, and tags plan-agreed.
• Send the plan to the student in writing the same day: "Here is what we agreed: {{plan items}} by {{review date}}. Nothing else is expected of you in the meantime. I will check in with you on {{review date}}."
• Reminder to the student 2 days before Review Date, and a task to the tutor on the date itself.
• Branch A - plan met. Write Intervention Outcome as recovered, move to Recovered, tag recovered and intervention-closed, then return to On Track on the next weekly calculation. Normal cadence resumes with no reference to the episode.
• Branch B - plan partly met. One revised plan, one new review date. Not an indefinite loop: if the second plan is also missed, the program manager takes the decision.
• Branch C - no contact achieved after 3 attempts across 5 working days. Move to Lapsed - No Contact, notify the program manager, and send one final message by email and SMS: "We have tried to reach you a few times about {{course}}. We are not going to keep messaging. If you want to pick it up, reply to this and we will find a way - that offer does not expire."
• Branch D - student chooses to stop. Move to Withdrawn or Deferred to Next Cohort, send the Exit Survey, and hand any refund or fee question to the program manager - never to an automation.
• Exit: an outcome is recorded by a human.

7. Weekly Pulse and Midpoint Review

Trigger: Friday evening weekly for the pulse; at the halfway week for the midpoint.

• Send Weekly Pulse: "Thirty seconds: how is the pace this week - too fast, about right, or too slow? And is anything blocking you?"
• Branch A - pace about right, no blocker. Record and send nothing.
• Branch B - pace too fast, or a blocker named. Reply within the hour: "Thank you - that is exactly what we want to know. {{Tutor}} will come back to you on this. If it is urgent, office hours are {{times}}: {{link}}" Create a tutor task with the student's own words attached.
• Branch C - pace too slow. Send the extension or stretch material and flag to the tutor. Bored students withdraw too, and this is the only signal that catches them.
• Branch D - any mention of illness, bereavement, mental health or crisis. Route to the named support contact within the hour, tag intervention-open, acknowledge warmly and briefly, and send nothing else automated.
• Post the weekly pulse digest to the internal channel: response rate, pace distribution, and blockers verbatim. Three students naming the same blocker is a content problem, not three student problems.
• At the midpoint week: send Midpoint Review to every active student with a Midpoint One-to-One booking link, regardless of stage. "Halfway. Before we talk, three questions on how it is going - what is working, what is not, and what you want from the second half." Reminder at 3 days, then a tutor task for anyone not booked at 7 days.
• After each one-to-one the tutor writes Completion Forecast and ticks Midpoint Review Done. Anyone marked borderline or unlikely gets a plan, not a flag.
• Exit: cohort ends.

8. Final Stretch, Completion and Alumni

Trigger: tag final-stretch applied, then cohort End Date.

• Email the final-stretch briefing, personalized to what each student still has outstanding: "Two weeks left. You have {{outstanding items}} to complete, and the final assessment is {{date}}. Here is the checklist and the submission route." A student with nothing outstanding gets a different, shorter version - never a chase.
• Reminders at 7, 3 and 1 days before the final deadline, escalating email to SMS, each naming only what is still missing.
• Branch - items still outstanding at 2 days before End Date. Assign a tutor task rather than sending another reminder. At this point only a conversation changes the outcome.
• On completion criteria met: move to Completed (or Completed with Distinction), tag completed, issue the certificate, write Certificate Issued, and send: "You are done. Certificate attached. It is worth remembering how you felt in week one - you have come a long way."
• Wait 2 days. Send End of Program Feedback, including the testimonial and review consent question.
• Branch - strong feedback with consent given. Wait 1 hour, then request a public review: "Thank you - genuinely. If you would put a few lines of that on {{review platform}}, it helps the next person decide: {{link}}" Tag review-requested, and testimonial-given on receipt.
• Branch - weak feedback. No review request. Create a task for the program manager due in 1 working day and reply: "Thank you for being straight with us. {{Program manager}} will read this properly and come back to you."
• Wait 14 days. Tag alumni, confirm Alumni Opt In with an explicit marketing consent step, and only then enroll in the alumni sequence: one useful piece of content monthly, the next-course options, and an alumni community invitation. Anyone who does not opt in receives nothing further.
• Wait 60 days. One re-engagement message about the next program to opted-in alumni, tagging next-course-interest on a click and handing those contacts to the enrollment funnel build.
• Post the cohort close report to the internal channel: completion rate, withdrawal timing, attendance curve, intervention outcome mix, feedback themes, and the week the cohort dipped.
• Exit: alumni sequence running on marketing consent, or the contact declines or unsubscribes - which is final.

The cohort has a rhythm it can feel. A briefing every Monday, a session reminder, a pulse every Friday - the same shape every week, merged from the cohort record so it serves every intake without being rebuilt. Students stop wondering what is happening this week.

Drift is caught in days. Two missed sessions and a week of inactivity used to be invisible until an assignment deadline. Now it produces a specific nudge within days and a tutor phone call within a week, which is the difference between a conversation and a withdrawal.

The tutor gets a list, not a worry. Instead of a vague sense that some people are behind, the board shows exactly who, by what measure, and since when. Tutor attention goes to the handful who need it rather than being spread evenly and thinly.

Nobody receives a message that contradicts reality. Because the individual layer reads actual engagement data, a student who dropped out in week two is not congratulated in week four, and a student who submitted early is not chased.

Completion becomes a managed outcome. Midpoint reviews, forecast flags and a distinct final-stretch cadence mean the end of a program is worked rather than awaited - and the feedback and review requests happen while the experience is still fresh.

Metrics to watch

• Completion rate per cohort, the headline number, tracked across consecutive intakes rather than in isolation.
• Per-session attendance rate and the distribution of consecutive misses - the shape of that distribution tells you where the program loses people.
• Engagement Score distribution by week, watched for the week the cohort typically dips; most programs have one, and it can be pre-empted once you know which.
• Count in Slipping and At Risk each week, and the recovery rate - how many returned to On Track after automated nudges alone, and how many needed a human.
• Time from first slip signal to human contact, which is the operational promise of this build.
• Weekly Pulse response rate and the pace-and-blocker themes by week.
• Assignment on-time submission rate per deadline, not averaged across the course.
• Withdrawal timing - which week withdrawals cluster in, and the exit survey reasons behind them.
• Intervention outcome mix: recovered, deferred, withdrawn. If few interventions recover students, the intervention is happening too late.
• Post-completion review and testimonial rate, and next-course enrollment rate from alumni.

Schedule and content data

• A complete cohort schedule per intake, as structured data rather than a PDF: every session date and time, every module release date, every assignment title and deadline, the midpoint week and the end date. This build is a thin layer over that data; without it, nothing can be merged and every message has to be written by hand.
• A defined engagement model agreed with the client before build: which signals count, how often they are evaluated, and what thresholds move a student to Slipping and At Risk. Get this wrong and the build either cries wolf or stays silent; expect to tune it after the first cohort.
• Weekly briefing copy written as one reusable template with merge fields, not twelve bespoke emails. Twelve bespoke emails will be out of date by the second intake.
• The catch-up path decided: do earlier modules stay open, is there a late submission policy, and who can authorize an extension.
• Named owners: the tutor who works At Risk, the support contact for personal disclosures, and the program manager who holds withdrawal and extension decisions.

Integrations

• LMS connection providing login timestamps, module completion and submission events. Days Since Last Login and submission status are the two data points the individual layer cannot function without.
• Per-session attendance from the video platform, attributed to the individual student and the specific session. Course-level attendance is not enough: the whole early-warning layer rests on knowing which session was missed and whether it was consecutive.
• Calendar sync for tutors, with real capacity on office hours and the catch-up clinic.
• Community platform connection if the cohort space is separate, for the automatic weekly prompt.
• Review platform connection for the completion-stage review request, and certificate generation if that is automated.
• A reliable scheduled job that advances Current Week Number and the week-{{n}} tag. If that job fails silently, every cohort message goes out for the wrong week - so build an internal alert if the week does not advance.

Numbers, messaging and compliance

• Provision the student services number and complete A2P 10DLC registration in the United States before the first cohort runs. These are transactional course messages; register the campaign to match and submit sample copy that reflects the actual reminders and nudges.
• Collect SMS consent with wording that covers course-related reminders, kept separate from marketing consent. The alumni and next-course sequences at the end of this build are marketing and need the marketing consent, not the course one.
• Honor STOP, UNSUBSCRIBE and HELP on every number. An SMS opt-out must not silence the schedule and deadline information a current student depends on - build the email fallback explicitly rather than assuming it.
• Set quiet hours so no automated SMS sends outside roughly 08:00 to 20:00 in each student's own timezone, and enforce a weekly SMS cap per student. A cadence build is the easiest kind to accidentally turn into harassment: count the messages a slipping student would receive in a bad week and make sure the total is defensible.
• Engagement and attendance data is a record of individual behavior. Decide who can see it, whether students can see their own, how long it is retained after the program ends, and whether it feeds any assessment decision - if it does, say so in the learning agreement.
• Disclosures of illness, bereavement, mental health difficulty or personal crisis will arrive through the pulse survey and the absence reason form. Route them to a named human within the hour, keep the detail out of the general record and out of every automated merge field, and give staff a written protocol for what to do with them.
• Where the provider operates under GDPR, UK GDPR, FERPA or similar regimes, confirm the lawful basis for engagement monitoring specifically - it is more intrusive than ordinary course administration and students should know it happens. Confirm the privacy notice, the retention schedule, the role-based access model, and the rules on marketing to alumni. Safeguarding duties apply where any student is under 18 and change the contact and escalation requirements materially.
• None of this is legal advice. Have the client's own counsel and data-protection adviser confirm the monitoring disclosure, the consent model, the retention schedule and any safeguarding or awarding-body obligations before the first cohort runs.

People and process

• A weekly cohort review, fifteen minutes, reading the At Risk and Slipping columns and the pulse themes. The build produces the signal; the meeting is where it becomes action.
• A service standard for interventions: contact attempt within one working day of an At Risk flag, a plan agreed and a review date set before the card leaves Intervention Active.
• A tuning review after the first cohort: were the thresholds right, did the nudges land, how many messages did the most-chased student actually receive. Expect to adjust.
• Scoping and pricing are per build. Book a call at bookings.appbo.io to work through the schedule data model, the engagement thresholds and the attendance integration.