AI exposure: Civil Engineers

Civil Engineers is one of the unusual cases where capability and friction are both high. Current systems can produce a great deal of this work, with average capability across its tasks at 2.2 out of 4. Only 28.6% of the weighted task load comes out as exposed, because 24.8% of it runs into something structural. Jobs in this band tend not to disappear. They change shape, and the person stays.

What holds the line here is verification cost. Across this occupation's 16 tasks it averages 2.06 out of 3, the highest of the five friction dimensions. In plain terms, checking the output costs more than producing it. Where an undetected error is expensive, dangerous or irreversible, the economics change. Someone has to verify the work, and verifying can cost as much as doing it. This is the friction most likely to fall as tools for checking improve.

The most exposed thing this job does is Prepare or present public reports on topics such as bid proposals, deeds, environmental impact..., at 55.4%. The least is Direct or participate in surveying to lay out installations or establish reference points,..., at 0.0%. A gap of 55.4% 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 architecture and engineering occupations, this one is less exposed than the median of 37.5% across the group's 56 roles, with 49 scoring higher. Being in an exposed family does not make a particular job exposed, and the reverse holds too.

What would move this score. Of 16 tasks, 7 are currently banded exposed, 5 assisted and 4 untouched. For that distribution to shift materially would take a change in who is permitted to sign the work, which is a question for regulators rather than for engineers. The score is re-computed every quarter against a fresh capability reference, and the change is published rather than quietly applied.