School scope
Tenant and school boundaries
Excursion information belongs inside the appropriate school context. Public marketing pages must not blur that boundary or expose product data.
Trust and operating limits
Excursion software must be careful before it is clever.
Excursa deals with safety-sensitive school workflows. The public website should make the product posture clear: scoped access, visible evidence, careful language, and no claim that software replaces school procedure.
Role scope
Teacher, admin and platform roles
Teacher, admin and platform-admin surfaces should remain separate because they support different decisions and different access levels.
Safety-sensitive data
Medical, consent, transport and attendance
These workflows need clear handling because mistakes can affect real students, staff and families.
Operational caution
Excursa supports school excursion planning and operations. It does not replace school policy, professional judgement, duty of care, emergency services, or required human checks.
Evidence, not theatre
The product should help schools understand what is ready, what needs action, and what changed. It should not create a false sense of safety.
Claims need proof
The website should avoid claims about adoption, certification, integrations, automation or location tracking unless implementation and evidence support them.
Clear public/product separation
The corporate website explains the product. The authenticated product and operational surfaces remain outside the public marketing navigation.
Public website
Homepage, product overview, school audience pages, trust posture and enquiry capture.
Product and operational surfaces
Teacher, admin, platform-admin, consent, status and waitlist-dashboard routes remain separate from the public website.