The English Program: Prep, Class, Recap
Hoan’s English classes for client-facing engineers get a schedule, a prep draft the day before, an exercise library it draws from, homework recordings and a recap written from the transcript. All of it on the training entity.
One week of the group
The teacher teaches in Lark as before, with recording on. Everything around the class is drafted for him and checked by him.
How the loop works
A plan carries the rhythm, the roster, the Lark meeting title its recordings are found under, and the programme philosophy. Publishing it up to a date creates one session per date with every learner on it. Nothing but the teacher extends it; one session can be moved or cancelled alone.
At 09:00 Vietnam time a routine reads the philosophy, the last three plans, the last recap, the teacher’s note on each learner and the exercise library, and writes an ordered list of blocks that fills the minutes and matches the programme’s split between the presentation half and the reactive half. One line says what the draft is reacting to.
An Inbox line says the plan is ready. On the session page he swaps exercises from the library, edits timings, adds a free block, attaches the slides and marks it checked. A block can name only an exercise that is live in the library.
At 08:00 the teacher gets one Inbox line per session: the time, and for each learner whether the homework due today is in. No model call, no Lark, no email.
Nothing changes in the room. The recording is picked up by title and time window after the class, or the transcript is pasted by hand when the sync does not find it.
What was covered, a line per learner with the actual words that went wrong and what to practise, and a homework suggestion. The teacher approves it; each learner sees only their own line. A weekly recap reaches the client with nothing the learners have not already seen.
The seven elements
Every workflow we document has the same anatomy: seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
The teacher publishes a plan on a rhythm (Tuesdays and Thursdays, 14:00 to 15:15) up to a date. Each date becomes a session on every learner’s record.
The programme philosophy in the teacher’s words, the exercise library, the last three session plans, the last recap and the teacher’s note on each learner.
The teacher checks the drafted plan the day before: swaps exercises, edits timings, sets the homework. A draft naming an exercise not in the library cannot save.
The morning of, an Inbox line with each learner’s homework standing. After the class, the recording is picked up and turned into a recap for the teacher to approve.
A session plan half presentation, half reactive by minutes; a recap addressed to each learner; a weekly recap for the client.
Learners see the next session, the homework and, once approved, the recap on My Training. The weekly recap goes by email on the teacher’s say-so or at the deadline.
Sessions held and attendance inside the programme read, under its three-person floor. Nothing about one learner is shown to anyone but them and their teacher.
The standing rules
- Every session plan is half presentation, half reactive, by minutes
- Pressure from session one: activities learners cannot prepare for
- Homework is a recording, a file, a link or text, brought to the next class
- A draft that names an exercise not in the library never saves
What stays private
- A learner’s stars, load, skip reason and review note are theirs alone (ADR 0016)
- The teacher’s note is teacher-to-learner feedback the learner reads; nowhere else
- The weekly recap carries nothing a learner has not seen in their own recap line
How it runs at Edge8
- Two routines on Settings › Agents: the prep draft at 09:00 and the reminder at 08:00, Vietnam time
- One Claude call per session for the prep, one per transcript for the recap, bounded per run
- Everything is on the portable training entity; the meeting record is the company meeting database
This is the same method documented across this whole section. Explore the other workflows →