IS WORK OVER?

Automation index

How much of a Civil registry officer’s job can AI already do?

An entry comes earlier. The name and the death being right, without losing the book, do not.

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

Task comparison

Civil registry officer

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
Entry, the book and the record.
Estimate

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

18%48%+8.6
Birth, the deadline and the one who is late.
Estimate

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

16%40%+6.4
Marriage, the impediment and not jumping.
Estimate

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

16%22%+3.5
Death, the family and not mixing the dead.
Estimate

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

16%28%+4.5
The registrar judge and not losing the volume.
Estimate

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

18%14%+2.5
That it is right, and not losing the book.
Estimate

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

16%12%+1.9
Total100%27%

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

Skills and activities

  • entries
  • registry books
  • births
  • marriages
  • deaths
  • records
  • registry deadlines
  • volumes

Sources for this job· O*NET 43-4031.00· ESCO/ISCO 3359

Backend developer

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
Endpoint, the contract and the test.
Estimate

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

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

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

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

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

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

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

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

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

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

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

16%12%+1.9
Total100%27%

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

Skills and activities

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 200Clinical research associate27%
  2. 201Neuropsychologist27%
  3. 202Office manager27%
  4. 204Talent scout27%
  5. 205University careers adviser27%
  6. 206Product owner27%