IS WORK OVER?

Automation index

How much of a Copy editor’s job can AI already do?

A checker and a first pass come earlier. Keeping the author’s voice and not inserting a typo do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Copy editor

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Spelling, agreement and consistency.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Style, repetition and sentence rhythm.
Estimate

No public source provides a precise figure. This is our estimate.

16%48%+7.7
Queries to the author, grey areas and the house style.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Second proofs, PDF and last-minute typos.
Estimate

No public source provides a precise figure. This is our estimate.

18%22%+4
Deadlines with publisher, layout and translation.
Estimate

No public source provides a precise figure. This is our estimate.

16%18%+2.9
Judgement, not over-rewriting, and the typo that remains.
Estimate

No public source provides a precise figure. This is our estimate.

16%14%+2.2
Total100%31%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • copy-edit
  • spelling and punctuation
  • unify style
  • catch typos
  • house style
  • second proofs
  • author queries
  • avoid over-editing

Sources for this job· O*NET 27-3041.00· ESCO/ISCO 2641

Technical writer

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Structure, API docs and the tutorial.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Screenshots, versions and not leaving the old shot.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
The engineer who will not write, and extracting the how.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Legal review, i18n and the changelog.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Support, the tickets and what the doc misses.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it can be installed, and not documenting thin air.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%28%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • document APIs
  • product tutorials
  • screenshots
  • changelogs
  • extract knowledge
  • docs i18n
  • version review
  • support tickets

Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641

Analyse my job

Jobs with similar scores

  1. 29Admin assistant31%
  2. 30Biologist31%
  3. 31Cartographer31%
  4. 33Information specialist31%
  5. 34Epidemiologist31%
  6. 35Growth manager31%