In brief

The checker can help you choose a task to investigate; it cannot decide whether you should stay or leave. Look for observable changes at work, then weigh whether an authorized, measurable redesign trial is feasible and whether waiting fits your constraints. Compare realistic alternatives in parallel if evidence is weak or delay is costly.

Can the checker decide whether you should leave?

No. Use the checker to choose which task to inspect first, then decide whether redesign is worth pursuing from evidence about your work and constraints. For a flagged task, ask whether the workflow changed, whether you can safely test a different division of work, and whether a realistic alternative is accessible if the role does not improve. The result can focus attention; it cannot weigh your income floor, location, health, caregiving duties, training time, or available openings. A strong signal is an early warning: inspect a recurring task, but do not resign on the score alone. Record what changed and when to distinguish a one-off demonstration from routine work. If a small, authorized test is feasible and the role remains workable, use it to gather local evidence while keeping alternatives in view. If no test is possible, include that constraint in your decision; it does not mean the role is safe or doomed.

What does a task change-pressure signal tell you?

A task change-pressure signal is a conditional estimate: given the tasks named and the assessment's assumptions about current AI capabilities, how susceptible might that work be to assistance or automation? The International Labour Organization's brief, “Workers’ exposure to AI: What indicators tell us – and what they don’t,” reviews indicators built from task descriptions and explains why they identify possible transformation rather than establish what a particular employer will do. The checker presents task-level signals; its result is a prompt for investigation, not a validated forecast of your job or a personal displacement probability.

Keep five links in the chain separate. Capability asks whether a system can perform or support some part of a task under specified conditions. Adoption asks whether an employer provides, permits, and relies on a tool in that work. Workflow redesign asks whether duties, handoffs, review, or accountability actually shift. Demand concerns how much work employers or customers need, including any new or expanded tasks. Displacement is a reduction or loss of work for people. A score near the start of that chain cannot settle what happens at its end.

That gap is practical. A task may be technically susceptible while a workplace lacks approved software, usable data, integration, or a way to correct errors. Even where a tool is used, people may need to interpret unusual cases, check outputs, explain decisions, or accept responsibility. This can preserve work, redistribute it, or add review time. Conversely, reliable, economical use may change staffing or assignments. The task signal cannot tell you which mechanism applies, how quickly, or who benefits. Consequences also depend on error costs, volume, exceptions, and review cost: if checking takes nearly as long as doing the task, capability may yield little usable capacity; frequent, standardized work that is easy to verify may be more workable to redesign. A task estimate does not observe these process economics or establish whether saved time reduces backlogs, raises output, improves service, creates duties, or changes headcount.

Read a high result as a prioritization cue: identify the recurring work it refers to, then look for permission, repeated use, changed assignment patterns, and new quality or review expectations in your setting. Read a low result just as narrowly; it does not cover every task, future capability, or employer choice. These interpretations do not claim that the checker has been validated to predict outcomes. They keep its useful role modest: it can help you decide where to gather direct evidence before comparing a redesign with other options.

Pay attention before local outcomes are settled. Repeated digital work with stable inputs and outputs may be susceptible before an employer changes the process; waiting for a formal reorganization could leave less time to learn. Use the signal to name a task, ask what would have to change for a tool to take part, and watch for evidence that those conditions exist. Whether that evidence justifies staying, redesigning, or preparing to move belongs to the later decision, informed by observed work and personal constraints.

Sources: Workers’ exposure to AI: What indicators tell us – and what they don’t

Why can one occupation label conceal different exposure?

Workers with the same occupational title can face different task change because each workplace allocates the broad task bundle differently. One analyst may assemble routine reports; another may resolve exceptions, coordinate with clients, and defend recommendations. Volume, input quality, discretion, and review requirements can differ even for the same duty. An occupation-level result describes a classification pattern, not every worker's schedule. Translate it into an inventory of your recurring tasks: what you produce, how often, from which inputs, who relies on it, and what judgment or checking follows. This is an interpretation step, not a new score.

