Track Workday Field Changes with RaaS and Worker BO Reports
To track field-level changes in Workday, build a custom report on the Worker business object with the fields you care about, enable it as a web service (RaaS), pull it on a schedule, and compare each snapshot with the last one to log what changed. Use Workday's own audit and effective-dated history alongside it for who-changed-what detail.
This guide is for Workday report writers, HRIS analysts and integration developers who need a reliable, queryable history of worker data changes, for analytics, data quality checks or downstream systems.
Key takeaways
- RaaS is a data extraction method, not a change detector. The comparison logic lives outside Workday.
- Snapshot comparison only sees the state at each pull. Changes made and reversed between pulls are missed.
- Workday's audit trail records old value, new value, who made the change and when, but access is restricted and it is not built for bulk trend analysis.
- For effective-dated data, such as job and compensation history, query the history directly instead of relying on snapshots.
- Your change log becomes sensitive HR data. Secure it and set retention before you go live.
What is RaaS and why use it for change tracking?
Workday's integration training defines a web-service-enabled custom report as a Report-as-a-Service, or RaaS. You build a custom report as usual, then enable it as a web service in the report's advanced settings. The report can then be called from outside Workday by an authorized account and returns data your script or integration platform can parse.
That makes RaaS a good fit for scheduled snapshots. Pull the same report daily, store each result, and compare them. The key limitation: RaaS shows you the current state at the moment you call it. If a field changed on Tuesday morning and was changed back on Tuesday afternoon, a daily pull will never see it. For most analytics that is fine. For compliance questions, use Workday's audit data instead. If you are deciding between RaaS and other integration tools, our comparison of Workday EIB, connectors and Studio explains where each fits.
What does the Worker business object give you?
In Workday reporting, the Worker business object is the main source for employee data. A custom report built on Worker can reach a very wide set of fields: name and contact details, job profile, position, management chain, location, cost center, compensation, worker type and much more.
The catch is that many fields return the current value only. Some data is effective-dated, meaning Workday keeps past and future values with dates. Workday's documentation gives a simple example: a job profile change scheduled for a future date shows the old title until that date and the new one after. Other fields, especially many personal or descriptive attributes, are easier to track by building your own history through snapshots. Knowing which kind of field you are dealing with is the first design decision. Our explainer on how an HRIS works and who owns the data is a useful primer if you are new to this.
How do you set up a RaaS report for worker field tracking?
- Create the custom report. Use Worker as the data source and choose an advanced report type.
- Add a stable identifier. Include Employee ID or Worker ID so you can match records across snapshots. Names and emails change, so do not use them as keys.
- Add only the fields you need. For example: job profile, business title, supervisory organization, manager, location, cost center, worker status, pay grade. Fewer fields means smaller payloads and less sensitive data in your log.
- Decide on population filters. Active workers only, or include terminated workers so you can catch terminations and rehires?
- Test the report inside Workday. Check for blank values, multi-value fields (such as multiple positions) and odd formatting.
- Enable it as a web service in the report's advanced settings.
- Set up access. Use a dedicated integration account rather than a person's login, and grant it only the security domains needed for the fields in the report. Work with your Workday security admin; our guide to designing Workday security groups covers the principles.
How do you build the comparison logic?
The logic is simple. On each run, pull the current report, load the previous snapshot, and compare record by record and field by field. Write each difference to a change log.
A practical change log has these columns:
| Column | Purpose |
|---|---|
| Worker ID | Stable key to join with other data |
| Field name | Which attribute changed |
| Old value | Value in the previous snapshot |
| New value | Value in the current snapshot |
| Detected at | Timestamp of the comparison run |
| Change type | Updated, new worker, or missing worker |
A short script (Python is common) or an integration platform can do this. A few details catch teams out:
- Normalize values before comparing: trim spaces, standardize date formats and sort multi-value fields, or you will log false changes.
- Handle new and missing workers separately from field updates.
- Record "detected at", not "changed at". A snapshot cannot tell you the exact moment of change, only the window.
- Alert on failed pulls. A silent failure leaves a gap that later looks like a burst of changes.
A common mistake we see is starting with dozens of fields "just in case." Start with five to ten fields people actually ask about, prove the process, then expand.
How does Workday's native audit trail fit in?
Workday's documentation says every change to business data is recorded, and that each user-made change is logged with the old value, the new value, who submitted it and a timestamp. Auditors can view this history in reports but cannot change it, and access is limited to the Auditor security group. Workday positions this as support for data integrity controls such as Sarbanes-Oxley Section 404.
So the two methods answer different questions:
| Question | Best source |
|---|---|
| Who changed this record, and exactly when? | Workday audit history |
| How many manager changes happened per department last quarter? | RaaS snapshot change log |
| What was this worker's job profile on a past date? | Effective-dated history in a Worker report |
| Feed changes to a downstream system every night | RaaS snapshot or a delta integration |
Use audit history for investigations and compliance evidence. Use the snapshot log for trends, dashboards and integrations that need a simple list of changes.
How should you handle effective-dated fields?
For effective-dated data, such as job changes, compensation and many organization assignments, you can report the history directly through Worker-based reports, filtering by effective date range. This captures every change, including several within one snapshot window, and gives you the true effective date rather than the date you happened to notice.
Watch for two things. First, future-dated changes: a report "as of today" will not show a promotion effective next month, so decide whether you want as-of-today values or the latest entered values. Second, corrections and rescinds can alter history after the fact, which can make a past snapshot disagree with today's history report. Document which source wins.
What security and governance controls do you need?
A change tracking report sees sensitive data across the workforce, and the change log you build becomes a second copy of that history. Treat it with the same care as Workday itself:
- Grant the integration account read access to the required domains only.
- Store the change log encrypted, with access limited to named roles.
- Exclude fields you do not need, especially compensation and personal contact data.
- Set a retention period and delete older records on schedule.
- Log who queries the change log.
NIST's guide to computer security log management is a good reference for how to collect, store, protect and retire log data in a disciplined way. Having this tracking in place also makes routine reviews like a Workday HCM data audit and cleanup much faster.
What can you do with field-level change data?
- Data quality: catch values that changed to something odd, fields that flip back and forth, or bulk updates outside expected business cycles.
- Organization analytics: track restructuring, manager changes and span of control over time. Several manager changes in a short period can be a retention risk worth a check-in.
- Location and cost center accuracy: find workers whose records were not updated after a move.
- Pay equity reviews: with appropriate access controls, compensation history helps show whether gaps are narrowing or widening.
- Downstream sync: send only changed records to other systems instead of full files.
Feeding these into your regular reporting is easier when you already have a Workday reporting governance strategy that defines owners and naming standards.
FAQ
Does Workday keep a history of every field change?
According to Workday's documentation, changes to business data are recorded in an audit trail with old value, new value, user and timestamp, and some data is also effective-dated. Audit access is restricted to the Auditor security group, and it is not designed for bulk analytics, which is why many teams also build a RaaS snapshot log.
How often should I pull a RaaS snapshot?
Daily is the most common choice. It catches nearly all meaningful changes and keeps payloads manageable. Hourly pulls narrow the detection window but add load and storage. Weekly is enough for slow-moving analytics. If you need every intermediate change, use audit history or effective-dated reporting rather than more frequent snapshots.
Can RaaS tell me who made a change?
Not from a snapshot comparison alone, because the snapshot only shows current values. To see who made a change, use Workday's audit history or business process history, which record the person and time. Some teams join the two by looking up audit details only for changes the snapshot log flags.
What to do next
- List the five to ten worker fields stakeholders most often ask "when did this change?" about.
- Mark each as effective-dated or current-value only, and choose history reporting or snapshots accordingly.
- Build and test the RaaS report with a dedicated, least-privilege integration account.
- Agree storage, access and retention for the change log with HR, security and legal before the first run.
Sources
- Workday Education: Workday Integrations Overview (Report-as-a-Service)
- Workday Administrator Guide: Auditing
- NIST SP 800-92: Guide to Computer Security Log Management
Last reviewed: October 2026.

Comments
Post a Comment