Approval pack
School Approval Pack
A printable pack for schools reviewing Bell Path before entering live operational data.
- Operator
- Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling
- Effective date
- 6 May 2026
Top actions
Hand this off to a principal, business manager, or ICT lead in one step. Nothing here shares school data: these actions only act on this public page.
Go straight to the evidence or checklist your reviewer needs.
Decision guide
What the school needs to decide.
Read across each row for Bell Path's current position and the action the school should take before entering live operational data.
ST4S and external approval
Not externally assessedData residency
Offshore processing possibleCore timetable data
Student names not requiredFeature-specific data
School controlledSubprocessors
6 named providersApproval record
Keep with school recordsCommercial terms
Price and refund position.
- Price today
- Founding schools help shape Bell Path during a controlled rollout. The first five pilot schools get year one complimentary, then $1,000/year for two more years. Schools 6-20 join for one product-shaping year at $1,000. After that, standard size tiers run from $679 to $12,599 per year based on verified enrolment.
- Trial and guarantee
- Full refund within 30 days. Pro-rated review days 31-90. Bell Path also reviews requests under the Term 1 timetable-fit money-back guarantee even if outside the first 30 days.
How to use this pack
This pack is written for principals, assistant principals, business managers, ICT leads, and privacy reviewers who need a practical summary before a school enters live operational data into Bell Path.
Schools can print this page and keep it with internal procurement, privacy impact assessment, security, School Council, or leadership approval records. It supports review; it does not replace a school, sector, ST4S, Department, or legal assessment.
What Bell Path is
- Specialist timetabling, APT and agreement planning, daily cover support, yard duty planning, wet day planning, event timetables, and operational exports for Australian primary schools.
- A school-owned workspace where leadership can model, review, publish, and export operational planning outputs.
- A support tool for school decision-making. Generated timetables, cover plans, and public calendar outputs still require school review before publication or action.
What Bell Path is not
- Bell Path is not a replacement for Compass, CASES21, eduPay, Microsoft 365, Google Workspace, or other Department-provided core systems.
- Bell Path is not currently represented as Department-approved, ST4S-assessed, ISO-certified, SOC 2-certified, or listed on a government panel unless Bell Path provides that written confirmation separately.
- Bell Path is not designed to store health files, behaviour records, parent contact databases, enrolment records, or whole-student profiles.
ST4S readiness status
Schools may need to check Arc Software and Safer Technologies 4 Schools assessment material before adopting software that is not provided by their sector or Department. Bell Path should be treated as requiring the school’s normal software approval checks unless a current written Bell Path statement says otherwise.
Bell Path is being documented in a way that supports ST4S-style review: clear data categories, subprocessors, access controls, public-sharing limits, support pathways, and data minimisation guidance. This is readiness material, not a claim that an ST4S assessment has been completed.
Pre-fills a request we answer in writing within one working day, so the reply can go straight into your review records.
Data storage and residency
Bell Path is operated from Australia but uses cloud service providers. The current repository and deployment posture should be treated as involving offshore processing unless Bell Path has separately agreed and verified an Australian-only residency arrangement in writing.
Schools that require Australian-only data residency should ask for written confirmation covering the application runtime, database, Redis or queue services, export storage, email, monitoring, payment records, backups, and support tooling before entering live data.
Pre-fills the written-confirmation request covering runtime, database, backups, email, and support tooling. Replies come within one working day.
Data collected by feature
- Core timetable setup: school name, staff names and roles, classes, rooms, subjects, bell times, meetings, availability, APT requirements, constraints, and generated timetable records.
- Agreements: staff member, original allocation, agreed allocation, compensation details where entered, reason, status, review history, and timestamps.
- Daily operations: cover plans, CRT or replacement teacher names where entered, yard duty and wet day planning records, public calendar events, and export metadata.
- Education Support: student names, year levels, funded minutes, assigned blocks, ES staff, and support notes only where the school chooses to use that feature.
- Account, billing, support, security, analytics, and audit records needed to operate, secure, support, and bill for the service.
Data Bell Path does not need
- Student names are not needed for core timetable generation.
- Health information, behaviour records, disability details, family contact details, home addresses, and enrolment files should not be entered unless a specific feature genuinely requires limited information and the school has authority to use it.
- Schools should use class labels, year levels, initials, groups, or staff-only notes where that is enough for the workflow.
Public calendar and school-code access
Bell Path public calendar links are intended for non-sensitive parent and student visibility. They should only publish items the school has chosen to make visible.
A school code reduces casual access but is not a substitute for authenticated staff access. Staff-only notes, drafts, internal admin notes, reminders, unpublished items, and non-public checklist items are redacted before public exposure.
Access, audit, and accountability
- School users authenticate before accessing protected workspaces.
- Workspace access is checked against school membership and role.
- School-scoped audit records are used for sensitive changes such as exports, timetable lifecycle actions, member changes, account deletion, and selected operations calendar actions.
- Schools should remove stale user accounts and avoid sharing logins.
Deletion, export, and retention
Schools can request export, deletion, account, or procurement assistance by contacting hello@bellpath.com.au. Bell Path may retain records where required for legal, accounting, security, backup, audit, dispute, or abuse-prevention reasons.
Schools should keep their own copies of published timetable, export, and approval records according to their normal recordkeeping rules.
For your finance office / new-vendor setup
- Legal entity: Dimitrios James Gregory Hooke ABN 59 429 101 462 trading as Bell Path Timetabling.
- Registered business name: Bell Path Timetabling.
- ABN: 59 429 101 462.
- GST registration status: not currently registered for GST.
- Contact email: hello@bellpath.com.au.
- Payment methods: card via Stripe checkout; invoice and bank transfer on request.
- Bank details are issued on the invoice itself and are not published on the website.
Subprocessors
Bell Path uses service providers where reasonably needed to host, secure, monitor, support, and bill for the product.
- Railway for application hosting, database, Redis, deployment, and infrastructure services
- Stripe for payment processing, hosted checkout, invoices, and subscription records
- Resend for transactional email delivery where configured
- Sentry for application error monitoring where configured
- Google for optional Google sign-in, related authentication services, and consent-based advertising conversion measurement where enabled
- OpenAI for reading staff-list photos a school chooses to upload, to extract names during setup, and for consent-based advertising conversion measurement where enabled
Support during busy school periods
Bell Path includes an in-app support form that captures the page, request type, impact level, and recent workflow context so urgent timetable, export, cover, or setup issues can be triaged more quickly.
Schools should still keep local fallbacks for critical operational records, including downloaded timetable PDFs and any information needed to run the school day if an online service is unavailable.
Current service health is published on the Bell Path System status page. Bookmark it so you have somewhere to check if the app is ever unreachable.
School review checklist
Tick each point as the school works through it, then record the decision below.
0 OF 6 CONFIRMED
Review record
Complete this on screen before printing, or print first and fill it in by hand. Ticks and sign-off details stay in this browser. Nothing is sent to Bell Path.
Keep the completed review with the school's records.
Your browser's print dialog can save the complete pack as a PDF.