AMES Attendance System

Demo Guide  ·  POC v2.9  ·  May 2026

Agenda

#TimeRoleWhat we show
10:00–3:00Super AdminStart a new term — upload the teacher's Excel file
23:00–7:00TeacherMark today's attendance session
37:00–9:00CoordinatorReview and follow up on unmarked sessions
49:00–10:30ESOCampus-level support view
510:30–12:00ManagerCross-hub dashboard and calendar
12:00–20:00AllQuestions and live exploration

How the System Works

Term lifecycle

flowchart LR
    subgraph TS ["Term Start"]
        SA["Super Admin\nUpload Excel"]
    end
    subgraph ED ["Every Day"]
        T["Teacher\nMark ATT / DNA / N/A"]
        CO["Coordinator\nReview & correct"]
        T -- "unmarked alert" --> CO
    end
    subgraph TE ["Term End"]
        M["Manager\nDashboard"]
        C["Compliance\nExport & Audit"]
    end
    SA --> T
    CO --> M
    M --> C
      

End-to-end attendance flow

flowchart TD
    A([Term Starts]) --> B["Super Admin\nuploads teacher Excel"]
    B --> C["Sessions & student\nroster loaded"]
    C --> D["Teacher\nmarks daily attendance"]
    D --> E{"All sessions\nmarked?"}
    E -- No --> F["Coordinator / ESO\nfollows up"]
    F --> D
    E -- Yes --> G["Manager\noversees hub"]
    G --> H["Compliance\ngenerates funding claim"]
    H --> I(["Submitted to\nFunding Body"])
      

Demo Accounts

All accounts use password: demo

UsernameRoleScope
super_adminSuper AdminAll hubs — system config + Excel upload
teacher1TeacherMelbourne — Centre Hub
teacher2TeacherDandenong — South East Hub
coord_seCoordinatorSouth East Hub
mgrManagerAll 3 hubs
esoESOSingle campus

Scenarios

Super Admin New Term Setup ~3 min

Goal: Show how a new term's timetable goes from teacher's Excel to live sessions in the system.

Steps

  1. Login as super_admin
  2. Go to Admin → Upload Excel
  3. Upload the term workbook (T3_new_term_demo.xlsx)
  4. Review the preview: session count, student count, errors
  5. Review carry-forward: returning students from last term — approve each
  6. Commit → sessions appear on the calendar immediately
flowchart LR
    A["Upload Excel"] --> B["Preview\nsessions + students"]
    B --> C{"Returning\nstudents?"}
    C -- Yes --> D["Carry-forward\nreview"]
    C -- No --> E["Commit"]
    D --> E
    E --> F["Sessions live\non calendar"]
        

ⓘ Only Super Admin can upload  ·  Same file cannot be uploaded twice  ·  Returning students matched automatically by Student ID

Teacher Mark Today's Attendance ~4 min

Goal: Mark attendance for all students in a session, then submit the whole session at once.

Steps

  1. Login as teacher1
  2. Select a session from Today's sessions
  3. For each student in the roster, mark one status:
    • ATT — student attended
    • DNA — did not attend  (absence reason is required)
    • N/A — not applicable (holiday, withdrawn, cancelled)
  4. If a student arrived late or left early: enter actual duration or time range
  5. Select the appropriate unit(s) for each student (pre-filled from configuration)
  6. Submit the session once — all students saved together
flowchart TD
    A["Open today's session"] --> B["Student roster loads"]
    B --> C["Mark each student\nATT / DNA / N/A"]
    C --> D{"Any DNA?"}
    D -- Yes --> E["Select absence\nreason — required"]
    D -- No --> F{"Any late /\npartial?"}
    E --> F
    F -- Yes --> G["Enter actual\ntime or duration"]
    F -- No --> H["Confirm unit\nselection for each student"]
    G --> H
    H --> I["Submit session\nonce for all students"]
    I --> J(["Session marked ✓"])
        

Marking rules at a glance

SituationStatusExtra fields
Student attended full sessionATTUnit(s) — pre-filled from config
Student attended but late / left earlyATTUnit(s) + actual time or duration
Student did not attendDNAAbsence reason — required
Holiday / cancelled / withdrawnN/ANone

ⓘ Default units are pre-selected from system configuration — teacher confirms or adjusts  ·  DNA without a reason will block submission

Coordinator Review & Follow Up ~2 min

Goal: Ensure all sessions are marked; correct errors; handle locked sessions.

Steps

  1. Login as coord_se
  2. See notification banner — unmarked sessions in the hub
  3. Click Mark now → mark on behalf of the teacher
  4. Use the Calendar to spot any gaps across the week
  5. Open a locked session → can still edit and add a note
  6. Check Audit trail → all changes logged with name and timestamp
flowchart LR
    A["Notification:\nunmarked session"] --> B["Coordinator\nlogs in"]
    B --> C["Mark on behalf\nof teacher"]
    B --> D["Edit locked\nsession with note"]
    C --> E["Audit trail\nauto-recorded"]
    D --> E
        

ⓘ Coordinators can edit locked sessions (teachers cannot)  ·  Every correction is audit-logged with username and timestamp

ESO Campus Support ~1.5 min

Goal: Show narrowed campus-only scope and what ESO cannot access.

Steps

  1. Login as eso
  2. Dashboard shows only the assigned campus — no other hubs visible
  3. Open a student record → can view and edit attendance for that campus
  4. Point to the nav bar — no Admin, no Audit, no Claim links visible

ⓘ ESO is campus-scoped only  ·  No upload rights  ·  Cannot see other campuses or hubs

Manager Dashboard & Calendar ~1.5 min

Goal: High-level attendance picture across all hubs.

Steps

  1. Login as mgr
  2. Dashboard → 3 hub cards showing students, sessions, claimed hours
  3. Drill into a hub → campus breakdown
  4. Calendar → full term view; filter by campus or teacher
  5. Spot sessions needing attention at a glance

ⓘ Manager scope is configurable — can be single hub or all hubs  ·  Same correction rights as Coordinator within assigned hubs

What Each Role Can See

Screen Super AdminTeacherCoordinator ManagerESO
Today's sessions Own
Dashboard All hubsHub All hubsCampus
Calendar All hubsOwnHub All hubsCampus
Students All hubsHub All hubsCampus
Review queue Hub All hubs
Funding claim ✓ downloadview view
Audit trail Hub All hubs
Admin panel
↑ Back to top