Partners and organizations

A load belongs to an organization and names a transport partner as its counterparty. The organization record holds its active state, time zone and currency. Team membership links a user to an organization and records the member’s active state, role name and time zone. These references give the dispatch team a way to see who owns a movement and which operating context applies before it begins.

A transport partner record holds a name, code, active state, contact, address and eligibility note. The Dispatcher uses that directory when selecting the partner for a load. The Dispatcher checks the eligibility note when choosing a partner and confirms its current standing with the source that owns it. The partner’s organization reference keeps the directory connected to the operation it serves.

• Maintain. Admin maintains organization, staff membership and transport partner records.
• Select. Dispatcher associates the load with its organization, team owner and partner.
• Review. Operations Manager follows the same references when investigating delivery or custody evidence.

A concrete case is a dispatcher working across organizations with different time zones. Before assigning a vehicle or promising a delivery time, the team verifies the load’s operating organization and owner. The partner directory supplies the carrier’s current contact and eligibility note. When an exception arrives on the next shift, the owner and organization references tell the Operations Manager where to start.

Agree who is allowed to create and deactivate organizations, staff membership and partner records. Decide how operating time zones should appear in assignment schedules and stop windows. The organization currency identifies operating context, while the load freight amount is recorded in USD. If finance needs settlement in another currency, define that financial process and its exchange-rate authority separately.

Set a review cadence for partner contacts and eligibility notes. Decide which external carrier records or fleet systems provide authoritative status, and how the Dispatcher handles a conflicting local note. Use staff role names on membership records to identify who prepares, decides and investigates work. Set access for those responsibilities during the pilot.

Create a load for an active organization and select its team owner and active transport partner. Check that the owner belongs to the intended operating scope and that the partner contact is current. Hand the load to another shift and ask the Operations Manager to find the right owner, partner and organization from the record alone.

Then repeat with an inactive partner. The Dispatcher should pause and resolve the selection before release. Try a team member assigned to a different operating organization and confirm that access and ownership rules fit the agreed policy. Use a cross-time-zone stop to verify that the promise, appointment and assignment interval refer to the intended moments. Those checks are easier to perform on a representative load than during an urgent exception.

• Transport partner directory — Active partners with contact and eligibility context.
• My team membership — The current member’s organization, role name and time zone.
• Active load lifecycle — Organization, owner and partner context for moving freight.

See load planning and dispatch and exception review.