The International Labour Organization's *Generative AI and jobs: A 2025 update* reports that one in four workers globally is in an occupation with some generative-AI exposure. Its assessment combines task-level information, expert input, and AI predictions across nearly 30,000 tasks, and organizes results into four exposure gradients. The unit matters: this is an estimate of occupational coverage around the world. It does not mean a quarter of each worker's hours can be automated, that all workers in a covered occupation do the same work, or that one in four people will lose a job. The ILO's assessment says transformation is more likely than redundancy because human input remains relevant across many exposed occupations. That broad conclusion can orient attention, but it cannot tell an individual which duty is changing first or whether their employer will adopt a tool.

The ILO–NASK Index methodology adds a different kind of detail: its occupational estimates are built from sampled tasks rather than treating a job title as an indivisible unit. NASK says its method draws on a representative sample of tasks from Polish occupational classifications and a large worker survey, compares this material with expert assessments and Delphi-style discussions, and applies AI-assisted estimation to task descriptions in ISCO-08. This construction can make the path from a role label to a task-level signal more visible. A worker can ask which tasks underlie a role's result and whether those tasks resemble their own assignments. It also shows why two indices may differ: their task lists, respondents, expert judgments, classification systems, and scoring procedures need not be identical. A difference between results can reflect these design choices, not a sudden change in the work itself.

NASK's inputs also limit transfer. Its survey and classification context is partly rooted in Polish occupational categories and cannot establish how work is allocated in another country, firm, or team. A granular index still does not observe your hours, exception rate, quality burden, manager's plans, or review economics. Modeled scores can identify what to inspect, while local task allocation and employer choices need separate evidence. If a broad signal feels mismatched, compare its implied tasks with your recurring work, noting which duties dominate and which carry responsibility or unusual cases. Treat a mismatch as a question to investigate, not proof that you or the assessment is wrong.

Sources: Generative AI and jobs: A 2025 update; ILO–NASK Index methodology

What evidence shows that work has changed in practice?

A worker can distinguish capability or casual use from an actual workflow change by looking for a sequence of increasingly local evidence: the tool is authorized for the relevant work; it is used repeatedly on that work; assignments or handoffs change because of that use; and review, ownership, or accountability move with the task. Treat this as a decision aid, not a validated scale. A tool demonstration establishes capability under demonstration conditions. A colleague trying a public chatbot establishes neither permission nor a recurring workplace process. Evidence becomes more relevant to your decision as it connects an approved tool to ordinary work and then to changed expectations about who produces, checks, corrects, and stands behind the result.

Anthropic's *Anthropic Economic Index report: Uneven geographic and enterprise AI adoption* illustrates both the value and limit of observed-use data. The September 2025 report classifies anonymized Claude conversations by task and interaction pattern, including a one-million-conversation analysis of Claude.ai use. That material can show that people use one product for varied tasks and that interactions can be classified by patterns such as automation and augmentation. It is a view into activity on that product, not a representative survey of employers or workers. A conversation record does not establish that a user's employer permitted the tool, that the task was part of paid work, that use recurred in production, or that output met workplace quality requirements. It also cannot show that a staffing decision followed. The dataset is useful for describing observed interactions; it cannot substitute for evidence about a specific team's operating process.

Apply the sequence to your own setting without turning it into a numerical rating. First ask whether the relevant tool and data are authorized for the task; an available account or informal use is not workplace approval. Next look for recurrence: does the same task return to the tool as part of ordinary work, or was the use a one-off experiment? Then identify workflow consequences. Are fewer items assigned to a person, are more cases handled, has a handoff disappeared, or has the worker's role shifted toward exceptions and review? Finally locate responsibility: who verifies errors, makes the consequential judgment, explains the output, and is answerable when it fails? These observations are more informative than counting mentions of AI because they connect tool use to changed work arrangements.

The sequence helps interpret missing evidence. Approved, repeated use with stable assignments, checks, and accountability suggests assistance without evidence that the role was redesigned. Changed ownership or review is a concrete workflow shift, even if title and headcount remain unchanged. No visible rollout does not prove change is absent: informal use, pilots, or unannounced decisions may be outside one worker's view. Product usage data may precede broader adoption, while company announcements may overstate routine use. Record what you observe and what remains unknown. The question is whether permitted, recurring use is changing the tasks and responsibilities your role depends on.

