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.

AskOccupationsMajorsBusinessFoundersChangesNotesMethodAboutRole diagnosisPrivacyTerms
© 2026 VOLO
Occupations
All occupations
AI / software
Translator / InterpreterBank tellerCopywriterContent moderatorCustomer service representativeAdministrative assistantSoftware tester / QA engineerGraphic designerParalegalVideo editorAccountant / BookkeeperMarketing specialistFrontend developerData analystInsurance claims handlerTechnical writer / documentation engineerJunior software developerHR / recruiterLoan officer / credit officerFinancial analystProcurement / supply chain specialistJournalistSales / account managerReal estate agentIT support specialist / helpdeskAuditorManagement consultantBackend developerAI researcherProduct / UX designerBusiness systems ownerE-commerce operations specialistRadiologistData engineerLawyerMedical assistant / clinic assistantMachine learning engineerExperienced software engineerDevOps / platform / SRE engineerProduct managerPharmacistPartnerships / channel managerSecurity analyst (SOC)Compliance officerArchitectFirst-line manager / team supervisorCounsellor / therapistRetail salesperson / shop assistantSecurity guardSchool teacherGeneral practitioner / primary care doctorWaiter / restaurant serverAuto mechanic / vehicle technicianPhysiotherapist / rehabilitation therapistConstruction workerRegistered nurseCare worker / nursing assistantAI implementation lead
RPA / self-service
Government service clerkOperations coordinatorMetro train driverReceptionist / front desk
Robotics
Retail cashier / shop assistantContainer port workerWarehouse workerAssembly line workerMedical laboratory technicianChef / cookCleaner / janitorElectrician
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
Guides
Ask VOLOFor businessFor foundersRecent changesNotesRole diagnosisMethod & evidenceAboutFollow an occupationSearch
You are reading as:I have a jobI am studyingI run a companyI am building something
On this pageRunning the analyserKnowing a result is wrongHandling the specimenMaking the critical call
Occupations›Medical laboratory technician›Tasks, one by one

Medical laboratory technician — tasks, one by one

The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.

Tasks
4
With evidence
2/4
Assessed
2026-09-14
Automating×1Still human-led×2New task×1

Every task on this page#

Running the analyser

Automating✓ Evidence-backed

Loading, calibrating, and moving hundreds of samples through machines that do the measurement themselves.

RoboticsRPA / self-service
Why

This occupation is the most completely automated one on the site and has been since the 1970s: automated analysers replaced manual titration, and track systems later replaced the walking between them. The measurement itself has not been done by hand in most laboratories for a generation, and the current wave adds scheduling and image reading rather than starting anything.

What this does NOT mean

Sixty years of this and the occupation is still here, which makes it the site's clearest counter-example to the idea that automating the core task removes the job. What it removed was the manual method, the entry ladder that taught it and a large share of the headcount per test — the job that remained is supervision of machines, which is a different job at the same title.

Knowing a result is wrong

Still human-led✓ Evidence-backed

Spotting the value that is impossible for this patient, the drift that says the instrument needs attention, the specimen that was mislabelled upstream.

AI / software
Why

Delta checks and rule engines catch the values that violate a stated rule, and they have for decades. What they cannot catch is the plausible wrong answer — a result that is internally consistent and belongs to somebody else — and that is caught by someone who knows what this ward, this analyser and this time of day usually produce.

What this does NOT mean

This task being human does not mean it is staffed: laboratories are sized on throughput, and the person who catches the plausible wrong answer produces no measurable output when they succeed. Where lab staffing has been cut, this is the capacity that went, and the consequence appears as a misdiagnosis nobody traces back.

Handling the specimen

New task≈ Platform inference

Receiving, spinning, aliquoting, and dealing with the sample that arrived clotted, short, unlabelled or at the wrong temperature.

RoboticsRPA / self-service
Why

Track automation handles the compliant specimen completely in high-volume laboratories and is spreading down to smaller ones as the price falls. The non-compliant specimen is the exception the track kicks out, and that exception is a physical judgement about whether the sample can still be used or must be recollected.

What this does NOT mean

Deciding a specimen must be recollected is a decision with a cost that lands on somebody else — a patient stuck again, a delayed result — which is why it stays with a person. But the volume of exceptions falls as the pre-analytical process tightens, so this task shrinks for reasons upstream of the laboratory.

Making the critical call

Still human-led≈ Platform inference

Deciding a result cannot wait, finding the clinician responsible for this patient right now, and making sure they heard it.

AI / software
Why

Automated alerting exists and is standard; what is not automated is the closing of the loop, because the requirement is that a person confirms receipt and understanding. Where this has been left to a system, the failure mode is a notification landing in a queue nobody was watching, which is the one outcome the protocol exists to prevent.

What this does NOT mean

This is protected by protocol rather than by difficulty, and protocols are rewritten. A laboratory under staffing pressure will move to automated notification with acknowledgement tracking, which satisfies the audit and moves the risk to whoever is meant to be reading the queue.

← Back to Medical laboratory technician