Delivery mode · Asynchronous

Finish on your own — but never alone.

Self-paced does not mean unsupported. Every self-paced participant has one assigned Champion and a fixed follow-up sequence from Day 0 to Day 10.

Who this playbook covers

This applies to every participant whose completion type is self-paced, no matter how they entered the programme. There is no separate dropout list — a participant either finishes or is still being followed up.

DimensionValue for this modeSet when
Entry — how they do Part 1Recorded orientation video, or live for those who left after Part 1At registration — immutable
Completion — how they do Part 2Self-pacedFrom the event type, or the moment they leave at a Part 1 exit point
Two doors, one playbook. Open-call sign-ups who watch the recorded orientation, and Part 1 leavers from live sessions, are handled identically from Day 0 onward. The recorded orientation requires the same registration and pre-course evaluation before Module 2, so the reporting baseline is the same in every mode.

What starts the clock

  • Day 0 is the Part 1 date — the day they completed the orientation, live or recorded
  • Every participant is assigned to exactly one Champion at registration, so no participant can exist without an owner
  • That Champion stays accountable until the participant is verified or dropped
  • Day 5 is the ideal completion time; Day 10 is the last day of dedicated, individual follow-up. For the participant it's a support window, not a deadline—the course stays open to them until the programme ends.
  • The window sets incentive eligibility: only completions by Day 10 count toward partner and champion financial support.

Day 0 to Day 10, message by message

Log every send against the participant on your sheet.

  • Day 0 — Welcome

    Course link, the three requirements, Day 5 target. Ask for their ADA email if you don't have it yet.

  • Day 3 — First nudge + requirements reminder

    One question: "How's Module 2 going?" Replies tell you who is reachable. Congratulate the movers, re-link the stalled to where they stopped, and name the two things people forget: the discussion post and the post-course evaluation.

  • Day 5 — Ideal completion

    Completers: congratulations. Everyone else: dedicated support continues to Day 10, and "what's blocking you?"

  • Day 7 — Blocker follow-up

    Solve the one blocker they named. Offer the next webinar's Part 2 as a guided finish.

  • Day 10 — Support window closes

    Completers: congratulations. Everyone else: last structured follow-up. Individual chasing stops after this, and completions after Day 10 no longer count toward host or champion financial support. Make clear the course itself stays open—they can still finish and earn their certificate until the programme ends.

  • After Day 10 — Light touch

    Monthly "still open" note. No individual follow-up unless they reply.

Which channel? Email always. Group chat for course participants or specific cohorts. Direct messages only where the participant has agreed to be contacted that way. Use whatever combination actually reaches the person—the sequence is the fixed part, not the medium.

Three lanes — protect your time

From Day 5, every self-paced participant sits in one of three lanes. You don't assign the lane by hand — it follows from the facts you record: last reply date, and module progress from the sanitized completion tracker.

Active

Replying or progressing

Run the full sequence. These are your best returns on time — keep the momentum going.

Stalled-responsive

Replies, but no progress

Diagnose the one specific blocker — login, device, time, or content — and solve that. Offer the webinar guided finish.

Unresponsive

No reply, no progress

No reply to two or more consecutive touches. Batch messages only. Spend no individual time here. Eligible to be marked dropped after Day 10.

Unresponsive is a routing decision, not a judgment. It only means batch messaging from here. They stay on the sheet, they keep their Champion, and they can rejoin any webinar's Part 2 at any time.

The Day 10 line — completions, support, and closing the loop

  1. Completions by Day 10 count

    Only completions inside the Day 0 to Day 10 window count toward host and champion financial support. For participants Day 10 is not a deadline: the course stays open until the programme ends, and late finishers still earn their certificate—they just don't count toward the support total, and they can't be re-registered into a later cohort for a fresh window: one participant, one Day 0.

  2. Flag two things for the Program Lead

    Completers: answered post-course assessment and ready for verifications.
    Systemic issues: for example, a whole student org (30 participants) stuck on the same blocker is one problem not 30 individual ones.

  3. Close the loop

    Mark dropped only where the criteria are met: in progress, past Day 10, and unresponsive. Log any new questions for the FAQ.

Record facts, not judgments. The facts drive the actual decision. That is what keeps the data from drifting as long as the information is updated.
Supported by: LinkedIn Organised by: ASEAN Foundation Implemented in the Philippines by: SmartCT with support from BNHR