Use Workday Mass Job Change interactive tables when HR Partners or managers need to edit, validate, review, and approve up to 5,000 job changes inside Workday under constrained row-level security. Use an Inbound Change Job EIB when you are loading more than 5,000 rows, applying unique pre-calculated M&A spreadsheet values to every single worker, or running central HRIS cutover loads under integration security.
With Workday replacing legacy Worksheets-based Mass Actions Workbooks with standalone Mass Job Change tables (opt-in today via Maintain Feature Opt-Ins, and automatic for all tenants in 2027R1), Core HCM admins now have two genuinely different bulk staffing tools—each with sharp limits that can wreck a weekend reorganization if you pick the wrong one.
Side-by-Side Comparison: Mass Job Change Tables vs. Change Job EIB
| Capability / Limit | Mass Job Change Tables | Inbound Change Job EIB |
|---|---|---|
| Capability / LimitVolume & Runtime Ceiling | Mass Job Change Tables5,000 transactions maximum per table | Inbound Change Job EIB5-hour runtime per load; 30 MB browser upload (300 MB XLSX / 1 GB XML via SFTP/REST/S3); max 5 concurrent EIBs |
| Capability / LimitSecurity Enforcement | Mass Job Change TablesContextual, role-based, constrained, and intersectional row security (supervisory org, location, cost center) | Inbound Change Job EIBUnconstrained central load governed by EIB integration security and Change Job web service permissions |
| Capability / LimitPre-Submission Validation | Mass Job Change TablesReal-time Workday and custom validations directly in the table (Valid, Invalid, Warning, Not Edited) |
Inbound Change Job EIBBatch Validate Only mode or post-load XML/HTML troubleshooting files (ErrorsAndWarningsSpreadsheet.xml, kept 60 days) |
| Capability / LimitPopulation Restrictions | Mass Job Change TablesAvoid mixing employees + contingent workers, or Position Management + Job Management orgs, in one table; unfilled positions excluded | Inbound Change Job EIBSupports employees and contingent workers via Change_Job SOAP request columns; requires exact WIDs/reference IDs |
| Capability / LimitSubprocess Coverage | Mass Job Change TablesOrganization Assignments and Compensation Change tabs (plus Personnel Action Requests for US Federal) | Inbound Change Job EIBSupports org, pay group, location, and comp columns; supports at most 1 Maintain Employee Contract subprocess per upload |
| Capability / LimitWorkflow & Rollback | Mass Job Change TablesOptional Review (editable table), Approve (read-only table), Send Back, Deny, and one-click mass Rescind | Inbound Change Job EIBUses web-service-specific routing on Change Job BP; mass fixes require Correct Change Job web service or custom cancel scripts |
Opt-In Is a One-Way Door Before 2027R1
Mass Job Change does not require Workday Drive or Worksheets. However, once you opt in on Maintain Feature Opt-Ins, you cannot revert to Mass Actions Workbooks for mass Change Job processing. Test your templates and security in Sandbox or Implementation first.
Setting Up Mass Job Change Without Missing Tabs or Permissions
Two configuration oversights cause 90% of broken Mass Job Change pilots: missing initiating-action permissions for reviewers, and missing subprocess entries on the consolidated template.
1. Align Domain and Business Process Security Policies
Granting access to Start Mass Job Change requires three distinct security policy updates before running Activate Pending Security Policy Changes:
- Domain Security (
Edit Domain Security Policies): On the Mass Action Events domain in the System functional area, grant View or Modify permissions to your target roles (for example, HR Partner or Manager) so they can run the Start Mass Job Change report and open tables. - Mass Action Event BP Policy (
Edit Business Process Security Policies): On the Mass Action Event policy in the Staffing functional area, grant permissions to initiate mass job change events, complete mass actions, view/cancel in-progress events, and—if using workflow routing—Review Mass Action Event, Approve Mass Action Event, Deny, and Rescind. Note that unlike legacy Mass Action Workbooks, the Complete Mass Action step on Mass Job Change supports constrained security groups. - Change Job BP Policy (
Edit Business Process Security Policies): On the Change Job policy in the Staffing functional area, locate Who Can Start the Business Process and assign the Change Job (Mass Action) initiating action to every security group that interacts with the table—including reviewers and approvers, not just initiators. Also confirm initiating roles hold View All under Who Can Do Actions on Entire Business Process so business process validations fire reliably.
2. Enable Subprocess Tabs in Both Templates
If your HR Partners open a Mass Job Change table and only see the primary Change Job tab—with no Organization Assignments or Compensation Change tabs—check the consolidated template rule:
Fails (Subprocess tabs stay hidden on Mass Job Change Table):
- Maintain Change Job Templates -> Initiation Action: Mass Actions
-> Subprocesses added: Change Organization Assignments for Worker, Propose Compensation Change
- Configure Business Process Consolidated Template (Change Job) -> Subprocesses NOT added
Works (Tabs and fields render on Mass Job Change Table):
1. Open Maintain Change Job Templates -> select Mass Actions under Select Initiation Actions,
choose sections, and add Change Organization Assignments for Worker + Propose Compensation Change.
2. Open Configure Business Process Consolidated Template -> Business Process Type: Change Job
-> add both subprocesses to the Templates grid.
3. Confirm domain access on Staffing Actions: Change Job Date and Reason,
Staffing Organizations: Header, and Add Compensation / Compensation Change domains.If you also want bulk event Rescind available after mistakes, open View Mass Action Type, select Change Job, check Enable Rescind, grant Rescind on the Mass Action Event security policy, and activate security changes. To force users to document why a reorganization row changed, enable comments on the Change Job business process and attach a validation condition rule on initiation checking Comment for Mass Action Worker Event is blank.
Four Execution Traps Inside Mass Job Change Tables
Even with clean security, train your HR operations team on four table mechanics before launching a live reorganization from Start Mass Job Change:
- Silent Population Exclusions: Workday generates one row per eligible filled position. Unfilled positions and workers outside the initiator’s Change Job initiating permissions never appear as error rows inside the table; they only increment the Positions Excluded from Mass Action counter on the My Tasks item. Always reconcile your expected headcount against
Table Rows + Positions Excludedbefore editing. - Keep Homogeneous Populations: Do not combine employees and contingent workers in the same table, and separate Position Management supervisory organizations from Job Management supervisory organizations into distinct Mass Action Events so template fields and position validation rules behave predictably.
Submit Tablevs.Submitin My Tasks: These two buttons do completely different things. Inside the open grid, Submit Table validates and launches Change Job events for valid rows (partial selection submission is not supported; click Refresh on the row status summary to confirm counts). Back in My Tasks, clicking Submit closes the Mass Action Event and permanently discards every unsubmitted row left in the table—including rows hidden from the current user by constrained security. Never click Submit in My Tasks while invalid or hidden partner rows remain unfinished.- Stale Rows Between Review and Approval: On Review Mass Job Change, reviewers receive an editable table and can fix invalid rows in Mass Edit or the single-row editor. On Approve Mass Job Change, approvers receive a read-only table (
EditandMass Editare disabled). If a concurrent transfer or termination makes a worker row invalid between Review and Approve, Workday skips that invalid row when the approver clicks Approve—leaving it unsubmitted unless sent back via Send Back.
When Inbound Change Job EIB Is Still the Right Tool
Reach for an Inbound Change Job EIB (built via Create EIB around the Change Job web service operation and Generate Spreadsheet Template) in four scenarios where interactive tables slow you down:
- Enterprise Reorgs Over 5,000 Workers: Rather than manually orchestrating four separate 5,000-row tables, a single SFTP-delivered XLSX (up to 300 MB) or XML payload (up to 1 GB) processes within Workday’s 5-hour inbound EIB runtime window (staying under 30 MB if uploading directly in the browser).
- Row-Unique Spreadsheet Mappings: Mass Job Change’s Mass Edit shines when applying shared values (new Cost Center, new Location, new Manager) to filtered cohorts. When an M&A mapping file assigns 3,200 distinct job profiles, business titles, and individual base pay figures already calculated in Excel, generating and validating an EIB spreadsheet avoids manual cell-by-cell entry.
- Repeatable Cutover & Correction Loads: EIB spreadsheets can be version-controlled, run in Validate Only mode during dress rehearsals, and paired with a Correct Change Job EIB if effective dates or reasons need high-volume post-cutover adjustment.
- Mixed Contingent and Employee Batches: Provided your EIB template columns and reference IDs match each worker’s staffing model and avoid multi-contract uploads (since the
Change Jobweb service supports only one Maintain Employee Contract subprocess per event), central HRIS teams can run scripted loads without constrained UI visibility blocks.
Pre-Cutover Verification Steps in Sandbox
Before running either method in Production, prove your exact configuration on a 20-worker test slice after a Sandbox refresh:
- For Mass Job Change, launch Start Mass Job Change, open the table from My Tasks, verify Positions Excluded equals zero, confirm Organization Assignments and Compensation Change tabs render, test Review and Approve as constrained personas, and confirm Rescind appears on the Archive tab of My Tasks.
- For Change Job EIB, run the integration with Validate Only checked first, inspect any
ErrorsAndWarningsSpreadsheet.xmlrows, then launch a small live batch and verify downstream Assign Pay Group, Change Benefit Elections, and Propose Compensation Change steps route as configured on your Change Job BP definition.
If you need to audit your tenant’s Change Job consolidated templates, trace missing domain permissions, or transform a messy reorganization workbook into a validated EIB load, Kiweely Vine inspects your connected tenant configuration, flags security mismatches, and prepares tested templates with your explicit approval before anything touches Workday.
Frequently asked questions
What is the maximum number of workers in a Workday Mass Job Change table?
A single Workday Mass Job Change table supports up to 5,000 transactions. For reorganizations exceeding 5,000 workers, you must either split the population across multiple Mass Job Change tables or load the transactions through an Inbound Change Job EIB.
Can you switch back to Mass Actions Workbooks after opting into Mass Job Change?
No. Opting in to Mass Job Change on the Maintain Feature Opt-Ins task is permanent for mass Change Job processing, and starting in 2027R1 Workday automatically replaces Mass Actions Workbooks with Mass Job Change tables for all customers.
Why are the Organization Assignments and Compensation Change tabs missing on my Mass Job Change table?
Adding subprocesses on the Maintain Change Job Templates task alone does not render tabs on a Mass Job Change table. You must include those subprocesses in both your Change Job template and the Templates grid on the Configure Business Process Consolidated Template task for Change Job.
What happens to unsubmitted or unauthorized rows when someone clicks Submit in My Tasks?
Clicking Submit on the My Tasks item completes the Mass Action Event and permanently discards every remaining row in the table, including rows that the user could not see due to constrained security. Always click Submit Table and verify row status counts before completing the My Tasks step.