Use of the platform assumes disciplined, authorized school operations.

Users are expected to access only the roles, routes, and school contexts assigned to them. Platform admin use, school staff use, parent use, and student use each follow separate product surfaces.

Attempting to bypass those boundaries, impersonate another user, or operate outside an assigned school context is not aligned with intended usage.

Many accounts on the platform exist because a school creates or authorizes them. Schools are responsible for the correctness of user invitations, role assignment, and school-level access decisions.

Schools are also responsible for removing or updating access when staff, parents, or operational circumstances change.

SchoolPilot provides the software environment and the workflows described in the product. It does not replace school judgment, policy decisions, fee policies, grading policy, or regulatory obligations.

The product supports those workflows, but the school remains responsible for the correctness of its records, messages, and published outputs.

The platform continues to evolve. Modules, screens, and workflows may be improved or extended as the system grows, provided those changes stay consistent with the broader operating model of the product.

When important product changes affect a tenant’s workflow, they should be managed through normal platform communication and rollout practices.