Sources: Anthropic Economic Index report: Uneven geographic and enterprise AI adoption

What can AI redesign improve, and what can it make harder?

AI redesign can reduce repetitive or physically demanding work and give people more room for judgment, but it can also raise skill requirements, intensify the pace, and move effort into checking. Which outcome appears depends on how a workplace reallocates tasks, review, training, and the time saved. The OECD’s *The impact of AI on the workplace: Evidence from OECD case studies of AI implementation* examined nearly 100 qualitative implementations in manufacturing and finance across eight countries. In those selected cases, reorganization appeared more common than displacement. Reported mechanisms included less tedious work, greater engagement, and improved physical safety; the same case research also identified higher skill requirements and greater reported work intensity. These cases help explain how redesign can change the character of work. They do not establish how often those gains occur across all workplaces or predict what an employer will do.

The cases are useful because they make the distribution of work visible. If a system takes over a repetitive step, the remaining job may involve handling exceptions, coordinating people, interpreting results, or intervening when equipment behaves unexpectedly. Removing one burden can therefore make a job more varied or safer while making another part more demanding. A claimed productivity gain could also mean the same staff handle more cases, meet tighter deadlines, or take responsibility for a larger volume of output. The OECD case study supports the existence of these different mechanisms in its studied settings; it does not say they occur together everywhere. For a worker considering redesign, the key question is what work replaces the task that shrinks, including who owns exceptions and whether the new duties fit available skills and working conditions.

A separate source measures perceptions rather than documenting implementation mechanisms. The OECD’s *The impact of AI on the workplace: Main findings from the OECD AI surveys of employers and workers* reports generally positive worker and employer assessments of performance and working conditions in surveyed manufacturing and finance settings across seven countries. Respondents also expressed concerns about job loss. The paper reports that training and worker consultation were associated with better reported worker outcomes. These are survey reports and associations: they describe what respondents said and how responses related to training or consultation, not proof that AI caused improved conditions or that consultation will produce the same result in another workplace. The survey findings therefore add both favorable perceptions and concern, but should not be blended with the selected qualitative cases as if one design confirmed the other.

Together, the sources suggest questions for a local redesign discussion. Which task will shrink, and what replaces it? Who receives freed time: the worker, a backlog, a customer, or the employer through higher throughput? Who checks outputs, handles exceptions, and carries accountability, and is review time counted in staffing and deadlines? What training precedes changed duties, and can workers raise quality or safety concerns? If responsibilities increase, do decision rights and recognition change? How will quality be judged, and can workers pause work for corrections? These questions test whether reported gains translate locally. Positive case findings and survey perceptions do not cancel job-loss concerns, intensified work, or possible role cuts; local allocation of benefits and burdens remains decisive.

Sources: The impact of AI on the workplace: Evidence from OECD case studies of AI implementation; The impact of AI on the workplace: Main findings from the OECD AI surveys of employers and workers

What can demand projections tell you before choosing a path?

National employment projections can provide a broad demand context for comparing a current occupation with an adjacent one, but they cannot tell you whether a particular worker can enter that path or find a suitable opening nearby. The U.S. Bureau of Labor Statistics’ *Employment Projections — 2024–2034* projects national employment using historical relationships among productivity, technology, and occupations. BLS says those relationships may not hold if technology changes rapidly and that the effect of AI ten years ahead cannot be precisely predicted. It also notes that technology can change the tasks within an occupation without changing the occupation’s overall demand. A task being redesigned, then, does not by itself show whether total employment will rise or fall; aggregate growth does not show which tasks or workers will benefit.

Treat BLS figures as a scenario from national historical patterns, not a forecast of local vacancies or an AI exposure measure. A ten-year national estimate differs from current hiring requirements or near-term changes on your team. A role can have a favorable national outlook but few local entry openings, while a slower-growing role may still have employers hiring for a specific capability. These are possible differences in scale and timing, not findings about a local market. Outside the United States, consult the relevant national statistical agency's occupational projections with their own scope and assumptions.

