LO
Worker adoptionCognitive automation2026-04-01
Census BTOS supplement: writing is the leading generative-AI task reported inside US firms, and 65% of firms limit AI use to three tasks or fewer
Technical writer / documentation engineeroccupation page →
Event date / reported
2026-04-01
Evidence stage
Worker adoptionMeasured, large-scale use of a tool for real work, where the decision to use it was the worker's rather than an employer's. It is more than a capability record — the work is real, not a demo — and less than a deployment record, because no employer put it into production, required it, or built a process around it. Weighted `cautious`: `automating` means the machine can do the task AND there are adoption signs, and this is an adoption sign — but usage can be experimental, and much of the measurement comes from a party with a stake, so one record is never enough and two independent ones are. Note who is counting. Vendor telemetry sees this directly and sells the tool, so such a record names that stake in its scope; a statistics agency asking firms whether their workers use AI in tasks sees the same channel with no stake at all, and that is the better source where it exists.
Tasks this bears on
Drafting the reference
The API reference, the parameter table, the release note, the changelog entry — documentation whose content is determined by the code.
Automating≈ Platform inference
Deciding what does not get written
Choosing which twenty per cent of the surface area gets documented properly, and refusing the rest.
Still human-led≈ Platform inference
Where this applies
Nationally representative, reference period November 2025 to January 2026. This is the worker-task layer of the same supplement rather than its firm-adoption layer: 23% of firms (41% employment-weighted) report workers using AI in work-related tasks, and among the tasks reported, writing, document analysis and information search lead. It is a count of firms reporting a task, not a measure of how much writing is done that way, and it does not distinguish technical documentation from any other writing — nobody asked what was written. Its value here is what it is not: unlike vendor telemetry, this is a statistics agency counting the same channel with no stake in the answer, which makes it the better source for worker adoption where it exists.
What this means
A statistics agency asking firms what their workers actually do with AI reports writing at the top of the list, and it reports it with no stake in the answer. That matters more than the ranking itself: the same channel is visible in vendor telemetry, and this is the version of it collected by a party that is not selling anything.
What it does not yet show
It counts firms reporting a task, not how much of any task is done that way, and it does not distinguish technical documentation from email, marketing copy or anything else written at work — nobody asked what was written. The 65% limiting AI to three tasks or fewer also cuts against the broadest readings: this is narrow use inside most firms rather than general adoption.
What you can check
List the document types your team publishes and mark which have a machine-readable source of truth. Those are the ones this finding is about; the rest are not, and the difference is your job.
Does it change the assessment?
No. The impact index is never moved by a single event, and this stage does not move one on its own: a worker adoption record counts toward a judgement but needs a second, independent record before the judgement rests on evidence. This one is counted; on its own it changed nothing.
Source
U.S. Census Bureau, Center for Economic Studies (CES-WP-26-25), worker-task findings · verified 2026-09-13 · Claude (VOLO agent) — the 23%/41% worker-task figures and the leading-task list read from the paper's own abstract and body, the same PDF already used for two other records on this site · interpreted 2026-09-13 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.