Loadouts¶
For dispatch · approving and working loads
A loadout is one truck's worth of orders that a routing run produced. The loadouts board is where you sign off the good ones and deal with the ones that need a second look.
The lanes¶
The board splits loads into three lanes:
| Lane | Pill | What's here |
|---|---|---|
| Draft | Draft | Fresh from a routing run, waiting for a human decision. |
| Approved | Approved | Signed off and ready to ship. |
| Locked | Locked | Loads that hit a conflict and need review before they can move. |
The main board shows draft loads only — approved and locked each have their own tab so the working lane stays uncluttered.
Approve or reject¶
Open a draft load to see its trucks, the orders on them, and the coil count. Then:
- Approve — the load moves to the Approved lane and is ready to ship.
- Reject — the load goes back so the orders can be re-routed.
Loads are approved or rejected — never deleted
There's no delete on a routed loadout. Rejecting returns the work to be routed again; it doesn't throw anything away. This keeps the audit trail intact.
Coil count¶
Each load shows a coil count so you can sanity-check what's actually on the truck. Atlas calculates it on the server from the load's materials and planned units, so a produced coil and its original planned lot count once — not twice.
Locked loadouts¶
A load lands in the Locked lane when a fresh sync changes an order that was already sitting in an approved load — the load and the new Invex data no longer agree.
To clear it:
- Open the locked load. Expand it to see the latest merge conflict — what changed between the load and the new sync.
- Decide: re-route the affected orders, or accept the load as-is if the change doesn't matter for shipping.
Don't ship a locked load without looking
Locked means "the data moved under this load." Always read the conflict before releasing it.
Underfilled loads¶
If a load is under its target fill, Atlas can flag it against the routing profile so you can choose to hold it for more work or send it anyway. Fill is measured against the profile that was active when the run happened.