PF02 — Lesson placement, status, and stop governance

Field	Detail
Features	F02, F04, F19, cover via F34/Da Capo
Primary owner	G14 HODs (variations) / G01 Sue (stop)
Frequency	Ongoing; peaks at intake and term changes
Source	Sessions 1, 3
Status	Draft — validate stop rules with Sue (teachers frustrated — R18)

Purpose

Manage each boy’s instrumental enrolment per instrument: placed, cover teachers, stopped — with strict rules so payroll and parent charges stay aligned.

Data model (business language)

CS Music — one record per boy.
CSMusic — one row per boy + instrument (status, teacher, temp teacher).

Who is involved

Role	Does what
HOD (G14)	Start new instrument, teacher change via variations (scripted)
Sue (G01)	Sets stopped; reconciles pay and charges first
Cover teacher	Temporary assignment on boy record
Tutor	Sees temp teacher field while active

Process steps — start / change (HOD)

Open Variations to lessons.
Start new instrument — confirm; fill details; process creates variation record.
Change teacher — finishes old enrolment row + new record (BR-U16?) — not in-place edit.
Temporary vs permanent cover: temp field per boy; variations path (BR-U30?).

Process steps — stop (Sue only)

Boy remains placed while lessons run and until reconciliations done.
Sue completes teacher pay alignment and accountant charges alignment.
Only then Sue/admin sets status stopped (BR-U27?).
Teachers may be blocked from stopping early (R18 — validate).

Variations & exceptions

Situation	What happens
Maternity / extended leave	Temp teacher on Da Capo; not removing boys from permanent teacher
Mid-year instrument add	Welcome email — overlaps F26 vs F02 trigger
Scholar	Charge rules differ (F20)

Outside FileMaker

Item	Ref
Parent emails for variations	Often Sue sends (F28, M04)

Open questions (validation)

Who can click stop besides Sue?
Exact reconciliation checklist before stop.
Confirm on-screen label reads Da Capo (§16 #6).

Register links

F02, F04, F19, F34, BR-U16, BR-U27, BR-U30, E02, E36