06 / How it flows
One request, three people, one sequence
Centre
Scheduler
Ishanga
Requests a class"7 day IE, Kothrud"
New requestbatches, language, stay
Request severalonly free + trained
I'm availableor I can't + reason
Replies in one lineAsked 4 / Available 3 / Can't 1
Confirm team
Told who is comingnames, phone, batch
Got it, I'll be therecontact + stay unlock
not enough offers? request more, no one is followed up by phone
away days are honoured before anyone is requested
every step lands in
HistoryScheduleReports
i
Five steps, one word each
the same word and colour on every screenRequested4 opencentre requests
AskedAskedteam requests several
AvailableAvailableoffered, not confirmed yet
ConfirmedConfirmedteam picks
DoneDoneclass happens
side roads:
Can't
Yatra / Silence / Break
Not seenSeenGot it
"Available": offering is not the same as being confirmed
ii
Team, scope, role
the rule behind the switcherTEAM switches the whole app
CentresSchedulingMe
SCOPE filters inside it
All 4 centres
ROLE just a label, never a toggle
Sector coordinator / 4 centres
| Who | Centres | Scheduling | Me | Access |
|---|---|---|---|---|
| Admin |  | | | |
| Sector coordinator | | if given | | cluster |
| Scheduler | - | | | - |
| Centre rep | 1 centre | - | | - |
| Ishanga / volunteer | - | - | | - |
a part you cannot use simply does not appear