Partners and organization

A load belongs to an organization and names a transport partner as its counterparty. The organization carries its code, active state, time zone and currency. The partner carries a code, contact, address, active state and eligibility note. These details let the team distinguish shipments handled by different business units and carriers.

Team members link to organizations and user accounts. A load owner is a team member, so ownership can stay with a named person even when the carrier or dispatcher changes. This context also supports a clear review boundary: the person preparing an operation should not be the independent reviewer of that same revision.

• Set operating scope. Give the organization a stable code, time zone and currency.
• Maintain carriers. Keep each partner contact and eligibility note current.
• Name the owner. Link the load to an active team member in the right organization.

Agree the organization codes, operating time zones and currency context before importing loads. Set a stable partner code for each carrier and confirm who maintains the contact and eligibility note. Keep inactive parties identifiable for history while preventing them from being selected for new work under your operating rule.

The App Administrator maintains company, member and partner records. The Dispatcher selects the correct organization and partner when creating a load. A Transport Supervisor can inspect the load context when evaluating a booking or exception, and an Auditor can trace that context later.

Imagine two business units using the same carrier on different lanes. Their loads remain attached to the right organization and owner. If a carrier contact changes, the partner record can be updated without changing the load number or the evidence recorded for a prior movement. The team can report recorded freight by partner without conflating the organizations.

Before the next load is entered, the App Administrator checks whether the partner is active and the team member belongs to the operating organization. The Dispatcher then selects those records on the load. An Auditor can follow the same references later without relying on a carrier name typed into a note.

• Load Register — See each load beside its owner and counterparty.
• My loads — Give a named owner their own operating queue.
• Active equipment — Check the fleet context used for assignments.

Read the operating process and the related handoff. Set up roles and rehearse the case in implementation.