Organizations that grow by acquisition tend to add operations faster than they add the ability to see across them. Each acquisition is absorbed under deadline pressure, consolidated onto shared systems, and declared complete. What rarely keeps pace is the workforce view: the single, trustworthy picture of who works where, at what cost, and with what turnover across the combined organization. The systems hold the data. The capacity to read it as one workforce lags behind, sometimes for years.
What follows is a physician group whose platform reflected the combined organization on paper while its leadership was steering a workforce of several thousand people without a number it fully trusted.
A multi-specialty physician group that grew the way many do, by acquiring practices. Each acquisition brought its own clinics, its own staff, and its own way of doing things. What had been a handful of locations became dozens of cost centers spread across several legal entities, all eventually consolidated onto one UKG Ready platform but never truly unified beneath it.
Finance inherited a workforce it could not see clearly. The platform held the data, but pulling a clean view of headcount or turnover across the combined organization meant exporting, reconciling, and hoping the entities lined up. The result was capable people producing numbers they themselves qualified rather than trusted.
PROFILE AT A GLANCE
The assessment expected to find one workforce-reporting process. It found two. Finance and operations were answering many of the same workforce questions through entirely separate reporting paths, each unaware of how the other arrived at its numbers. Somewhere in the organization, the operations side had built a reporting pipeline that fed certain workforce numbers into a reporting tool. Finance had never been made a consumer of it, and had built its own manual process from scratch.
Neither side was wrong. Both were producing real numbers. But the organization had one workforce and two versions of the truth, and no one owned the work of reconciling them.
Finance believed no workforce data flowed into reporting at all, because none flowed to finance. Operations had been running reports for some time. Each side was certain of a different reality, and both were right about their own half of an organization that had never been stitched together.
That reframed the engagement. The risk was not a missing report. It was that capital, staffing, and acquisition decisions were resting on workforce numbers two halves of the organization could not agree on. The acquisitions had been consolidated into the system long before they had been consolidated into a shared understanding of the workforce, and the gap between the two had quietly become a decision-quality problem.
The review combined stakeholder interviews across finance and operations, workforce-management process reviews, UKG Ready configuration and entity-structure analysis, and validation of how reporting was actually produced and consumed. The objective was not simply to find technical gaps. It was to understand where the organization was relying on manual effort and parallel processes to answer questions the platform should have answered once, for everyone.
That distinction is what surfaced the finding. Looking only at finance would have confirmed finance’s belief that no data flowed. Looking only at operations would have missed that finance was excluded. Comparing how each part of the business consumed workforce information against how the organization actually produced it was the only lens that revealed the split.
Once the split was understood, the patterns arranged themselves into a clear causal chain. One root condition, never addressed, produced the symptoms leadership actually felt.
Putting the two parallel efforts side by side made the cost legible. The organization was spending skilled finance capacity rebuilding workforce reports every cycle while an operations pipeline produced an overlapping view no one had connected to it. Across a year, that is a substantial share of experienced finance time spent on assembly and reconciliation rather than on the judgment the work was meant to support.
This is not a dollar figure, and it was never meant to be one. It is a measure of how much effort an organization can spend answering the same question twice without realizing it is doing so.
WHAT THE SPLIT WAS COSTING
The data already existed. The work was to unify the structure it sat in and surface it where the whole organization could share one view.
The organization’s entities were brought onto one common structure, so that a number means the same thing whichever part of the business produces it. The workforce data then flowed into a single governed reporting layer that finance and operations share, with access set so each consumer sees what they should and sensitive workforce detail stays where it belongs. The manual reconciliation stopped being necessary because there was finally one source to reconcile to.
The order mattered more than any single step. A shared reporting layer built on the old, inconsistent foundation would only have produced a cleaner-looking version of the same disagreement. Settling the foundation first is what made the single view trustworthy rather than merely shared, and it is the difference between two halves of an organization seeing the same screen and actually believing the same number. The analyst’s time moved from assembling figures to interpreting them, which is the work the role was created for.
| Workforce KPI | Current State | Future State |
|---|---|---|
| Headcount by entity & specialty | Reconciled by hand each cycle | One governed view across the group |
| Turnover rate | Defined differently by source | One definition, trended over time |
| Labor cost per provider FTE | Assembled per request | Continuous, by entity and specialty |
| Open roles vs. staffing plan | Tracked in side spreadsheets | Live, tied to the plan it serves |
| FTE vs. budget | Days old when it lands | Current, governed, board-ready |
| Reporting access & control | Email exports to individuals | Role-based, sensitive data protected |
The governed reporting layer is the inflection point. When a regional controller can see open roles against the staffing plan for her clinics, she fills the right ones first. When the CFO trusts the FTE-versus-budget number, she stops commissioning a rebuild every time the board asks. Workforce management stops being a backward-looking record and becomes the instrument leadership steers by.
The return concentrated in three places, and only one of them is a number.
An acquisition is consolidated into the system the day the data moves over. It is consolidated into the organization only when everyone is finally looking at the same workforce and believing the same number.
A group that has grown by acquisition was not buying visibility it lacked the data for. The data was already there. It was building an organization that could see itself whole again, make decisions on one set of numbers, and absorb the next acquisition without splitting into parts that each see only their own.