To make an adjacent option concrete, inspect current postings where you could realistically work, including remote roles when your circumstances and the employer's terms allow. Compare several for recurring requirements, essential versus preferred skills, credentials or experience, and whether level and compensation meet your constraints. Record date and source: postings are snapshots and may be duplicated, aspirational, or withdrawn. This personal exercise is not a representative market study; a few listings cannot establish job counts or whether you would receive an offer. They can reveal gaps, such as a commonly requested tool, domain experience, or license, to investigate before committing time and money to retraining.

Projection evidence is worth including because a move with no plausible demand pathway can consume scarce preparation time. But national projections should sit alongside, not substitute for, checks of local requirements, access, and the worker’s constraints. Ask whether the candidate role’s repeated requirements build on experience you already have, what proof or credential is missing, and how long and costly it would be to close that gap. Compare those demands with the present role’s actual redesign prospects and the income, location, health, and family conditions you must preserve. If the projection and local postings point in different directions, investigate the difference in geography, time horizon, and job level before deciding what it means. Neither an aggregate forecast nor a small set of postings is a personal verdict; each helps frame a next question that more local evidence can answer.

Sources: Employment Projections — 2024–2034

When is a bounded redesign trial credible?

A bounded redesign trial is credible when it tests one recurring bundle of work under authorized conditions, preserves a meaningful comparison with the current process, and assigns responsibility for quality and exceptions. It should have a named scope, a baseline, protected time for learning and review, and a decision date set before results are known. This is an editorial decision procedure for structuring a workplace conversation, not a validated assessment and not proof that a trial will predict long-term staffing effects.

Start by choosing a bundle that recurs often enough to observe but is narrow enough to describe: inputs, usual output, handoffs, and common exceptions. Avoid proposing a vague experiment such as “use AI more.” Specify the step the tool may assist with and the step that remains human-owned. Then confirm that the tool, data, and proposed use are permitted by workplace policy and that the person sponsoring the trial has authority to approve them. If permission is absent or unclear, do not move real work or sensitive information into the tool; ask for an approved route or test with permitted material. A worker who cannot authorize a test can still request clarification or document ordinary work, but should not be expected to create a trial alone.

Before changing the process, capture a baseline over a defined set of comparable cases or a practical period. Record the current completion time and volume alongside quality measures that matter for the output: errors, rework, missed exceptions, or downstream corrections. Note variation in case difficulty so that an unusually easy batch does not make the redesigned process appear better. The baseline need not be elaborate to be useful; it needs consistent definitions and enough context to compare like with like. Agree in advance what counts as acceptable quality and which failures require stopping or escalation.

Write down the operating roles before the first case: who provides inputs, who uses the tool, who checks the result, who handles exceptions, and who remains accountable for the final work. Allocate time for onboarding, verification, correction, and discussion rather than treating those tasks as free. At the preset review date, compare pace, quality, corrections, and total workload, including review time and any new duties. A faster first draft is not a gain if checking absorbs the saved time or errors shift work to colleagues. Decide whether to stop, adjust the scope or safeguards, or continue under the same review conditions; record why, and do not generalize from one bundle to every task in a role.

Illustration, not evidence: a team that prepares a recurring internal meeting summary might test a permitted tool on routine notes while a named employee checks names, decisions, and action owners. The comparison would include preparation and review time, corrections, omissions, and whether the summary remains usable—not just how quickly a draft appears. If the team lacks permission, a reliable baseline, or capacity to review, the test is not yet informative. That limitation describes access to evidence; it does not show that the task or role is either secure or in danger.

Which move should you compare before leaving?

Before leaving, compare three paths against the same constraints: redesign the current role, move to an adjacent role, and make a larger change. The useful choice is the path whose work, entry requirements, and timing fit both the evidence you can gather and the life you must support. This comparison is a planning framework, not a forecast of hiring or income. Retained experience can reduce what you need to learn, but it does not guarantee that an employer will recognize it or that a transition will succeed.

