10 to the 23 AI logo

Domain Atlas

Logistics dispatch & scheduling AI

AI in logistics optimizes routing, dispatch, and warehouse task assignment, and the pattern that defines its governance is that the same system which optimizes the work also manages the worker doing it. A parcel carrier's route-optimization system is a documented operations-research success — reported to save on the order of a hundred million miles and millions of gallons of fuel a year — and the same system dictates the route to the driver and monitors adherence through telematics, so the efficiency is enforced through workplace surveillance and the driver's discretion is what it replaces. A warehouse's algorithmic management pairs a genuine human-robot picking benefit with a documented injury-productivity trade-off: when the algorithm sets the pace, regulators and a legislative inquiry have tied the speed it demands to ergonomic hazards and to warehouses described as uniquely dangerous, so the productivity gain and the worker-injury risk are coupled. Two things follow. The efficiency metrics — miles, fuel, throughput, units per hour — measure the optimization's success and are silent on its cost, which shows up in injury data, in surveillance the worker experiences, and in ethnographic research, not on the operations dashboard. And the workers being managed are, in effect, the served people of this domain: the person executing the AI's plan is also the person the optimization presses on, so the governable question is whether the system internalizes the human executing it — a pace that is feasible and safe, monitoring that is proportionate — or externalizes that cost as an injury or an autonomy loss the productivity number never sees. The Lab networks model only the deploying organization — its optimization or management model, the drivers and pickers who execute its plans, and its operations records; no worker-injury or safety outcome is computed on any diagram, and injury and surveillance findings are recorded external facts, never diagram-derived.

Use cases

What AI is doing here

Route & dispatch optimization

Predictive

Optimization that computes and dictates delivery or dispatch routes and monitors adherence — a documented operations-research efficiency success (miles and fuel saved) that is, in the same system, a workplace-surveillance tool, so the efficiency is enforced through monitoring and the worker's discretion is what it replaces.

Warehouse task assignment & pacing

Predictive

Algorithmic management that assigns and paces warehouse tasks (picking, stowing) — where a genuine human-robot productivity benefit is coupled to a documented injury-productivity trade-off, because the pace the algorithm sets is what regulators and inquiries have tied to ergonomic hazards.

Workforce pacing & adherence monitoring

Predictive

The monitoring and metrics layer that enforces an optimization on the frontline worker — miles, units-per-hour, adherence scores — where the efficiency dashboard measures the optimization's success and is silent on the cost (autonomy, surveillance, injury) that lands on the worker executing the plan.

Case files

What has gone wrong and right

Documented deployments, presented as model organizations calibrated to the evidence, with full citations.

System map

Who is in the system and what pushes on it

Who is in the system

  • Frontline workers. Caseworkers, screeners, eligibility staff — the operator network whose judgment the system augments or erodes.
  • Supervisors & QA. The institutional correction layer: overrides, second reads, quality review.
  • Agency leadership. Owns procurement, policy, and the authority map; answers for the system publicly.
  • Served people & families. Those the decisions land on. Deliberately outside the PAN dynamics — their outcomes are measured, never simulated.
  • Vendors. Build and update the systems; hold the information asymmetry procurement must govern.
  • Regulators & oversight bodies. Boards, auditors, data-protection officers, inspectorates — external correction capacity.

Dominant pressures

  • Reviewer bottleneck. One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
  • Austerity & recovery incentives. Cost-cutting and overpayment-recovery targets tilt the system toward denial and enforcement errors.
  • Vendor opacity. The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Data & policy drift. The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
  • Compliance over substance. Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

Governance

Questions leaders should be asking

  1. 1. The system that optimizes the route or the pick also dictates it to the worker and monitors adherence — so is the efficiency being enforced through surveillance the worker experiences, and is that monitoring governed as a cost, or treated as a free byproduct of the optimization?
  2. 2. When the algorithm sets the pace, the productivity gain and the worker-injury risk are coupled — so does the pace-setting internalize the safety of the person executing it, or externalize it as an injury the throughput metric never sees, the way regulators and inquiries have documented in warehouse work?
  3. 3. The efficiency metrics — miles, fuel, units per hour — measure the optimization's success and are silent on its cost — so is anyone measuring the cost that lands on the worker (autonomy, surveillance, injury), which shows up in injury data and worker experience rather than on the operations dashboard?
  4. 4. The workers being managed are in effect the served people of this domain — so is the deploying organization treating a route or a quota that is optimal on paper as feasible and humane for the person who has to execute it, or is 'optimal' being defined only on the metric the system was built to move?

For the actions behind these questions, see the Practice Library.

Seeing your organization in this domain? Mapping its actual pathways, pressures, and correction capacity is engagement work.

Work With 1023AI