Organizations and partners

Organizations hold the school district or operator that owns the transportation records. Each has a code, active flag, time zone and currency. A run points to its organization, owner and transport partner. That combination tells the team who is responsible for the journey and which provider is involved, even when similar route names appear elsewhere in the workspace.

Team member records connect people to organizations and user accounts. Their active flag, role name and time zone help the App Administrator maintain membership. Transport partner records hold the contracted operator or provider, with its code, contact details, address and eligibility note. Keep partner records current so the Dispatcher selects the right counterparty for a run.

• Operator. Set the organization code, active state and time zone before loading daily runs.
• Membership. Connect each team member to the correct organization and user account.
• Provider. Maintain the transport partner’s identity and eligibility note for selection on a run.

The Operations Overview should be read within the appropriate operating context. The run itself retains its organization link, so a Supervisor or Auditor can follow the record back to its owner.

Agree the source of organization and partner codes, who updates contact information, and how an inactive provider is removed from daily selection. Decide how team membership changes when a Dispatcher moves between organizations or leaves the operation. Access should reflect the person’s current responsibility, while historical decisions continue to show the reviewer who made them.

Currency appears on the organization and a freight amount appears on the run. Agree how that amount is used in this transport operation before using it in any comparison. It does not describe student fares. If identity comes from another system, map stable user identifiers to the membership record and test that disabled access no longer exposes operational records.

A district uses a contracted bus operator for a morning route. The App Administrator creates the organization and partner with their stable codes. A Dispatcher has a district team member record and owns the run; the run names the contracted provider as its counterparty. The Supervisor can inspect these links beside the driver and vehicle assignment.

Later the partner’s eligibility note changes. The administrator updates the partner record for future planning. The existing run still keeps its counterparty link and its dated decisions. If the Dispatcher becomes inactive, another authorized team member must take over upcoming work. The earlier review and operation receipts remain attached to the run for audit.

• Active transport partners — Select an active provider and inspect its operator and eligibility note.
• Run status list — Follow each run back to its organization, owner and counterparty.

Prepare a run and confirm its assignment.