Delivery pools

Some work arrives as a list of places rather than a plan: forty addresses that all need visiting before six o’clock, with no decision yet about who drives where. Committing that to trips first thing in the morning means rebuilding them every time a driver calls in sick or an order lands late.

A delivery pool is where that work waits instead. You put the destinations in a pool with a deadline, and decide later — possibly much later — how to cut it into trips.

A pool carries a name, a deadline, a priority, an optional trip type, free-text notes, and a set of destinations. What it deliberately does not carry is a commitment:

• No driver and no vehicle.
• No stop order.
• No trip, and no schedule.

Each destination sits in the pool as unresolved until something turns it into a stop on a real trip. At that moment it becomes resolved and remembers which trip took it, so you can always trace where an address went.

The deadline drives a countdown badge that sharpens as it approaches — comfortable, then due soon inside a day, then urgent inside two hours, then overdue. It is a signal for the person watching the list, not a timer.

Nothing expires a pool automatically. Past its deadline a pool stays open and simply reads as overdue until somebody resolves it or cancels it. That is intentional: work that quietly vanished at six o’clock would be far worse than work that is visibly late.

There are three ways a pooled destination becomes a stop on a real trip.

• You resolve it on the pool’s dispatch board: group the destinations into runs, assign a driver and vehicle to each, and resolve. Each run becomes one trip, created as a draft with no schedule, ready for you to plan.
• Cooriroo proposes a split — a geographic clustering of the unresolved destinations into trip-sized groups with distance and duration estimates. It is a suggestion that seeds the board; you still assign and resolve.
• A driver claims it, where self-claim is enabled. A claim is a self-dispatch, so the trip is created already assigned to that driver and ready to start immediately.

Self-claim is a second toggle under Customization → Operations, available only once pools are on. With it enabled, drivers see the unresolved destinations from open pools and can take some into a trip of their own — optionally filtered to what is near them, what is due soonest, or what has not been visited lately.

With it off, the server refuses both the listing and the claim. The driver app hides the entry point as well, but hiding a button is not the control — the refusal is.