---
title: "Workday Change Control Process With an Audit Trail — Kiweely"
description: "A change control process a two-to-five person Workday team can run: what to control, who approves, which tenant tests it, and which Workday reports prove it."
url: https://kiweely.com/guides/workday-change-control-audit-trail
---

# Workday Change Control for a Small Team: Request, Sandbox Test, Approval, Production and the Audit Trail

One change control process for a small in-house Workday team, from request to Production, with the Workday reports (audit tags, Audit Trail, policy history) that show an auditor each change.

-   **Checked** against Workday on November 18
-   Applies to **In-house Workday HCM, Payroll and Financials teams**
-   8 min read
-   Published November 18
-   By Kiweely

A small Workday team doesn’t need a change advisory board. It needs five things it can keep up every week: a short list of changes that are controlled, one place where every request lives, a rule that controlled changes are built and tested outside Production, a second person’s approval before Production, and a monthly check that compares what Workday says changed with what the tickets say changed. Workday already records most of the proof. This guide puts the process and the reports together.

The Workday facts here come from Workday’s documentation, listed in the sources. The practices come from in-house teams who described theirs on r/workday, linked where we use them; they are what those teams reported, not rules.

## Step 1: decide what is controlled

Controlling every change is the usual reason a process collapses. One admin [described exactly that](https://www.reddit.com/r/workday/comments/15ab1dc/): at companies where they had tracked every Production config change with calls and change management, “it became too much”, and they cut the scope to integrations and bigger changes. On a thread about a first SOX audit of Workday change management, the [advice that drew agreement](https://www.reddit.com/r/workday/comments/1ly47vk/) was to ask “What’s the risk to financials” and to keep proof that impactful changes were tested and approved; another reply listed what their team audits: specific business processes and key integrations (payroll, taxes, benefits, AD, security), from a pre-defined list.

A workable split for a small team:

| Tier | What is in it | What it needs |
| --- | --- | --- |
| Controlled | Business process definitions that touch pay, benefits, hiring and termination; security groups and domain or business process security policies; integrations (payroll, benefits carriers, identity); calculated fields and reports that feed pay, finance or audit evidence | Ticket, test in a non-Production tenant, recorded approval by someone other than the builder, migration record, check after the move |
| Logged | Other business process steps and notifications, reports other people use, organization and lookup changes | Ticket that says what changed and why |
| Not tracked | Personal reports, help text, announcements | Nothing |

Write the list down and get your auditors to agree to it before the first audit, not during it. One consultant in the same thread [notes](https://www.reddit.com/r/workday/comments/15ab1dc/) that the interpretation of SOX “varies from auditor to auditor”.

## Step 2: one place for every request

Every change starts as a ticket, whatever the tool: Workday Help, Jira, ServiceNow or a form. The rule that makes the audit trail work is the one an admin [put plainly](https://www.reddit.com/r/workday/comments/15ab1dc/): if it’s not in the ticket, it doesn’t go to Production. The ticket holds:

-   what is asked and why, and who in the business owns it;
-   the tier;
-   the objects that will change (the business process definition, the security group, the integration system);
-   the test evidence and the approval, once they exist.

Choosing the tool is its own question; our guide to [HRIS ticketing in Workday Help, Jira or ServiceNow](https://kiweely.com/guides/workday-hris-ticketing-help-jira-servicenow) compares them.

## Step 3: build and test outside Production

Workday’s course manual for HCM administrators describes the Sandbox tenant as the place administrators “develop and test new features, customizations, and configurations before deploying into the main production tenant”. Two things to plan for:

-   **The Sandbox is refreshed from Production every week**, and the refresh wipes your changes. Finish and migrate a change inside the week, or list it with Configuration Change Tracker before the refresh. Our [Sandbox refresh guide](https://kiweely.com/guides/workday-sandbox-refresh) covers what survives.
-   **Test as the people who use the change**, not as an administrator. An administrator sees steps, fields and tasks the real approver won’t.

For a business process change, Workday recommends testing in a preproduction tenant and then running the **Business Process Exception Audit** report to find definitions with critical errors. Workday also runs a background process every hour that finds exceptions, including ones caused by changes outside the definition, such as removing a security group from a business process security policy while the definition still uses it. A broken definition can’t be initiated until it is fixed, so run the report before you call the test done. The **Security Exception Audit** does the same for security configuration that a policy change made invalid.

Attach what you ran and what you saw to the ticket: the scenario, the person you tested as, the result.

## Step 4: approve before Production

The approval that auditors look for is a person other than the builder, after the test, before the move. For a small team that means:

-   the business owner approves *what* (the requirement is met, in the test tenant);
-   a second team member approves *the move* (the test evidence is there, the scope matches the ticket).

One team on r/workday [said](https://www.reddit.com/r/workday/comments/1f8vjan/) an approval to move to Production is required because they follow SOX controls, and that they usually deploy on Thursday or Friday. Record the approval in the ticket with the date, not in an email nobody can find later.

## Step 5: move it, and keep the record

How a change reaches Production decides what record you get:

-   **Object Transporter** migrates configuration with its dependencies, runs a pre-migration check for missing prerequisites in the target tenant, and shows the differences between source and target for the instances you selected just before migration. Workday describes it as providing “auditing and reporting functionality that isn’t possible with manual configuration”.
-   **Configuration Change Tracker** reports configuration changes in a tenant over a date range and by selected users, sorted into Ready to Migrate and Not Ready to Migrate, with **View Changes** for an audit trail of each primary instance. From its report you can build an Advanced configuration package that contains only the instances you vetted.
-   **Re-keyed by hand** in Production, the change has no migration record, so the ticket and the audit reports below are the only evidence. Keep that path for changes the tools can’t move.

Our comparison of [Object Transporter and Configuration Change Tracker](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker) and the [Sandbox-to-Production checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist) cover the mechanics. After the move, rerun the test scenario in Production where it is safe to, and close the ticket.

## Step 6: prove it every month

The step most teams skip is the one that catches the change nobody ticketed. Once a month, pull what Workday recorded and match each change to a ticket. One admin [described](https://www.reddit.com/r/workday/comments/15ab1dc/) daily notifications for critical changes (business processes, security, custom validations) and monthly reviews for the rest, because “this will show you what actually changes” rather than what people say changed.

| What changed | Workday report that shows it |
| --- | --- |
| A tagged business process, custom report, user-based security group, domain security policy or integration system |  **Audit Trail Report**, after you tag the instances with audit tags. Workday describes audit tags as tracking what changed, who changed it and when. |
| Which related objects Workday follows for a tagged instance |  **Audit Trail Configuration Report**. Workday recommends using it together with the Audit Trail Report. |
| Domain security policies |  **Domain Security Policy History** (selected policies) or **Domain Security Policies Changed Within Time Range** (all), each with the date and the person |
| Business process security policies |  **Business Process Security Policy History** or **Business Process Security Policies Changed Within Time Range** |
| Anything one account, task or object changed |  **View User or Task or Object Audit Trail**. It has a display limit; **Create Audit Log** produces the same report as an Excel file in the background. |
| Configuration that could be migrated |  **Configuration Change Tracker**, by date range and user. It reports direct changes only: Workday’s example is a calculated field change that alters a condition rule, where only the calculated field shows. |
| Which Workday version you ran |  **Workday System Status**, which Workday notes is there for when an auditor asks |

Tag the controlled tier once (audit tags can be restricted to audit tag segments, so only the right people see them) and the monthly check becomes one run of the Audit Trail Report plus the two policy reports. A change in the reports without a ticket is the finding to fix, and usually the reason for the next process tweak.

For the access side of the same audit, see [auditing segregation of duties before a SOX review](https://kiweely.com/blog/auditing-workday-segregation-of-duties-before-sox-review); for a worked example of one change from request to Production, [the anatomy of a Production-safe Workday change](https://kiweely.com/blog/anatomy-of-a-production-safe-workday-change).

## The whole process on one page

1.  Ticket with requester, business owner, tier and the objects that will change.
2.  Build in Sandbox (or an Implementation tenant), inside the week.
3.  Test as the real roles; run Business Process Exception Audit or Security Exception Audit; attach the evidence.
4.  Business owner approves the result; a second team member approves the move.
5.  Move with Object Transporter or a Change Tracker package; re-key by hand only when the tools can’t.
6.  Check in Production; close the ticket.
7.  Monthly: Audit Trail Report and the policy history reports, each change matched to a ticket.

## Where Kiweely Nest fits

The hard part of this process for a team of two or three isn’t knowing it, it’s keeping it up next to the queue. **Kiweely Nest (coming next)** keeps to the same approval rule. As [kiweely.com/nest](https://kiweely.com/nest) describes it, Nest is a team of eleven AI specialists, led by Kai, the Solution Architect, for a company’s own Workday. Nothing changes in your tenant until you approve: each approval shows what it is now and what it will be after, a change is built and tested in a lower tenant first, and bringing it to Production needs your recorded approval. Routines only read; any change they want waits for you. Every approval is recorded with who approved it, when and what changed, and you can export the change log for your auditors.

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](https://kiweely.com/demo?for=nest) to walk through one of your own change requests in Nest.

## Frequently asked questions

### Which Workday changes need formal change control?

The ones with financial, pay or access risk: business process definitions for pay, benefits and hiring, security groups and domain policies, integrations such as payroll and benefits feeds, and the reports your auditors rely on. Agree the list with your auditors; many teams log everything else without approvals.

### Which Workday report shows who changed a business process or security policy?

Tag the business process or policy with an audit tag and run the Audit Trail Report. Domain Security Policy History and Business Process Security Policy History show policy changes with the date and the person, and View User or Task or Object Audit Trail shows changes by account, task or object over a period.

### Does Configuration Change Tracker give a full audit trail?

It reports direct changes to configuration in a tenant over a date range and by user, with View Changes for each primary instance. Workday's documentation says it doesn't report behavioral changes: a change to a calculated field shows, the effect on the condition rule that uses it does not.

## Sources checked

-   [Setup Considerations: Audit Tags](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/pzv1587159184725.html)
-   [Reference: Auditing-Related Reports](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/wln1467042699742.html)
-   [Concept: Exception Audit Reports](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/dan1370797846981.html)
-   [Concept: Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/concept--configuration-change-tracker.html)
-   [Concept: Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/omh1634567473070.html)
-   [Concept: eSignature Integrations Best Practices](https://doc.workday.com/admin-guide/en-us/manage-workday/user-experience/electronic-signatures/concept-esignature-integrations-best-practices.html)
-   [Workday Tenants and Tools (HCM Core for Administrators)](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Sandbox to Production Object Transporter checklist Confirm Customer Central access, build a supported Sandbox package or single instance, clear Pre-Migration Check, review Pre-Migration Diff, keep Merge for security unless you mean Override, then migrate to Production and keep the Post-Migration report.](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [### How do I build a Configuration Change Tracker package by user and time? Configuration Change Tracker builds a change list for selected users and a timeframe. Package Ready to Migrate instances as an Advanced configuration package, run blank reference ID and exception audits, then launch Object Transporter. Advanced packages migrate only what you selected.](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)
-   [### Object Transporter or Configuration Change Tracker: which moves Workday config? Object Transporter migrates configuration you select, with dependents on standard packages. Configuration Change Tracker builds a change list by user and time, then hands an Advanced package to OX without auto-adding extra dependents.](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [### When does the Workday Sandbox refresh, and what does it wipe? Weekly: Workday replaces the Sandbox with a full copy of Production data and configuration. Public Workday docs give no day or hour, so ask your tenant management contact. Preview refreshes twice a year, Implementation on demand.](https://kiweely.com/guides/workday-sandbox-refresh)

### More guides on Tenants and developer accounts

[All 25 guides](https://kiweely.com/guides#tenants)

-   [Automating Workday R1/R2 Release Regression Testing Across Two Tenants](https://kiweely.com/guides/workday-release-regression-testing-two-tenants)
-   [Is Kiweely free for a Workday personal developer tenant?](https://kiweely.com/guides/is-kiweely-free-personal-developer-tenant)
-   [Testing in a Workday Implementation: What’s Tested, by Whom, How Long, and What Can Be Automated](https://kiweely.com/guides/workday-implementation-testing)
-   [How Long Does a Workday Implementation Take? Workday’s Own Timelines by Scope](https://kiweely.com/guides/how-long-does-a-workday-implementation-take)
-   [Start a proxy test after an AI-suggested Workday change](https://kiweely.com/guides/workday-start-proxy-testing-after-ai-changes)
-   [When a Successful Payroll File Still Has the Wrong Tax or Garnishment](https://kiweely.com/guides/payroll-files-that-succeed-while-tax-and-garnishment-are-wrong)
-   [What Breaks a Workday Payroll File the Night Before Pay](https://kiweely.com/guides/what-breaks-a-workday-payroll-file-the-night-before-pay)
-   [Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)

### From the blog on Tenants and developer accounts

[All posts](https://kiweely.com/blog)

-   [Keeping Workday Design Workbooks, Test Scripts, and Tenant Setup in Sync](https://kiweely.com/blog/workday-design-workbooks-and-test-scripts-from-live-tenant)
-   [The Production tenant problem: why AI and enterprise systems need a trust layer](https://kiweely.com/blog/production-tenant-trust-layer)
-   [Workday Testing Tools Compared: Kiweely Vine vs Kainos Smart Test, Opkey and Tricentis Tosca](https://kiweely.com/blog/workday-testing-tools-compared)

## Your own AI Workday team, working from day one.

Kiweely Nest is coming next: eleven AI specialists for your company's Workday, and nothing changes in your tenant until you approve.

[Book a demo](https://kiweely.com/demo?for=nest) [See Kiweely Nest](https://kiweely.com/nest)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
