Product workflow

From planning to day-of operations to evidence review.

Excursa is being shaped around the real stages of a school excursion, with safety-sensitive information kept visible to the right people at the right point in the workflow.

Plan

Create the excursion context, attach students, organise transport, and prepare consent information without losing the school or excursion boundary.

  • Excursion details
  • Student participation
  • Transport records
  • Consent setup

Prepare

Make readiness visible before departure: consent, groups, medical context, staffing, transport and compliance evidence.

  • Medical readiness
  • Staff and group allocation
  • Compliance checks
  • Departure readiness

Run

Give teachers a day-of workspace that keeps the current excursion attached while moving between operational tasks.

  • Roll call
  • Transport detail
  • Seating plan
  • Urgent support

Review

Support follow-up with clearer evidence about what was ready, what needed action, and what happened during the excursion.

  • Readiness summary
  • Action evidence
  • Operational history
  • School review

What the first version should not pretend

The product is safety-adjacent. The public website should be clear and grounded: Excursa supports school procedure; it does not replace duty of care, emergency services, school policy, or human judgement.

Purposeful

Focus on the workflows that reduce confusion and make readiness visible.

Careful

Avoid claims about production adoption, certification, automation or integrations unless evidence exists.

Clear separation from the product app

The pages under this public site explain Excursa. The existing teacher/admin routes remain product surfaces with their own context, role and safety boundaries.