01
Find Your Centre
You need to confirm the exact centre before you leave, not guess from partial names.
Flowchart3 steps
01Search centre or city
02Open the correct centre page
03Check route and proof
Text guideHow to use
- Start from search and type the centre name, school name, or city.
- Open the matching centre page and confirm the full address first.
- Use route notes, source evidence, and related pages before exam-day travel.
GraphicsVisual summary
Entry pointSearch
Decision gateCorrect centre
OutcomeTravel-ready
You get one clear centre page with address, route links, and proof-backed context.
Open module02
Command Rooms
If you need help on the way, coordinate only with people going to the same place.
Flowchart3 steps
01Create or join room
02Use chat, rides, or group tools
03Restore room if the tab closes
Text guideHow to use
- Open Command Room and join the room that matches the exam, date, and centre.
- Use chat, rides, and coordination only with people tied to that room.
- If the session breaks, restore the room instead of creating noisy duplicates.
GraphicsVisual summary
Room scopeExam-day only
Shared toolsChat / ride / group
RecoveryRestore flow
A temporary exam-day coordination space without public-group noise.
Open module03
Live Coordination
Live should feel controlled and safe, not confusing when a shared link opens.
Flowchart4 steps
01Host starts live
02Viewer taps Watch Live
03Viewer requests join
04Host approves media
Text guideHow to use
- The host starts first and becomes visible in the room.
- A viewer enters in watch mode and only joins media after requesting access.
- The host approves camera and mic before the viewer starts publishing.
GraphicsVisual summary
First stateWatch mode
ControlHost approval
Media roleViewer to speaker
Live opens in watch mode first, then camera and mic are approved only when needed.
Open module04
Safety SOS
If travel feels risky, one trusted person should be able to follow your safety status simply.
Flowchart3 steps
01Start safety session
02Share guardian link
03Send heartbeat or SOS status
Text guideHow to use
- Create one private safety session before travel starts.
- Share the guardian link only with the trusted contact who should monitor the trip.
- Send normal heartbeat updates until there is a real need to trigger SOS.
GraphicsVisual summary
AudienceTrusted guardian
Normal stateHeartbeat
EscalationSOS alert
A private guardian safety flow that stays separate from public incident posts.
Open module05
Incident Updates
Public incident updates should stay useful, specific, and moderated.
Flowchart3 steps
01Upload factual report
02Moderate in admin
03Publish public update
Text guideHow to use
- Upload a factual incident with place and exam context, not gossip.
- The owner queue verifies or hides the report before it becomes a public signal.
- Published items stay useful when they are timely, specific, and reviewable.
GraphicsVisual summary
InputReport and video
FilterAdmin moderation
Public stateReviewed feed
A public update surface for timely, reviewed exam-day signals.
Open module06
Centre Correction
When a centre is missing or wrong, students need one place to fix it with proof.
Flowchart3 steps
01Add, correct, or request verification
02Attach photo, video, or source
03Approved evidence updates the record
Text guideHow to use
- Submit a new centre, correct an existing one, or ask Margdarshak to verify it.
- Attach photos, video, or a source URL only when they add real proof.
- The admin queue reviews the evidence before it becomes part of the public centre record.
GraphicsVisual summary
SubmissionAdd or correct
Proof layerPhoto / video / source
ResultBetter centre page
Proof-backed centre updates that improve the public record without fake data.
Open module07
Updates and Guides
Students need quick notices in one place and longer guidance in another.
Flowchart3 steps
01Important notice is posted
02Public notice rail displays it
03Longer guidance stays in the blog
Text guideHow to use
- Use broadcasts for urgent operational updates that need quick public visibility.
- Use the blog for evergreen explainers, guides, and planning content.
- Keep the two surfaces separate so urgent notices do not get buried.
GraphicsVisual summary
Fast surfaceBroadcasts
Deep surfaceBlog
RuleDo not mix
Short updates stay fast, while evergreen guidance stays easy to read later.
Open module08
Android App
The app should feel cleaner on phone and still respect permissions properly.
Flowchart3 steps
01Open app shell
02Allow location when needed
03Use the same core tools on phone
Text guideHow to use
- The web and app surfaces share one product but do not need the same UI shell.
- In app mode, native-aware permissions and location behavior matter more than browser assumptions.
- Testing should happen on a real device, not only in desktop preview.
GraphicsVisual summary
Surface splitWeb and app
Native needPermissions
Final checkReal phone QA
The same product works on web and phone, with app-specific permissions where needed.
Open module