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›Technical writer / documentation engineer›2026-08-03
ConstraintCognitive automation2026-08-03

FDA guidance says instructions for use are judged by how representative users perform with the device, and that fixing a use problem by rewriting the instructions needs new test data

Technical writer / documentation engineeroccupation page →
Event date / reported
2026-08-03
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Actually using the thing you are documenting
Following your own instructions on a clean machine and finding the step that was obvious to the engineer and impossible for everyone else.
Still human-led✓ Evidence-backed
Where this applies
FDA's guidance for medical device makers, marked as containing nonbinding recommendations. It covers labelling including instructions for use, user manuals, package inserts and quick-start guides, and says human factors validation testing can assess the adequacy of the instructions for use, but only in the context of use of the device; that the most important consideration for test participants is that they represent the population of intended users; and that if testing shows use errors on critical tasks, stating that the risk was mitigated by modifying the instructions or other labelling is not acceptable without additional test data showing the change worked. It applies to medical devices only and does not say who writes the instructions.
What this means
For instructions where mistakes hurt people, the regulator does not accept a well-written manual as proof: the manual is judged by real users using the device, and a rewrite has to be tested again. Using the thing — through people who do not already know it — is built into how instructions are accepted.
What it does not yet show
Nonbinding guidance for medical devices only; it does not show how software documentation is tested, or that writers themselves run the tests.
What you can check
Open FDA's guidance "Applying Human Factors and Usability Engineering to Medical Devices" and find "is not acceptable unless you provide additional test data".
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
US Food and Drug Administration — Applying Human Factors and Usability Engineering to Medical Devices, guidance for industry and FDA staff (issued 3 August 2026; originally issued 3 February 2016) · verified 2026-09-28 · Claude (VOLO agent) · interpreted 2026-09-28 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Technical writer / documentation engineer →All recent changes →How events become evidence →
FDA guidance says instructions… — impact on technical writers | VOLO