Control spot freight approvals when contracted capacity fails

The lowest spot quote may not serve the shipment

A contracted carrier declines a load shortly before its collection cut-off. Two spot offers arrive. The cheaper offer uses an unsuitable vehicle or cannot meet the required window. The more expensive one appears feasible, but the dispatcher still needs the appropriate spending approval.

The workflow should make these decisions explicit. First establish the failed contracted assignment and the shipment requirement. Then assess feasible offers, approve the selected commercial basis and obtain the carrier’s acceptance. A price approval alone does not create transport capacity.

This is especially important when time is short. Repeated calls and messages can otherwise produce two carrier awards, an unapproved premium or a booking whose equipment differs from the quote reviewed by the approver.

Start with the exception and a stable shipment requirement

Record the original carrier, contracted assignment reference, decline or failure evidence and the time the exception became actionable. Avoid opening a spot request merely because an acknowledgement has not yet arrived if the original assignment might still be active.

The request should identify the shipment, equipment and service requirements, collection and delivery windows, relevant location details and the quote response deadline. State what charges each offer must include and which items remain conditional.

The Oracle Transportation Management 26C — Spot Bid Tenders Configuration documentation describes timed spot-bid tendering and automatic award by adjusted cost in the documented configuration. That is a product behaviour to examine carefully. A supervised approval pilot must confirm how its actual configuration controls automatic evaluation and award; it should not assume a documented auction workflow already implements the organisation’s approval policy.

Use redacted or synthetic shipment details for the initial replay. Live carrier requests belong within the normal authorised procurement and dispatch process, not an unattended evaluation exercise.

Illustrative offers: suitability comes before the price comparison

Assume a fictional contracted movement costs ₹20,000, but the carrier declines. The shipment needs the specified suitable vehicle and collection by 15:00 IST.

Carrier A quotes ₹24,000 but proposes a different, unsuitable equipment configuration and a 16:00 collection. Carrier B quotes ₹27,000 for the required configuration and a 14:00 collection. Both quotes are assumed to use the same stated charge basis for the comparison.

The relevant comparison is not simply ₹24,000 against ₹27,000. Offer A does not serve the current requirement. Selecting B adds ₹7,000 to the illustrative contracted charge, subject to the actual approved quote and final service.

Suppose the authorised spending ceiling for this request is ₹28,000. B’s ₹27,000 offer fits that ceiling, but a later counterquote of ₹29,000 does not. The changed commercial basis requires renewed approval through the applicable process. An old approval should not silently attach to a higher offer.

Keep approval, award and acceptance separate

A spending approval records who authorised the selected scope and amount. An award records the instruction issued to the selected carrier. Acceptance records the carrier’s response to that instruction. These events can occur close together while retaining different meanings.

The selected carrier may change its timing or conditions when accepting. Such a response needs review against the approved offer. It should not become an unconditional accepted booking merely because the message contains an affirmative word.

Also distinguish the carrier premium from any customer charge. Approval to spend ₹27,000 does not authorise billing the customer an additional ₹7,000. That requires the relevant commercial agreement and evidence.

Compare a controlled register with native tendering

A controlled exception register can work for a small number of urgent requests if one dispatcher owns the active award. It should retain offer versions and approval evidence. Its main risk is simultaneous action by several people under time pressure.

An existing TMS may support offers, tender responses and audit history. Test the actual award configuration, response deadline and approval controls. A vendor feature labelled “spot tender” may implement an auction model that differs from a supervised commercial decision.

An extension can connect a failed contract assignment to an approval queue and then to tendering. Its value lies in preserving the authorised offer and preventing conflicting instructions. It should not become an independent carrier master or bypass procurement controls.

Use the two-offer example to compare these options. The system should exclude the unsuitable offer from an automatic price-only selection and show why the selected offer requires the applicable approval.

Bound a pilot around a small exception population

Choose one lane or service group with a known carrier pool and a defined approval matrix. Limit the pilot to spot requests arising from documented contracted-capacity failures. Keep other procurement situations outside scope until their requirements are reviewed.

Start with historical replay, including declined requests and cases that missed the required window. Establish the baseline: exception requests, time to a feasible accepted carrier, unapproved changes, duplicate awards and total comparable charges.

The baseline should distinguish time awaiting approval from time awaiting a carrier response. Combining them into one duration makes it difficult to identify whether the bottleneck is commercial authority or actual capacity.

During supervised use, designate one active request owner. Review each award before it is issued through the established channel. The pilot does not need to automate external communication to establish whether the decision record is useful.

Test uncertainty before testing speed

Replay a carrier acceptance that is delayed or whose acknowledgement is lost. The dispatcher must check the existing tender state using the original reference before awarding the same shipment to another carrier. An uncertain response is not a confirmed decline.

Test withdrawal of the first award and require the relevant acknowledgement or authorised resolution before treating another award as unconflicted. Keep the original instruction and cancellation history visible.

Replay a quote change after approval, a vehicle substitution and a collection time moving beyond the cut-off. Each should return the affected aspect to the appropriate reviewer. The system must not retain an overall approved status while its material basis changes.

Also test an approver outside their authority and a user viewing another customer’s offers. Access should be limited to the information and decisions the role needs. A technical administrator account should not be the only account used in acceptance testing.

Define stop conditions and reconcile active awards

Pause the pilot if it issues duplicate awards, loses the selected offer version or allows spending approval outside the agreed authority. Return to the existing controlled tendering process with one named owner maintaining the active-request register.

Recovery begins with the carriers and shipments potentially affected. Reconcile which instructions were issued, which were accepted, which were withdrawn and which remain uncertain. Do not infer the current award solely from the latest internal status.

Before restart, the transport and commercial leads should review the reconciled population and the failed test. Demonstrate that the corrected process preserves one coherent assignment and the applicable approval basis.

If the TMS’s automated auction behaviour cannot be constrained to the approved pilot design, keep the evaluation in replay or supervised manual mode until the configuration is resolved. The operational team should not discover an unintended automatic award during a live exception.

Review the commercial and service outcome

Compare the time to a feasible accepted carrier, approval effort and deviations from the reviewed quote. Include cases where no suitable offer was available. A process that reports only successful awards hides the actual capacity limitation.

Review invoices against the approved scope and actual service. Additional charges need their own evidence and authority. The tender record should make that review easier without claiming that every quoted amount is automatically payable.

For a focused pilot assessment, prepare a redacted contract failure, two comparable offers and the current approval matrix. The output should be a bounded workflow, test set and recovery plan.

Spot-freight control works when the team can explain why an offer was feasible, who approved it and which carrier actually accepted the assignment. Faster selection is useful only when those decisions remain clear.

Next actions

1. Define the contracted-capacity exception and the shipment requirement.
2. Align offer scope and suitability before comparing prices.
3. Test approval changes, uncertain acceptance and withdrawal before issuing another award.
4. Review a supervised pilot with transport and commercial owners before expanding automation.