For each path, describe the tasks you would own and the experience that carries over. In a redesign, ask whether the role can shift toward work that still needs your domain judgment, coordination, exception handling, or accountability, and whether the employer will provide the permission, training, time, and decision authority that work requires. For an adjacent move, identify which parts of your knowledge transfer and which new proof is needed: a portfolio, credential, license, supervised practice, or demonstrated tool use. For a larger change, list the foundations and qualifications required from the beginning. A path that sounds future-facing is not actionable until its entry conditions and first credible proof are clear.

Compare demand at the scale where you could act. Use the national outlook as broad context and check current postings or direct hiring requirements where you could work. Identify repeated requirements and distinguish must-haves from preferences. A few listings are clues, not a job count or evidence you would be hired. Consider level: a growing field may have few accessible entry roles for someone without requested experience. If local evidence is thin, gather more information or keep options open rather than assuming demand.

Put the practical costs beside the opportunity: prerequisites, preparation time, course or credential cost, lost or reduced income during training, location and commuting limits, health needs, and care or family obligations. Set an income floor and a latest realistic transition date. Ask which option can be tested while employed, which requires a substantial commitment, and what would make that commitment unaffordable. An adjacent move may preserve more domain experience and shorten the learning gap, yet still require a credential or evidence of capability. A larger change may be necessary if the present role or its conditions are already untenable; preserving experience should not become a reason to remain in harmful or unsustainable circumstances.

Illustration, not evidence: someone whose work combines routine client reports with knowledge of a regulated service might compare redesigning report preparation, moving to a neighboring operations role, and retraining for a different field. The comparison would ask, for each route, which tasks remain theirs, which regulations or tools they must learn, what local openings repeatedly require, and how long they can study without breaching their income floor. The example does not imply that any route is available or likely to pay a particular amount. It shows how the same constraint set makes tradeoffs visible.

Parallel exploration can preserve choice: while employed, a worker might seek approval for a redesign discussion, inspect relevant postings, and identify a low-cost way to demonstrate a missing skill. Exploration takes time and energy, and a worker may lack capacity or a safe workplace in which to investigate. Set an effort limit and review date. If conditions are untenable or an alternative requires immediate action, account for that reality rather than treating resignation as a failure to plan.

When is waiting for redesign a poor bet?

Waiting is a reasonable choice only while it buys information you can use and the cost of waiting remains manageable. A redesign promise should not become the default plan simply because it sounds reassuring or because no decision has been announced. Set a personal review horizon around a concrete event: a scheduled discussion, a trial decision, a budget or staffing decision, or a point when you must act on notice, income, health, immigration, or caregiving needs. The horizon is yours, not a universal number of weeks. It should reflect how long you can stay under current conditions without losing options you need.

Ask who owns the proposed redesign and what decision that person can make. A useful commitment identifies an accountable owner, a next date, and the specific information expected by then. A trial with a named reviewer may tell you whether a recurring task can be changed safely or whether verification absorbs the apparent time saving. An informal statement that the company is exploring AI, with no owner or date, offers little information about your role. That absence may mean the organization is delayed or undecided; by itself, it does not show that a job loss is imminent. It does mean you should avoid treating the promise as a dependable plan for your own finances or schedule.

Compare what you observe at each review point with the work and terms you actually have. Assignments that steadily shrink, duties removed without replacement, worsening hours or terms, or a decision process that repeatedly slips are reasons to ask what changed and what remains undecided. These signs do not predict displacement, but they can show that the current arrangement is deteriorating or that waiting is consuming time. Separate a missing answer from a negative answer: note what was promised, what happened, and what you still need to know. If there is no safe way to ask, use what is visible in your own work and the terms you have been given.

The decisive test is whether delay is closing a feasible option. If waiting could jeopardize an income floor, an immigration or notice deadline, treatment, recovery, or care responsibilities, parallel exploration may be prudent before certainty arrives. This need not mean resigning or committing to a new path; it can mean checking an adjacent role's entry requirements or identifying what evidence a transition needs. If the role remains tolerable, terms are stable, and an authorized trial has a credible owner and review date, waiting for its specific information may be worthwhile. Reassess at your set date; do not let postponed dates silently extend the decision.

