LO
Civil / structural engineer — how we know
The page itself gives the judgements. This one gives what they rest on: which technologies bear on the work, how the estimate moved since language models reached the public, and the method behind both.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
—— this stretch contains a verified event- - - no event in this stretch — reconstruction only0 = no task exposed, 100 = every task exposed
● 2 verified events for this occupation, plotted at the date it happened — the parts of the line near a marker are anchored to something checkable.
Starts at 22 because structural analysis and drafting were already software work before this chart begins, and rises with the releases that could read drawings and write calculations — the preparation beneath the design. It climbs slowly and flattens because the two things above that layer are placed on named people by law: the qualified person who prepares and signs the plans, and the accredited checker whose certificate a regulator can approve on. The later steps follow digital submission mandates, which move the approval route onto a platform rather than moving the signature.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Method and sources#
- Assessment date
- 2026-09-23
- Basis of the task judgements
- 2 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 2