Oldest open job vs local preference inside a group

Three material call-offs sat open in the forklift line-feed group. The newest one was beside the idle truck. The oldest one had been waiting twelve minutes. The driver took the short new hop. The starve stayed on the older line. ## What the shared list forces you to decide When [AOS](https://www.twinzo.com/glossary/aos-automated-ordering-system) (commonly known as [FGS](https://www.twinzo.com/glossary/forklift-guidance-system)) broadcasts to a [driver group](https://www.twinzo.com/glossary/driver-group), every member sees the same pool of claimable [work orders](https://www.twinzo.com/glossary/work-order). Location does not currently assign the nearest person automatically. Someone still chooses, or rules still rank what appears first. That choice is the management problem this page names. Keep the pool inside one ordering shape. Direct forklift pallet brings compete with other direct forklift jobs. [Tugger](https://www.twinzo.com/glossary/tugger) milk-run delivery jobs compete with other prepared trains, not with supermarket prep still unfinished. Mixing shapes in one list invents unfair claims that vehicle class should have blocked. The shapes are under [milk-run orders vs direct forklift orders](https://www.twinzo.com/glossary/milk-run-orders-vs-direct-forklift-orders). Dispatch studies on forklifts and guided vehicles keep finding the same tradeoff. Distance-first rules cut average empty travel and often cut average wait. They also let remote stops age badly when nearby hops keep winning. Waiting-time-first rules protect the longest wait and raise travel. Multi-attribute rules that blend distance with a wait threshold usually beat either extreme. Plants that never write the rule get all three behaviors at once and argue about fairness every afternoon. ## How teams set the rule without pretending nearest routing is free Most halls need a default of oldest-first inside the group for jobs of similar priority, with a short list of priority exceptions for true line stops. Local preference is fine when two calls have similar age, or when the older job is already claimed. Coaching should still stop a twelve-minute starve from losing to a two-minute convenience hop. The live hall and the stored [spatially oriented dataset](https://www.twinzo.com/glossary/spatially-oriented-dataset) show which pattern actually won. Priority configuration belongs in the same workflow layer as request types. How triggers and groups are set is under [request triggers in the workflow editor](https://www.twinzo.com/wiki/request-triggers-in-the-workflow-editor). Harder priority stacks for busy hours are under [priority rules that survive a busy hour](https://www.twinzo.com/wiki/priority-rules-that-survive-a-busy-hour). Group broadcast myths are under [group broadcast vs nearest-truck myths](https://www.twinzo.com/wiki/group-broadcast-vs-nearest-truck-myths). ## Where milk-run slack changes the fair claim When a [milk run](https://www.twinzo.com/glossary/milk-run) lap is quieter than theoretical consumption, forklift capacity freed by that afternoon may sit near a new call while an older call waits farther away. Local grab looks efficient for that truck and unfair for the hall. Keep the age default inside the forklift group, then let that freed capacity take the next ranked open job. Do not treat proximity as permission to ignore age, and do not dump those pallet jobs into the tugger milk-run delivery list. How that slack should move across lines is under [milk runs on theoretical consumption vs dynamic pull across lines](https://www.twinzo.com/wiki/milk-runs-on-theoretical-consumption-vs-dynamic-pull-across-lines). ## A typical unfair claim that was still legal At 14:20 the group shows two open material call-offs. Job A opened at 14:08 for line 4. Job B opened at 14:18 for line 5, three bays from an idle truck. The idle driver takes B. Line 4 waits longer. Nothing in the software forbade it if the UI sorted by distance or by newest. Sorting and coaching for oldest-first among equals would have kept the claim fair inside the same group broadcast model, while still letting near jobs win when ages are close. ## How teams decide the claim order is fair **1. Default to oldest open job inside the group for equal priority** - Write it into training and into how the list is shown. **2. Allow local preference only when ages are close or priority already ranks the near job** - Convenience must not beat a long starve. **3. Review accepts where a newer job beat an older one by more than a few minutes** - Pattern work belongs in weekly logistics review. **4. Do not pretend nearest auto-routing fixed fairness** - Offer scope is still the group. Ordering behavior sits under [material order automation](https://www.twinzo.com/material-order-automation) and [internal logistics optimization](https://www.twinzo.com/optimize-internal-logistics), with depth on the [features overview](https://www.twinzo.com/features). Pricing is under [pricing](https://www.twinzo.com/pricing). [Get in touch](https://www.twinzo.com/contact-us) if you want to walk whether your group lists reward oldest waits, or only the nearest convenience hop.