LO
Bricklayer / blocklayer — 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
● 4 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 8 because mixers, hoists and laser levels were common before this chart begins, while every brick on site was laid by hand. It climbs as bricklaying robots move from factory tests to a few housing projects, where they lay long straight runs with a bricklayer alongside, and as more walling moves into factories as prefabricated panels. It stays low because the robots work beside a bricklayer, are limited in height and, by one builder's account, not yet as fast as hand work, and the best-known maker has fully impaired its machines, while setting out, detail and repair stay with bricklayers.
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-10-01
- Basis of the task judgements
- 1 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 5