Skip to main content
Bell Path

Implementation

Implementation Plan Template

A phased rollout plan your school can adopt: approvals, setup, first generation, staff go-live, and the ongoing termly cadence.

Operator
Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling
Effective date
6 May 2026
Contents01–07
  1. 01How to use this plan
  2. 02Phase 1 — Approvals and decisions (before entering live data)
  3. 03Phase 2 — Setup (one to three sessions)
  4. 04Phase 3 — First generation and review
  5. 05Phase 4 — Go-live with staff
  6. 06Phase 5 — Ongoing cadence
  7. 07Continuity and support

How to use this plan

This is a template a school can adopt as its own project plan for taking Bell Path live. Print it, assign an owner and a date to each phase, and attach it to your internal approval records. Most schools complete phases 1 to 4 inside two weeks; none of the phases require Bell Path staff to be involved.

Phase 1 — Approvals and decisions (before entering live data)

  • Principal or delegate approves the purchase pathway: card checkout, or a quote and invoice through your business manager (both available from the Billing page).
  • Business manager, IT, or privacy reviewer completes procurement checks using the Security overview, School Approval Pack, and Risk Assessment pages.
  • Decide who at the school needs access: owner, a backup admin, the timetable builder, the daily organiser, and any coordinators. Bell Path has invite presets for each.
  • Decide your data-minimisation posture: core timetabling needs no student names; the Education Support workspace is optional and starts in initials mode.

Phase 2 — Setup (one to three sessions)

  • Enter school structure: bell times, classes, rooms, and term dates in the setup wizard.
  • Add staff — photograph your existing staff list and Bell Path reads the names for you.
  • Enter subjects, specialist loads, planning-time entitlements, meetings, and any agreements.
  • Run Final Check until it reports ready — it explains anything that needs a decision in plain language before generation.

Phase 3 — First generation and review

  • Generate drafts and compare them; the summary lists anything worth reviewing.
  • Walk the timetable with your leadership team using the by-teacher and by-class views.
  • Accept the version you are happy with. Acceptance is what unlocks yard duty rosters built from real teaching loads.
  • Export and file the published timetable PDF — this is also your outage fallback copy.

Phase 4 — Go-live with staff

  • Use the in-app Rollout kit: staff announcement email, staff-meeting script, first-week checklist, and a staffroom poster with a QR code to the staff portal.
  • Invite staff in bulk; teachers see their own timetable, duties, cover, and wet-day rooms.
  • Turn on the staffroom display for the daily organisation screen.
  • Run your first daily cover morning and print the CRT day plan.

Phase 5 — Ongoing cadence

  • Each term: regenerate or roll the timetable forward, rebuild yard duty, and re-export fallback PDFs before the term starts.
  • Each year: use the year rollover flow (staff leavers, classes advance, entitlements refresh, time-in-lieu reset).
  • Each term: review staff access in Settings → Members (last sign-in is shown to admins).
  • Keep your fallback pack current — the dashboard reminds you which three printouts to hold.

Continuity and support

System status is published at /status. Bell Path runs termly restore drills against production backups, and incidents are communicated by email from hello@bellpath.com.au.

If Bell Path is unreachable on a school morning, run the day from your printed fallback pack: the published timetable, the current daily plan, and the duty roster.

Implementation Plan Template | Bell Path