Insights, minus the fluff.

A practical guide to using Workday Document Builders and sub documents in field overrides to output parent and child data as a nested XML structure, rather than flattening it into single value calculated fields. It covers the two main use cases (keeping multi-instance entries separate, and bringing in objects a connector does not output natively, such as payment elections), the Grid enablement prerequisite, how the pieces fit together, and what to watch for.

Where Workday integration development is heading: Orchestrate, browser-based Studio Builder, and a worked example loading daily RBA exchange rates into Workday.

Field notes from five years of connecting Workday to six Australian and New Zealand payroll platforms: ADP Payforce, ADP Lyric, Jade Star, Employment Hero, Micropay and Chris21. Each section covers what the product is and what the integration was like, from Payforce's handling of mid-period pay changes to Chris21's blank-means-blank behaviour. The common thread is that vendor-side people shaped the outcome as much as the product did.

Most go-lives get all the way through stage gates without anyone properly deciding who owns the product once the project team leaves. Vendor support fills the gap by default, but answering tickets isn't the same as enabling a team to own a process. This piece walks through the ownership questions that need deliberate answers, especially across Workday's many functional domain touchpoints, and makes the case for layering a RACI on top of future state process maps, including the Change Management and Cyber stakeholders that get pulled in more than people expect.

Most "agent-ready" claims focus on the model, but the real requirement is architectural: clean interfaces, well-labelled and consistent data, and goals specific enough that an agent can't find a technically valid shortcut to the wrong outcome. Drawing on lessons from building iDeeDee and a real 2026 incident where an OpenAI model gamed its own benchmark by breaching Hugging Face, this piece looks at what actually makes an enterprise system ready for agents, and why Workday's strict data model and ASOR already put it ahead of most platforms on this front.

Ten practical Workday security checks that go beyond the standard implementation checklist, covering everything from piping the User Activity Report into your SIEM, to IP restricting admin and API access, to catching toxic approval flow combinations before they become a real problem. None of them are complicated individually, but they're the kind of thing that gets set once and never revisited until an audit or incident forces the question.

Workday's strict data model gets criticised as a limitation, but it's one of the platform's biggest architectural strengths. This piece looks at why that rigidity pays off, from stress-free release cycles to business logic your own team can actually support, and where delivered connectors owe their reliability to a data model with fewer unknowns to account for.

A dashboard that's already sitting in your delivered content library, waiting to save you from notification fatigue.

A practical five-phase guide to building integrations: align the right people, define the exchange, agree on meaning, test real exceptions, and plan the cutover.

If you've ever tried to have a conversation with someone who's learning your language, you already understand integrations. You just didn't know it.

Inheriting a portfolio of nearly 100 integrations taught me why long-term ownership and native architecture judgement matter before a build begins.

Why a technically successful integration can still leave a business process fragmented, and the six questions that reveal what is missing.

The build cost is visible. The maintenance cost is quieter; and both need to be pressure-tested before a business case is signed off.

Santinon Consulting has partnered with Considered Group to bring clients a wider network of committed specialist expertise, without sacrificing long-term ownership.