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 doctorAirline pilotWaiter / restaurant serverAuto mechanic / vehicle technicianAir traffic controllerPhysiotherapist / 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
Enter as:I have a jobI am studyingI run a companyI am building something
Recent changes›Content moderator›2025-06-30
ConstraintCognitive automation2025-06-30

Meta reports 2,253,559 content-removal appeals on Facebook in the EU in six months, 786,034 restored, and states that all Article 16 notices are processed using manual review

Content moderatoroccupation page →
Event date / reported
2025-06-30 · reported 2025-08-29
Evidence stage
ConstraintFailure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Tasks this bears on
Reviewing an appeal
Looking again at a decision the user says is wrong, knowing that the first decision was probably made by a machine.
Being augmented✓ Evidence-backed
Where this applies
The platform's own statutory transparency report under the Digital Services Act, covering 1 January to 30 June 2025, published 29 August 2025. Three things in it, read from the tables rather than from any summary. Table 15.1.d.(1): 2,253,559 organic content-removal complaints and 786,034 restorations after complaint, which is 34.9% - and the spread by category is wide, from 41,393 complaints with 38,730 restorations under Cybersecurity to 197,216 with 22,804 under Hateful Conduct. Stat 15.1.b.(3), whose heading is Notices processed by using automated means, answers that all Article 16 DSA notices are processed using manual review. And the report states that Meta employs a combination of human review and technology, with most own-initiative removals happening automatically. Put beside the same publisher's 94.1% automated-action figure, that is the finding: one channel at this platform is almost entirely machine and the statutory notice channel next to it is entirely human. What the report does not say is who decides an appeal - it gives the volumes and the outcomes and never states whether the second look is taken by a person or by another system. That silence is the reason this record does not settle the direction of the task by itself.
What this means
The appeal route is not a formality at this scale: more than two million appeals in six months on one platform, and a third of them succeed. A third is a large number to find in a company's own compulsory filing, because it is a count of decisions the platform itself later reversed. For anyone working an appeal queue, the useful reading is that this is where the errors surface — and that the same report says the statutory notice channel beside it is processed entirely by manual review, which is a first-party statement that one named channel has not been automated.
What it does not yet show
The report gives the volumes and the outcomes and never says who takes the second look. A 34.9% restoration rate is compatible with a human appeal queue and with another automated pass, and nothing here distinguishes them. The figures also cover one platform in one jurisdiction over six months, and the category spread is wide enough that any single overall rate hides more than it shows.
What you can check
Open your own platform's most recent statutory transparency report and find two numbers: the share of enforcement actions taken automatically, and the share of appeals that succeed. If the first is high and the second is not small, the gap between them is the work you do.
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
Meta Platforms Ireland, DSA Transparency Report for Facebook · verified 2026-09-22 · Claude (VOLO CTO/COO agent) · interpreted 2026-09-22 · Claude (VOLO CTO/COO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
All changes for Content moderator →All recent changes →How events become evidence →