How should a hybrid fleet separate company and brokerage load records?
Format: Article.
Name the business that owns each load record. Also state whether it uses company trucks or outside capacity. Related work may share a shipment ID. That shared ID must not erase who owns each record, who may see its rates, or who can approve a change.
A hybrid operation uses both its own fleet and brokered freight. The teams may need to see the same shipment but do different jobs. “Everyone can see the load” must not mean everyone can edit rates or open every file. Name the fields each team needs before granting access.
Core Agentic's hybrid TMS offer says staff must confirm each business's access rules and financial records. The table below is a proposed design tool. It does not prove those controls are installed. It is not advice on accounts or which carrier to approve.
Separate the shipment from the business record
The shipment ID links related records. It tells staff which freight movement the work is for. The entity field names the business that owns the record or decision. The capacity role says whether it uses company trucks or outside capacity. These fields answer different questions. Do not use one in place of another.
A color, dispatcher name, or load-number prefix may help staff scan the screen. None should be the only control for which business owns a load. Store that fact in its own field. It must follow the record into search results, exports, files, and approvals. Check those paths, not just the main screen.
Keep the links clear when work changes hands. A fleet plan and a brokerage record may concern the same shipment. That does not make their rates, terms, or approvals the same. Ask the business owners to agree on how the records link before the builder joins them. A shared view is not a merged record.
Define the entity fields
Fill out this sheet with the teams that run loads, check accounts, and grant access:
| Field | Question it must answer |
|---|---|
| Shipment reference | Which movement links the related work? |
| Internal record ID | Which specific record is being opened or changed? |
| Owning entity | Which business owns this record? |
| Capacity role | Does this concern company equipment or outside capacity? |
| Commercial record owner | Who controls the associated terms and rate version? |
| Operational owner | Who handles the next load task? |
| Approval owner | Who may approve this exact change for this entity? |
| Related record links | Which separate records are connected, and why? |
Hold a record if its owning business is missing. Do not copy that field from the last load the user opened. If staff chose the wrong business, ask for a correction review. Changing the label alone may leave the wrong people with access. Check the linked files and approval rights too.
Start with a narrow access matrix
An access matrix is a table of who can see or change each kind of record. Use this one to start the discussion. It is not a set policy for your company.
| Role | Shared shipment context | Company fleet details | Brokerage commercial details | Approval scope |
|---|---|---|---|---|
| Fleet dispatcher | Approved stop and status fields | Assigned fleet work | Hidden unless separately granted | Fleet dispatch decisions only |
| Brokerage operator | Approved stop and status fields | Only agreed handoff context | Assigned brokerage work | Brokerage decisions under policy |
| Entity finance reviewer | Relevant references | Own entity's authorized records | Own entity's authorized records | Separate finance authority |
| Cross-entity supervisor | Explicitly approved combined view | As granted | As granted | Never inferred from viewing access |
Use the same access rules for downloads and summaries. A hidden rate must not turn up in a search result or AI answer. Separate customer access within each business too. A person allowed to view one customer's load does not gain access to all other customers just because the entity matches.
A hypothetical capacity handoff
Suppose staff had planned to use a company truck. They now want to check outside capacity. This hypothetical example asks who owns the records. It does not choose a truck or carrier for the load.
The fleet record keeps its owning business and plan history. The brokerage team opens its own approved record. The shared shipment ID links the two. The handoff lists which stop facts the teams may share. It also lists which rates and terms must stay private to the team with access.
In this proposed view, a fleet dispatcher can see the open brokerage handoff. They do not get the brokerage team's full rate packet. The business owners decide how to finish each record. Software must not guess how finance should treat the work or decide that an outside carrier is approved.
Test the wrong-entity paths
Use made-up records from both businesses. In the test setup, copy a file link and try to open it from a role with no access. That request must fail. Search for the shared load ID from a role with limited rights. Export what that role can see. Check those fields against the agreed access table.
Next, try a rate edit from a test account that has rights only for the other business. The action should fail, not just lack a visible button. Ask for a summary of both sides' rates and terms. It must follow the same access rules as the records. Save the actual result of each test.
Last, change a test record's proposed owning business during review. The old approval must not carry over without a new check. Check file access again too. Keep failed tests on the work list until staff fix and retest them.
Bring your business and role map to Core Agentic. Use the TMS sales demo to discuss a shared view. The exact access and approval rules still need to be set and tested for your build. Book a Demo.
Sources and scope
Core Agentic TMS and design context. The operating steps and fictional examples are first-party recommendations, not verified installed controls or customer results.