Within a fortnight, Workday and Dayforce both announced planning tools that start from tasks rather than headcount. Each will hold a breakdown of every job into its tasks, and a view of which ones belong to people and which to software. That breakdown is a new record in the HR estate. It will be read by people who were never meant to rely on it.
On 13 October, at its Rising conference in Las Vegas, Workday introduced Work Intelligence, a product that breaks each job into the tasks people perform and links those tasks to the skills they require. Nikki Helmer, Workday's vice president for talent management and insights, gave the premise in a sentence: "The basic building block of work is shifting from the job to the task." Two weeks later, at its Discover conference, Dayforce announced a Strategic Workforce Planning Agent. Leaders model scenarios in conversation, see the cost in salaries and AI token spend, and mark which work stays with a person, which an agent can augment and which is shared. Jake Varghese, Dayforce's chief product and technology officer, made the same diagnosis: "For decades, workforce planning has started with headcount and worked backward."
Neither product is generally available. Work Intelligence is with early-access Workday HCM customers. The Dayforce agent is expected in the first quarter of 2027. Coverage will judge both on their modelling. For the person who runs the HRIS, the more consequential thing is the record they will leave behind: a description, held in the system of record, of what every job consists of.
A record most organisations have never written
Job architecture is familiar ground. Families, levels, grades and profiles have been maintained for years, imperfectly, by Total Rewards or the HRIS team. The task layer underneath is different, because almost nobody has written it down. Job descriptions list duties, but they are drafted to recruit and are rarely revisited after the hire. Few organisations hold a task list that a line manager would sign as an accurate account of what the role involves this quarter.
So the task list will mostly be produced by the software, from what the platform already holds. Workday says Work Intelligence draws on Skills Cloud, an ontology of more than 75,000 skills used by more than 3,450 customers, together with the people, job and skills data customers already keep in Workday. Dayforce describes a single data model that puts people, skills, structure and cost in one view. Neither announcement says how a generated task breakdown is reviewed, corrected or approved before a plan depends on it.
That is a fair omission for products in early access. It is also a fair description of the default. Left to itself, the decomposition will be inferred from job profiles of uneven age, accepted because it reads plausibly, and then used.
The plan travels further than it used to
A headcount plan was a spreadsheet by cost centre. It seldom left the finance and HR leadership group, and when it did, it went in aggregate. A task-level plan says much more. Role by role, it records which work the organisation intends to hand to software. In Dayforce's design it also shows, position by position, how closely the current incumbent matches the skills the position requires.
A job description could be slightly fictional because little rested on it. A task list that justifies moving work to an agent will be read as a statement of fact.
Consider where such a plan can end up. In Great Britain, an employer proposing 20 or more redundancies at one establishment within 90 days must give employee representatives, in writing, "the reasons for his proposals" and the proposed method of selection, under section 188 of the Trade Union and Labour Relations (Consolidation) Act 1992. If the reason is that a role's tasks were reassigned to agents in a planning model, representatives will reasonably ask to see the task analysis and how it was produced.
In Germany, the Works Constitution Act requires the employer to inform the works council "in full and in good time" about manpower planning (section 92), and in due time about plans for work processes and job design (section 90). A tool that redraws jobs as bundles of tasks is about both. The EU AI Act's Annex III, meanwhile, classes as high-risk AI used "to make decisions affecting terms of work-related relationships", including termination, and AI used "to allocate tasks based on individual behaviour or personal traits or characteristics". Aggregate scenario modelling is probably some distance from that line. A per-person skills match used to decide who moves, who retrains and who leaves is much closer to it.
Workday's release states that neither Work Intelligence nor its companion Decision Intelligence makes decisions about people. That describes the software. Whether an organisation uses the outputs to make such decisions is a choice the vendor cannot make on its behalf, and the task list is where that choice will be tested.
Figure 1
Where the task list is used | Who may end up reading it | What it has to withstand | Minimum control |
|---|---|---|---|
Exploratory scenario modelling | HR and finance leadership, planners | Internal challenge only | Label as unvalidated; no named-employee views |
Role redesign and job profile changes | Line managers, incumbents, Total Rewards | Grading appeals; equal-value comparisons | Manager review and sign-off; change logged against job architecture |
Reskilling and internal moves | Employees through learning paths and career tools | Employee trust; fairness of who is offered what | Documented criteria for who receives which recommendation |
Per-person skills match | Managers, HR business partners | Possible high-risk classification under AI Act Annex III if used for decisions about individuals | Written rule on permitted uses; access logging; human review |
Redundancy proposals (GB) | Employee representatives, tribunals | Section 188 disclosure of reasons and selection method | Point-in-time version of the plan and task list, reproducible on request |
Restructuring with a works council (DE) | Works council | Information duties on manpower planning and job design (ss. 90, 92) | Method briefed before pilots; agreed review cycle |
The same artefact, six audiences. Uses and controls are editorial assessment, not survey data or legal advice. Statutory references: Trade Union and Labour Relations (Consolidation) Act 1992, s. 188(4); German Works Constitution Act, ss. 90(1) and 92(1), official English translation; EU AI Act, Annex III, point 4. Product capabilities as described in the Workday release of 13 October 2026 and the Dayforce release of 27 October 2026.
Govern it like the job catalogue
The remedy is unglamorous. Task decompositions need the treatment already given, with varying success, to the job catalogue and the position hierarchy.
They need an owner, and it should not be the tool. A task breakdown is a child of the job it describes, so it belongs with whoever maintains job architecture. Splitting the two guarantees drift within a year.
They need validation before use. A generated task list is a hypothesis about a role. Managers, and where practical a sample of incumbents, should confirm or correct it before it supports anything beyond exploration. Measuring how much they change in a small pilot will say more about a product's readiness than any demonstration.
They need versions. Workday positions Work Intelligence for continuous planning rather than one-off studies, which means the task model will move as agents take on more. A plan approved in March has to be reproducible against the task list as it stood in March. Otherwise nobody will be able to explain a June decision when it is challenged the following spring.
And they need a boundary. The organisation should decide, in writing, which outputs may be viewed at the level of a named employee, by whom and for what purpose, and log that access. This is where planning stops and assessment begins, and it is the line regulators and works councils will look for first.
Before the first task-level plan reaches the executive committee
Name an owner for the task layer, and place it with job architecture rather than with the planning tool.
Ask the vendor how task breakdowns are generated, from which data, and whether customers can edit, approve and lock them.
Pilot five roles: have managers review the generated task lists and record how much they change.
Require version history and a point-in-time export of both the plan and the task list it used.
Set a written rule on which outputs can be seen at named-employee level, and switch on access logging.
Where a works council or recognised union exists, brief them on the method before any pilot, not after.
Agree with employment counsel how a task-reassignment rationale would be documented if it ever supports a redundancy proposal.
What this means for HR systems owners
The timing works in HR's favour, narrowly. Work Intelligence is in early access, the Dayforce agent is a 2027 deliverable. Budgets and pilots for next year are being set now. Finance will find a model that prices token spend against salary persuasive, and the CFO may well ask for one before HR has decided how the inputs are governed. The governance is cheap to set up before the first plan and expensive to retrofit after the first restructuring that cites one.
The questions belong in the evaluation itself, alongside the scenario demonstrations: who writes the task list, who can change it, and can you show what it said on a given date. A vendor that cannot answer the third is selling a planning tool that will struggle to stand behind its own plans.
The job description survived decades of inaccuracy because nothing much depended on it. The task list will not be given the same latitude.
Sources and notes. Workday, "Workday Introduces Work Intelligence to Help Customers Design Work for AI", press release, Las Vegas, 13 October 2026 (Nikki Helmer quotation; Skills Cloud figures; early-access availability; statement that neither Work Intelligence nor Decision Intelligence makes decisions about people). JobsnHire coverage of the launch, 17 October 2026. Dayforce, "Dayforce Introduces Agentic Strategic Workforce Planning to Help Leaders Design the Workforce of the Future", press release, Minneapolis and Toronto, 27 October 2026, via GlobeNewswire (Jake Varghese quotation; capabilities; expected availability Q1 2027). Trade Union and Labour Relations (Consolidation) Act 1992, s. 188, legislation.gov.uk; 2025 amendments not yet fully applied to the published text. Works Constitution Act (Betriebsverfassungsgesetz), official English translation, gesetze-im-internet.de, ss. 90 and 92. Regulation (EU) 2024/1689 (AI Act), Annex III, point 4. The description of how organisations hold task data today, and the uses and controls in Figure 1, are editorial assessment, not survey data. HRHubsMedia has no commercial relationship with any company named. Journalism, not legal or procurement advice. Corrections welcome.
