AI exposure: Logistics Engineers

59.5% of this occupation's weighted task load is exposed, which puts Logistics Engineers at the 95th percentile of 923 occupations. The capability is largely there. Its average task scores 3.4 out of 4 on what a current system can produce, and the frictions that hold other jobs in place are comparatively weak here.

What holds the line here is context. Across this occupation's 30 tasks it averages 2.00 out of 3, the highest of the five friction dimensions. In plain terms, the work depends on knowledge the model cannot hold. Much of this job runs on things that were never written down: what this particular organisation does, what happened last week, what the person across the table actually meant. That context is the barrier, and it erodes as systems are given more access.

The most exposed thing this job does is Analyze or interpret logistics data involving customer service, forecasting, procurement,..., at 80.0%. The least is Direct the work of logistics analysts, at 13.3%. A gap of 66.7% between two parts of the same job is the reason this index publishes at task level. An occupation-wide number would have hidden both.

Within business and financial operations occupations, this one is more exposed than most. The median across the 48 roles in the group is 47.1%, and only 7 of them score higher than this. Occupational families are not uniform, and the spread inside them is often wider than the gap between them.

What would move this score. Of 30 tasks, 29 are currently banded exposed, 0 assisted and 1 untouched. For that distribution to shift materially would take cheaper ways to verify output, since the cost of checking is currently doing more to hold this work in place than the cost of producing it. The score is re-computed every quarter against a fresh capability reference, and the change is published rather than quietly applied.