Two releases, and only one of them is about your project plan
Workday published two releases on September 2, 2026. One says Workday has been named a Leader in the 2026 Gartner Magic Quadrant for Cloud HCM Suites for 1,000+ Employee Enterprises for the eleventh consecutive year. The other says Workday signs a new state or local government nearly every week as agencies move off legacy systems, and counts more than 100 government entities that selected Workday in the past two years.
The first tells you where the product sits on an analyst grid. The second names twelve public bodies and gives timelines for two of them, five months for a city and roughly thirty for a state. Those two numbers are the most useful thing either release contains for anyone who has to put a date on a steering slide.
A signing a week counts procurements
A public-sector signing means a procurement closed. Somebody wrote the solicitation, a committee scored it, the protest window passed, and a council or legislature voted the contract through. Counting signings tells you Workday is getting through that process at a steady rate.
The release separates new customers from recently live ones, and we'd read the two lists differently. Eight have signed. Four are live. Nothing in the release says how long the eight will take, so the four are the ones worth calling. Our companion piece covers how to read the recognition without mistaking it for fit. Here we care about what happens after the signature.
Five months and thirty months are both true
The release says the City of Bell Gardens, California went live on Workday HCM and Workday Financials in five months after a decade on an aging legacy platform. It says the State of Georgia deployed across more than 200 agencies and more than 70,000 employees in approximately 30 months, replacing a heavily customized 25-year-old system.
The software did not change between Bell Gardens and Georgia. What changed is the number of distinct ways the organisation pays people and books money. A small city has a handful of bargaining units and one chart of accounts. A state with 200 agencies has 200 opinions about position control and a chart of accounts every controller has bent to their own reporting.
So before anyone quotes a timeline, count two things. The departments that run their own pay rules, and the funds and grants that need their own accounting. If those counts look like a small city, five months is a fair reference. If they look like Georgia, a five-month reference gets found out somewhere around month fourteen, usually by the payroll supervisor.
The conversion is rules first and records second
Data conversion in a public body is mostly rules. Step increases tied to anniversary dates, shift differentials for police and fire on 28-day work periods, retroactive pay when a contract settles late, pension reporting with its own definition of earnings. In a heavily customized 25-year-old system those rules live in code nobody has read for a decade and in the head of whoever has run every cycle since it went in.
Every one has to be found, written down, and signed off before the first parallel run. The release doesn't say how many parallel cycles Georgia or Bell Gardens ran, and we'd ask that first on any reference call. Our piece on payroll cutover as a reconciliation project covers the tolerances and sign-offs that decide whether a go-live is safe, and they bite harder when every payslip is a public record.
Georgia's state accounting officer is quoted saying that what once took days now takes minutes. We believe her. The months before that sentence became true are where the constraint lives.
Grants on spreadsheets are the finance half of the same problem
The release says Georgia's grants management was handled manually in spreadsheets and that basic data requests could take days. Grant periods rarely match the fiscal year, restricted money cannot pay for the wrong thing, and every cost has to be charged back to the award that funded it. A spreadsheet survives for twenty years in that setting because it encodes decisions nobody wanted to argue about in the ledger.
Moving that into Workday Financial Management means the chart of accounts gets redesigned rather than migrated, and the accounting officer and the external auditor own that design, on a calendar that has to clear a fiscal year boundary and an audit. Read our argument that modernisation needs a retirement list before the plan is written, because a grant tracker nobody formally retires keeps running beside the new ledger.
Early-access agents arrive after the rules are settled
The release names a Self-Service Agent, a Payroll Agent, and a Financial Audit Agent, all in early access. An agent that answers a leave question is only as correct as the leave rules loaded into the tenant, and a payroll agent that flags an anomaly is only useful once parallel runs have established what normal looks like. Our read of Workday's agent adoption numbers from the August 27 results applies here: adoption is a statistic about tenants that finished the hard part first.
A public body also answers records requests. Where an agent's actions are logged, who can produce that log, and whether it survives the retention schedule belong in the design review in month one, and in the contract, where it is cheaper to raise before signature than after.
Two numbers to write down before the Gantt chart
At the next steering meeting, write two numbers on the whiteboard. The departments that run distinct pay rules, and the funds and grants that need separate accounting. Then ask Workday for a reference customer that matches those two numbers rather than your headcount, and ask that reference how many parallel payroll cycles they ran, what the go-live scope left out, and which spreadsheet is still alive.
If nobody in the room knows the first number, that is your first deliverable. It costs a week with the payroll supervisor and a stack of collective agreements, and everything else on the HCM plan depends on it.