A redesign is a poor default when no accountable route to an answer exists, conditions are worsening, or delay conflicts with an immovable constraint. Preserve room to act while internal discussion continues. If conditions remain workable and a bounded trial can provide relevant information, the calculation differs. A review horizon ties waiting to useful information and a personal limit, rather than treating optimism or uncertainty as evidence about what the employer will do.

Choose one next step this week

This week, choose one task flagged by the checker and write down one safe, observable change to look for—or one unanswered question about how that task is handled. Keep the note specific to a recurring step: what input arrives, what output is expected, and what a person currently checks or decides. Then choose a single next move tied to that note. If workplace rules allow, ask the accountable manager who could own a bounded trial and when its result would be reviewed. You are asking for a route to useful information, not a promise that the role will remain unchanged. If there is no authorized trial, or discussing the work could put you at risk, use public role information and privately inspect one realistic adjacent path. Look for its repeated entry requirements and identify one gap worth checking before spending money or making a commitment.

The free [AI Proof Work task checker](/ai-job-risk-checker) offers task-level change-pressure signals to help identify where to look. The optional [career roadmap](/career-roadmap) compares scenarios against personal constraints. Neither provides a validated personal probability of displacement or guarantees work or income. Let the task you selected determine whether the next useful step is a permitted workplace question or quiet exploration; one focused observation is enough to start.

Questions readers ask

Does a high checker signal mean I will lose my job?

No. It indicates task-level change pressure, not a validated probability of job loss. Check whether the task is used repeatedly at work and whether ownership, review, workload, or accountability have changed.

What makes a role-redesign trial credible?

A defined task, permitted tool and data use, a baseline, quality and workload measures, assigned responsibility for review and exceptions, and a decision date. A local trial can test a workflow; it cannot predict staffing or long-term demand.

When should I explore another role instead of waiting?

Explore in parallel if work is shrinking, no authorized person can define a trial, conditions are worsening, or waiting threatens an important financial, health, immigration, or caregiving need. Compare paths against local requirements and your constraints.

Sources and notes

  1. Workers’ exposure to AI: What indicators tell us – and what they don’t

    Exposure indicators estimate potential task susceptibility under stated methods; they do not by themselves predict employer adoption, workflow redesign, economic feasibility, labor-market outcomes, or an individual's displacement.

  2. Generative AI and jobs: A 2025 update

    The 2025 ILO assessment combines task-level data, expert input, and AI predictions across nearly 30,000 tasks and four exposure gradients; it estimates one in four workers globally is in an occupation with some exposure, with transformation more likely than redundancy in its assessment.

  3. ILO–NASK Index methodology

    The index combines assessments of a representative sample of Polish occupational tasks from a large worker survey, expert input and Delphi-style discussions, then applies AI-assisted estimation to ISCO-08 task descriptions; its stated purpose is to locate likely work change, not job disappearance.

  4. Anthropic Economic Index report: Uneven geographic and enterprise AI adoption

    Anthropic classifies anonymized Claude conversations by task and interaction pattern; its reported sample provides evidence of use on that product and changing automation/augmentation patterns, not representative employer adoption or job displacement.

  5. The impact of AI on the workplace: Evidence from OECD case studies of AI implementation

    Nearly 100 qualitative AI implementation case studies in manufacturing and finance across eight countries found job reorganization appeared more prevalent than displacement in studied cases; reported gains included less tedium, engagement and physical safety, alongside higher skill requirements and reported work intensity.

  6. The impact of AI on the workplace: Main findings from the OECD AI surveys of employers and workers

    OECD surveys of workers and employers in manufacturing and finance across seven countries found generally positive reported impacts on performance and working conditions, alongside job-loss concerns; training and worker consultation were associated with better worker outcomes.

  7. Employment Projections — 2024–2034

    BLS national projections use historical productivity and technology relationships; BLS describes AI effects as highly uncertain, says rapid future change could make historical relationships unreliable, and notes task composition may change without changing overall occupational demand.

Apply this to your own work

See the whole job market at once.

Explore which occupations AI may reshape, then turn the signal into a practical response.

Explore the job map