Route proposals

A route proposal belongs to a load and organization. Dispatcher can record its revision, estimated miles, capacity units, generation time and optimization version. Those values give Transport Supervisor a concrete route candidate to examine. The proposal status separates Draft work from Submitted review and records an Approved or Rejected outcome. The estimate describes a proposed route; actual stop and delivery times describe the movement that followed.

• A defined candidate. Each proposal belongs to a parent load and carries its own revision. The reviewer should decide on that version.
• A visible queue. Submitted proposals appear in Route Review Queue for Transport Supervisor.
• A separate decision. review decisions records the reviewer, source revision, decision, date and reason against the load.

A proposal can include the version of the optimization method that generated it. That is useful when the team compares revisions with different estimated miles. It does not replace a human check of stop windows, vehicle capacity or partner commitments. A lower mileage estimate can still be unsuitable if the route cannot satisfy the delivery promise.

Agree where route candidates come from and who enters the estimate and generation details. Set a consistent meaning for capacity units and how they relate to vehicle capacity. Decide what a submitted proposal must contain before the supervisor reviews it. Establish how the team handles a returned or rejected candidate, including whether it creates a new revision and what reason is recorded.

For the first rehearsal, use a load with ordered stops and a credible delivery window. Enter a Draft proposal, add its mileage estimate and optimization version, then submit that exact revision. Ask a Transport Supervisor who did not prepare it to inspect the load, stop windows and proposed assignment. Record the decision with a reason. Make a material change to the route and confirm the team reviews the new revision rather than relying on the previous approval.

A Dispatcher proposes a route for a load with two timed stops. The first revision estimates the shortest path but misses an early stop window. Transport Supervisor returns it with a reason. Dispatcher revises the candidate and submits it again. The supervisor approves the later revision, and dispatch uses that reviewed plan when preparing the assignment. The review history remains useful if the load later enters Exception: the team can see which proposal was considered and why.

• Route Review Queue — Submitted route candidates awaiting a decision on their current revision.
• Route Proposal Board — Draft, submitted, approved and rejected candidates grouped by status.
• Review Decisions — Recorded decision reasons and the revision each reviewer considered.

See route review, assignment and dispatch and the data model.