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›Data analyst›2024-09-26
DeploymentCognitive automation2024-09-26

Grab says AI-drafted documentation, reviewed and accepted by the tables' owners, raised documentation of its most-queried tables by 70 points to about 90% before it launched an LLM data-discovery bot

Data analystoccupation page →
Event date / reported
2024-09-26
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
Owning the definitions the tools rely on
Maintaining the metric definitions, the documentation and the semantic layer that make natural-language querying produce correct answers.
New task✓ Evidence-backed
Where this applies
Grab engineers describing their own internal data tools. Only 20% of the most frequently queried tables had documentation; the team pre-populated AI-generated documentation for the most critical tables and notified data producers to review it, showing it with an 'AI-generated' tag until a producer accepted or edited it, and coverage for those tables rose by 70 percentage points to about 90% before the LLM discovery bot was launched. The bot runs on a vendor platform Grab uses; the figures are the company's own.
What this means
Before a data bot could answer questions, someone had to write down what the tables mean — and at one large company the machine drafted it while the tables' owners reviewed and signed off. Owning the definitions is the work that made the tool possible.
What it does not yet show
One company's own figures; they do not show who does this work elsewhere or how analysts' time changed.
What you can check
Open Grab's engineering post of 26 Sep 2024 and find "documentation coverage for P80 tables increased by 70 percentage points to ~90%".
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
Grab Engineering — "Enabling conversational data discovery with LLMs at Grab" (26 Sep 2024) · 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 Data analyst →All recent changes →How events become evidence →