1
Confirm your workspace and profile
Check the school name in the workspace selector. Under User Settings, confirm your name, appearance and default workspace.
2
Add the school year and terms
In Settings → Term Structure, add each term’s name, start date and end date. See Term structure.
3
Configure the bell structure
In Settings → Periods, import teaching times from LISS or create the week manually. Hide breaks that should not appear in the timetable builder. See Periods.
4
Review workspace settings
Add school branding and decide which production-ready portal and workflow capabilities your school will use. Configure how daily drafts are published.
5
Connect LISS when available
Create the LISS connection and complete a sync before importing students, teachers or bell times from LISS.
6
Build the learner directory
Import from LISS, upload CSV or add learners manually. Review year level, priority, funded hours and always-support requirements.
7
Build the support-staff directory
Add names, work email addresses, working days, weekly hours and active status. Link accounts and send portal invitations only after records are correct.
8
Check teachers
Review the read-only teacher directory synced from LISS. Resolve missing or duplicate emails before enabling teacher portal use.
9
Invite coordinators
Invite other administrative users from User Management. Keep staff portal invitations in the support-staff directory rather than User Management.
10
Build and review planned support
Allocate support in the Timetable Builder. Add groups and staff commitments if that workspace capability is enabled.
11
Pilot the portals and daily workflow
Test one staff account, one teacher account and one daily change before rolling out broadly.
Readiness checklist
- Term dates cover the intended planning window.
- Teaching periods appear on the correct weekdays and times.
- Learner external IDs match LISS where integration is used.
- Staff emails, working days and hours are correct.
- Teacher emails are present in the synced directory.
- Portal capabilities match the school’s rollout plan.
- At least one coordinator can access the workspace.
- A sample planned allocation appears correctly.
- A draft daily change can be saved, reviewed and published.
Screenshot placeholder SW-008: Completed setup sequence shown as a visual checklist.