ReleaseSignoff

User guide
Open the app

How to use ReleaseSignoff

This page walks through everything a signed-in user needs: signing in, reviewing your own features, checking overall status, and (for admins) importing a release. Everything described here reflects the app as it actually behaves today.

New reviewer

Start with My Work. It is the fastest way to find and confirm your own features and scenarios.

Admin

Jump straight to Admin for importing a release, adding reviewers and assigning who owns each area.

1

Signing in

A one-time emailed link does the whole job, and there is a password option if you prefer.

Enter your email on the sign-in screen and click Send sign-in link. A magic link arrives in your inbox within a minute or two; click it and you're in. There's no separate signup step. If you'd rather sign in with a password, Use a password instead switches the form over, provided a password has been set on your account.

Member of more than one organization? Most people are only in one, but if you administer or review for several, you'll see a Which organization? picker every time you load the app fresh. Pick one from the dropdown and click Continue. This is the normal post-sign-in flow, not an error or a login gate.
“Your email isn't set up on any organization yet” means nobody has added you as a reviewer yet. ReleaseSignoff doesn't support self-signup: ask your admin to add you by name and email, then try the sign-in link again.
2

Overview tab

Your landing page every time you sign in.

Overview shows the current release's label, its live status, and a running feature count at the top, followed by a quick-nav grid and a short set of stats for the release as a whole.

●
My Work
Your features and test scenarios
●
All Features
Search all rows
●
Testing
Track scenario execution
●
PM Dashboard
Completion by owner
●
Release Admin
Import a release, assign owners

This release at a glance

Below the quick-nav, a stats row totals up the release: total features, functional areas, reviewers, features reviewed so far, and features still unassigned. It updates live as reviews come in, so there's nothing to refresh.

The five quick-nav tiles are always visible to everyone, including Release Admin. If your account isn't an admin, clicking it just shows a message explaining that admin access is required, rather than being hidden entirely.
3

My Work: the fastest way to do your part

Your own features and test scenarios on one screen, with a count of what is left.

My Work is its own screen, and it holds two lists: the features assigned to you, and the test scenarios assigned to you. Each carries its own progress line, so you can see at a glance that you have, say, four of seven features reviewed and one of five scenarios still to go.

Rows arrive collapsed; click the chevron to expand one and reveal the review controls. That's a deliberate extra click rather than a bug, because it keeps the long descriptions and flags out of the way until you actually want them.

If nothing has been assigned to you for this release, each list tells you so rather than sitting empty.

You can only review your own rows. Review controls appear on the features and scenarios assigned to you. You can still read everything else in your organisation, including other people's reviews and comments, from the All Features and Testing tabs. Seeing a row you cannot edit is by design, not a permissions error.
4

All Features: the full table, with real filtering

Everyone's features in one grid, searchable and filterable.

Type into the search box to filter by title or functional area as you type. Every column header with a filter icon (Category, Functional Area, Impact/Effort, Owner, Training) opens a checkbox popover; the Owner filter's list includes an Unassigned entry alongside real owner names so you can isolate unassigned rows in one click. Click a column label itself to sort by it.

Active filters show up as removable chips above the table, each with its own × and a Clear all to reset everything at once.

Clicking All Features in the nav always resets to the full, unfiltered table, even right after using My Work. You never have to manually clear a stale filter left over from a previous visit.

Row detail

Click a row's chevron to expand it: full description, plus four status flags (Training/Testing Impact, Effort, End User Training, Super User Training recommendation). If it's your row, the review controls appear inline: a two-way toggle (Accurate as-is / Needs a change), an optional comment box, and Save.

Export

The export button in the toolbar downloads a CSV of exactly what's currently visible in the table, so it respects your active search text and filters. Filter down to your area first if you only want your own rows in the file.

5

PM Dashboard: status at a glance

Useful for anyone, essential for the person running the release.

A stat row up top totals features assigned and unassigned, the percentage reviewed, and how many reviews were flagged Needs a change. An alert card below calls out any functional area with no assigned owner at all, since those need attention before the review can be considered complete.

Underneath, owner-by-owner progress cards show how far each person has gotten through their own assigned features.

Unassigned functional areas also surface as a small red badge on the Admin icon in the app's nav rail, so a gap is visible even before you open the dashboard.
6

Testing tab: the second review type

Scenario execution, separate from feature-accuracy review.

Testing tracks execution of regression and integration test scenarios sourced from Workday's separate Testing Workbook. It is a different kind of review from All Features: All Features asks “is this description accurate,” Testing asks “did this scenario pass.” A release can need both, and they're tracked independently.

