VOLOVLOAutomation risk & transition, task by task
AskOccupationsMajorsBusinessFoundersChangesNotesMethod
Search occupations, majors…
EN
  • English
  • 简体中文
  • 日本語
  • Español
  • Português
  • Français
VLO
VOLO

Understanding how automation changes work — task by task, with the evidence shown and the uncertainty admitted.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodWill AI replace my job?AboutRole diagnosisOpen dataOntologyVOLO ProPrivacyTerms
© 2026 VOLO
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisFirst AI experimentVOLO ProMethod & evidenceAboutFollow an occupationSearch
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterContent moderatorCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerTax preparer / tax agentVoice actorMedical coderData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerInsurance underwriterHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistActuaryRadiologistData engineerProject managerLawyerMedical assistant / clinic assistantQuantity surveyorMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Financial adviser / financial plannerCompliance officerLibrarianArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantCivil / structural engineerSecurity guardBus driverInsurance agentSchool teacherGeneral practitioner / primary care doctorAirline pilotWaiter / restaurant serverRadiographer / radiologic technologistAuto mechanic / vehicle technicianPolice officerSonographerAir traffic controllerVeterinarianPhysiotherapist / rehabilitation therapistDentistConstruction workerSocial workerRegistered nurseCare worker / nursing assistantPlumberAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorMetro train driverReceptionist / front desk
Robotics
Retail cashier / shop assistantContainer port workerWarehouse workerAssembly line workerMedical laboratory technicianWelderChef / cookCleaner / janitorFarmerFirefighterCabin crewElectrician
Autonomous driving
Ride-hail / taxi driverTruck driverDelivery rider / courier
Majors
All majorsEnglish / Foreign languagesComputer scienceAccountingPsychologyJournalism / CommunicationFinanceLawVisual communication designMarketingNursingBusiness administrationEducation and teacher trainingArchitecturePublic administrationMedicineHospitality and tourism managementEconomicsInformation systems
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Experienced software engineer›2026-03-20
ConstraintCognitive automation2026-03-20

A UK government department's engineering standard says AI cannot replace human responsibility for designs, and requires a person to approve every AI-assisted output before production

Experienced software engineeroccupation page →
Event date / reported
2026-03-20
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Designing for how it fails
Choosing a structure, and choosing which failure modes to accept — knowing what happens at 3am when a dependency is down and half the requests are already in flight.
Still human-led✓ Evidence-backed
Where this applies
An engineering standard binding the Home Office's software teams. It says teams will retain full accountability for all AI-assisted code and outputs because AI tools cannot replace human judgement, understanding, ownership or responsibility for decisions, designs or changes made to systems, that AI-assisted outputs must be reviewed and approved by a human before reaching production, and that teams must be able to assert the security and maintainability of what they run. The firm 'must' applies to review; the sentence on designs states where accountability sits. It is one department's published standard, not a measure of practice elsewhere.
What this means
At least one engineering organisation has written down where design responsibility sits once AI is in use: with the team, not the tool. The bet about which failure the organisation can survive stays with people who answer for it.
What it does not yet show
One department's standard; it does not show how architecture decisions are actually made there or elsewhere.
What you can check
Open the Home Office standard SEGAS-00020 'Use AI' and find "AI tools cannot replace human judgement, understanding, ownership, or responsibility for decisions, designs, or changes made to systems".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
UK Home Office — Engineering Guidance and Standards, SEGAS-00020 "Use AI" (last updated 20 March 2026) · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Experienced software engineer →All recent changes →How events become evidence →
A UK government… — impact on experienced software engineers | VOLO