Workday’s 2027 R1 feature release reaches Production in March 2027, and your Sandbox Preview tenant gets it about five weeks earlier. For a team of two to five people, those five weeks are the whole job: decide what changes for you, test the processes that would hurt if they broke, and decide which new features to take. This guide gives the dates Workday publishes, a week-by-week plan with who does what, and what to hand to automation.
The Workday facts come from Workday’s documentation, listed in the sources. The testing practices come from in-house teams on r/workday, linked where we use them.
The 2027 R1 timeline
Workday doesn’t publish next year’s exact dates on its open documentation; they are in the Release Center, behind a Workday sign-in. What its public pages do fix:
| What | When | Source |
|---|---|---|
| WhatProduct and industry roadmaps for R1 | WhenOctober of the previous year (October 2026 for 2027 R1) | SourceWorkday Release Schedule |
| What“Coming Soon” release notes for high-impact features | When1 to 6 weeks before Preview | SourceWorkday Release Schedule |
| WhatFeature release notes | When1 week before Preview, and at Production | SourceWorkday Release Schedule |
| WhatNew features in Sandbox Preview and other preview tenants | WhenAbout five weeks before the release date, if not earlier | SourceWorkday course manual, HCM Core for Administrators |
| What2027 R1 in Production | WhenMarch 2027; every tenant type gets the release on the same date | SourceWorkday Release Schedule; course manual |
| WhatWhat’s New in Workday report | WhenUpdated every Friday in your tenant | SourceWorkday Release Schedule |
| WhatRelease notes in the Release Center | WhenEvery Wednesday and Friday (Pacific) before the service updates | SourceReference: Workday Release Center |
Workday labels release notes by Production date. Its own example: 2025R1 covers features delivering to Production in week 11 of 2025 (March 15), until the 2025R2 Production release. If 2027 follows that pattern, R1 Production falls in mid-March 2027 and Sandbox Preview in early February; check the Release Center for the day before you book people’s time.
Between the two feature releases, weekly service updates land in the weekend maintenance window. Workday describes them as delivering “timely fixes and enhancements that are less impactful to customers”. One in-house admin described their practice: regression test the two releases, and don’t test the weekly patches. Others in the same thread warn that calculation changes do sometimes arrive between releases, so read the weekly notes for the features you use.
Before Preview: the test inventory (January 2027)
The work that makes a five-week window possible happens before it opens. Build, or dust off, one list of what you test every release. One team ranks theirs in this order, and pulls the same inventory out for every release:
- Critical business processes, alone or strung into end-to-end scenarios (hire, job change, compensation change, termination; for Payroll, a pay calculation).
- Critical functional tasks.
- Custom-built solutions: Extend apps, Studio integrations, custom reports used by integrations.
- Areas of complex configuration: many condition rules, many branches.
- Critical reports.
- Workday exception reports.
For each item, write down who tests it and as whom. Test as the role that uses it (the employee, the manager, the HR partner, the payroll administrator), not as an administrator, who sees more than they do. Our guide to testing Workday with Start Proxy personas covers how, in non-Production tenants.
Baseline what you can measure before Preview arrives: run the critical custom reports and integrations in Production or Sandbox and keep the output, so in Preview you compare files instead of eyeballing them.
The five weeks, for a team of three
The plan below assumes three people: a lead who owns the release, a functional analyst and someone who owns integrations and reports. With two, the lead takes the security week; with five, split the business process tests by module.
| Week | What happens | Who |
|---|---|---|
| WeekWeek 1: Preview arrives | What happensRun What’s New in Workday in Sandbox Preview. Sort every item into automatically available or opt-in. Create adoption items for the ones that matter (below). Confirm everyone who tests can sign in to Sandbox Preview. | WhoLead |
| WeekWeek 2: business processes | What happensRun the critical-path scenarios as the real roles. Check inbox routing, notifications and condition rules. Run Business Process Exception Audit. | WhoFunctional analyst |
| WeekWeek 3: integrations | What happensLaunch the critical integrations in Sandbox Preview and compare output with the baseline. Read any release notes on web service versions you call. | WhoIntegrations owner |
| WeekWeek 4: reports and security | What happensRun the critical reports against the baseline. Look for new securable items and their default domains; run Security Exception Audit. | WhoIntegrations owner, lead |
| WeekWeek 5: decide and prepare | What happensDecide the opt-in features (take now, later, or never). Write what changes for employees and managers. Agree who checks what on Production day. | WhoLead |
| WeekProduction weekend and Monday | What happensSign in, check single sign-on, run one critical report, confirm integration schedules are running, watch the first business process events and the ticket queue. | WhoAll |
Sort the release with the Adoption Planning Hub
Workday’s Adoption Planning Hub lets you create adoption items straight from the What’s New in Workday report: one item per release note, one item for a group of notes, or a link from notes to an existing item. Items sit in a backlog (In Backlog, In Review, Prioritized) or on a roadmap (Deferred, On Roadmap), and close as Completed, Duplicate or Will Not Do. For a small team that turns “hundreds of release notes” into a short list with an owner and a status, in the tenant, where an auditor can see it.
If your company uses Workday’s Adoption Agent, its Release Impact Analysis compares automatically available features with your tenant’s usage and marks each note Testing Recommended, Configuration Required, Review Only, No Impact, Unknown Impact or Analysis Blocked. It relies on the security of the person who runs it, so items they can’t see are left out and the test plan is incomplete. Our guide to the Adoption Agent’s release impact analysis covers it, and what still costs Flex Credits in non-Production tenants covers the cost side.
What not to miss
- Changes to how existing things work. One admin warns that many updates only add things, but notes that deprecate fields or change existing behavior are the ones to test.
- Your own deviations from delivered Workday. Custom reports, custom security, Extend apps: another admin in the same thread puts the emphasis there.
- Opt-in features with security. An opt-in feature often needs a domain or business process policy enabled before anyone sees it. Note which ones you take, and run them through your normal change control after Production.
Where automation helps, and where it doesn’t
Automated UI tests that click through Workday by screen position or selector break when Workday moves the screen, which a feature release does. Tests written as goals (“as this manager, approve this compensation change and confirm the worker’s pay”) survive layout changes, because the tester, person or AI agent, looks for the task, not the pixel. Our UI test charter for AI agents and the post on goal-driven agents versus scripts for release testing cover the setup. Whatever runs the tests: give it personas in non-Production tenants only, baseline the critical reports before Preview, and record failures as they happened; a flaky run marked green is worse than a failed one.
For running tests in Preview and Sandbox side by side, see regression testing across two tenants.
After Production
The release isn’t finished on Monday. The opt-in features you deferred are now roadmap items; the ones you took go through change control; and the next release’s roadmap arrives in April. A one-page record of what you tested, what you found and what you decided is the start of next release’s inventory.
Where Kiweely Nest fits
The release is planned work that lands on top of everything else twice a year. Kiweely Nest (coming next) is built for the team carrying it. As kiweely.com/nest describes it, Nest is eleven AI specialists for your company’s own Workday, led by Kai, the Solution Architect. Projects such as open enrollment and year-end are planned, with who is on each; routines run checks on a schedule; and dashboards show what the team is doing. A change is built and tested in a lower tenant first, and nothing changes in your tenant until you approve it.
Nest is $999 per seat a month, with 20,000 Kiweely Credits included each month, and it starts with a 30-day pilot whose $999 counts toward an annual contract. Book a demo and bring your release calendar.
Frequently asked questions
When is Workday 2027 R1?
Workday's release schedule puts the yearly R1 release in March. New features reach Sandbox Preview and other preview tenants about five weeks before the release date, and then every tenant gets the release on the same day. The exact 2027R1 dates are in Workday's Release Center, which needs a Workday sign-in.
How long is the Workday Sandbox Preview window?
About five weeks. Workday's course manual for HCM administrators says new features reach preview tenants approximately five weeks before the feature release, if not earlier.
Do we need to regression test every weekly service update?
Most teams don't. Weekly service updates land in the weekend maintenance window and Workday describes them as less impactful. Read the weekly release notes for changes to features you use, and keep full regression testing for the two feature releases.