Each scenario row expands the same way rows do in All Features, but instead of a two-state toggle it uses four states, plus a notes field:

StatusMeaning
Not startedNobody has run this scenario yet.
PassedRan clean, no issues found.
Issues to resolveRan, but something needs follow-up.
BlockedCouldn't be run at all.

The toolbar lets you filter by type (Regression / Integration) and by status, and search by scenario or functional area, mirroring the All Features toolbar.

A scenario only shows up on this tab if its functional area is currently in scope for the release. Admins control that per release in the Admin tab (see below); it doesn't remove the scenario from the catalog, it just excludes it from this release's Testing list.
7

Admin tab

Admins only. If you're a reviewer, this section doesn't apply to you.

If your account isn't an admin on the organization, the Admin tab shows a short message saying so and stops there. Everything below is for organization admins.

Importing a release

Upload one workbook: the heat map, meaning your tenant's “What's New in Workday” export or a heat map your team builds from it. It's parsed entirely in your browser; only the extracted data is sent to the server. Give the release a label (e.g. 2026R2) and click Import. It's safe to re-run an import for the same release label; it updates the release in place rather than creating a duplicate.

There is no owner roster to upload. It was removed on 2026-09-04 because it had no Workday equivalent and had to be written by hand before the app would show anyone anything. Owners are set in Who owns each area instead.

Importing a testing workbook

Upload the separate Feature Release Testing Workbook the same way. The scenario catalog is org-wide and carries over release to release; import the matching release's heat map first so the testing import can attach to it by label.

Testing Scope

Toggle a functional area in or out of the current release's Testing tab without deleting its scenario catalog. This mirrors the in-scope decision the workbook's own Dashboard tab makes per release.

People on this client

Everyone who can sign in to this client. Admins import the release and manage people; reviewers own functional areas and sign off. One person can be both, and the same person can be on several clients with a different role on each.

Add someone by typing their work email first. If they already work another client you administer, their name fills itself in and the app says where, because it is the same login rather than a second account. The email address is required: it is how they sign in, with a link rather than a password.

Each row can be renamed, switched between Admin and Reviewer, and deactivated. Two things are deliberately refused: deactivating someone who still owns functional areas, which would drop them out of every dropdown while features still pointed at them; and demoting the last remaining admin, which would leave a client nobody can administer.

Who owns each area

Every functional area the heat map names is listed here, and this is where a release becomes somebody's work. Add a reviewer with the Full name and Work email boxes at the top of the card, then pick them in the Owner dropdown for each area and click Save. The email address is required because it is how they sign in, with a link rather than a password.

The Features column shows how many of the current release's features each area holds, so you can see which assignments matter most. A line above the table says how many features still have no owner, and how many reviewers have not yet been told there is work waiting.

Notifying reviewers

Notify reviewers sends one email per person, listing how many features are waiting for them in this release. It skips anyone with nothing assigned and anyone already notified for this release, so it is safe to press again after assigning a few more areas. Assigning an area never sends an email on its own, which is what stops a reshuffle from mailing the same person a dozen times.

Aliases

When your heat map and your own area list spell the same functional area slightly differently (for example, “Common Financial Management” vs. “Common Finance Management”), add the variant in the Known aliases column. Future imports resolve it to the right owner automatically.

Changing an owner takes effect immediately on the release currently open: its features move into the new owner's My Work without re-importing anything. A past release does not move, because it is a sign-off record of who decided what and when.

Handing the release over

The Handover pack button, on both the PM Dashboard and the Admin tab, opens everything decided on this release as one document: the summary, what was flagged or left unowned, who signed off and when, the full feature register and the testing results. Save as PDF and Download Excel are inside that window.

It reads as a status report while the release is open and as a sign-off record once it is past, and it says which it is at the top.

Clients, for a consultancy

If you run releases for several clients under one account, a Clients tab appears alongside the others. It lists every client with where its current release stands, a Your team view showing each person once with the clients they work, and Add a client. Naming that client's PM is part of creating it, because a client nobody can administer is one nobody can open.

A single customer with one client never sees this tab: their account and their client are the same thing.

8

Switching organizations, signing out

Two controls, both in the header.

If you belong to more than one organization, the client picker in the header switches between them without signing out, and the app remembers the last one you were in. The Which organization? picker still appears right after sign-in when you belong to several.

Next to it, the release picker appears once an organization has more than one release. The current release is marked Live; an earlier one reads Past release in amber and accepts no new answers, because it is the sign-off record of who decided what and when. Beside that, a countdown shows how long until production: neutral while the date is far off, amber inside 30 days, and red inside 7.

Sign out using the sign-out icon in the app's header, next to your name.