Transport partners and teams

Admin maintains the operating organizations and the transport partners used by dispatch. An organization carries its active setting, time zone and currency. A partner carries a stable code, contact details, address and eligibility note within that organization. Dispatcher chooses the partner when preparing a load so later questions reach the correct contact.

Staff membership links the person doing the work to the operating organization and platform user. This gives the team a consistent owner for loads and review decisions. The operating responsibility must remain clear when a dispatcher changes shifts or a supervisor covers another location.

• Keep partner identities stable. Use the partner code to distinguish businesses with similar names. Review the contact and address before assigning new work, and retain the partner reference on existing loads.
• Maintain organization context. Confirm the active operating organization and its time zone. Staff should interpret pickup and delivery times in the agreed context when work crosses regional boundaries.
• Map people to access. Connect team membership to the correct user and organizational responsibility. Admin reviews who can prepare work, who can decide and who needs read access for investigation.

Agree who is responsible for the partner directory and how eligibility notes are maintained. Decide when an inactive partner must stop receiving new assignments and how the team continues handling its open loads. A contact change should not create another carrier identity simply because the person answering the phone is different.

Review organization scope with the people who will use the app. A shared staff name must not become a shortcut around the intended access boundary. Confirm the time-zone convention for each team and how imported timestamps are interpreted. Freight amounts on loads are recorded in USD; an organization’s currency choice must not silently relabel those amounts.

An operating group uses the same carrier name at different locations. Admin imports each partner with its own code and organization context. Dispatcher selects the intended partner for a load, then asks the receiving shift to find the carrier contact from that record. The team should reach the correct contact without relying on the display name alone.

Next, deactivate a team member who previously owned open loads. Review how their responsibilities pass to the current dispatcher while earlier review and attachment history remains attributable. Rehearse access with an ordinary staff account from another organization. The check should include opening a load directly as well as browsing its list, because a filtered list alone does not define the access rule.

• Transport Partner Directory — Active partner contacts and eligibility notes within the operating context.
• Team Members — Active staff membership and the user identity behind operational responsibility.
• Loads Default List — The owner and transport partner beside work awaiting preparation or resolution.

Start plan and assign a load after the directory is reconciled. Use exception reconciliation for disputed partner outcomes. Prepare imports with the data model.