We sat down with Steve Gould, Crown’s Data Engineering and System Integration Solutions Consultant, to explore where workforce systems really fall short and what organisations often miss when it comes to integration.
Most businesses don't start out with broken systems. Everything looks like it works on paper: HR keeps track of information about employees, scheduling tools handle shifts, payroll runs weekly or monthly and reports are made – there are known processes.
But if you look closely, the cracks are not in the systems themselves but in the space between them. As Steve explains, “I wouldn’t necessarily characterise it as something that’s broken. Systems integration is really just a way to keep a business process going in a different system.”
Understanding that distinction is important because most problems with the workforce aren't caused by software failures; they are failures in processes caused by systems that aren't connected.
In many organisations, each system does its job well enough in isolation.
HR platforms manage employee records, workforce management tools track time and attendance, payroll systems calculate pay and finance tools handle reporting.
On their own, each part appears functional, but the reality is that workforce management is not a set of isolated tasks. It is a continuous process that moves across systems every single day. New employees are onboarded in HR; their details need to flow into scheduling, their hours need to flow into payroll and their costs need to flow into finance.
When that continuity breaks, the organisation doesn’t immediately see it as a failure, and instead, it compensates. Someone exports a report, someone else re-enters the data, a manager checks the numbers and payroll double-checks calculations. Small manual steps begin to fill the gaps, and over time, that extra layer becomes the system.
The reality that most organisations face is not a single system that is failing. It is a landscape of systems that were never designed to fully work together. As Steve explains: “They may have several disparate applications.”
It is common to see organisations running platforms like SAP or Workday alongside specialist workforce management tools, yet each system has its own role, its own data structure and its own logic.
Workforce management often sits outside the core HR system, particularly in complex environments. That separation introduces friction because data has to move between systems, processes have to align and timings have to match. When they don’t, the organisation has to manage the gaps, and those gaps are where errors, delays and inefficiencies begin.
The cost of poor integration is rarely obvious at first, as it doesn’t appear as a single failure or outage. Instead, it shows up in daily work. Steve describes a common scenario: “You generate a report, then someone goes and keys those details in manually. How much money is that actually costing you?”
This is how many businesses operate. Data is exported from one system, passed to another team and then manually entered into another system. The process repeats daily, often across multiple workflows and every step introduces significant risk. Manual processes create errors because people make mistakes. Errors create rework, rework creates delays and delays impact payroll accuracy, compliance and decision-making.
Over time, the organisation absorbs these issues as "normal," but the cost compounds quickly:
None of these is caused by a single system failing, but rather the systems are not working together as part of a continuous process.
Many organisations assume that integration is already solved because most enterprise systems offer some form of integration or a standard connector; however, in practice, these often fall short. “They might include some sort of standardised solution, but it’s a one-size-fits-all approach,” says Steve.
Standard integrations are designed for predictable, uniform use cases, when in reality, workforce environments are anything but predictable. Shift patterns vary, pay rules are complex, the organisation grows through acquisitions, different sites operate in different ways, and then there are also legacy systems that remain in place.
Trying to force this complexity into a fixed integration model rarely works. Instead, organisations end up adapting their processes to fit the system, rather than the system supporting the process, and that is where inefficiency returns.
This is where the difference between software and consultancy becomes clear.
Crown’s approach is not to offer a rigid integration layer but to understand how an organisation actually operates and then design around that.
As Steve explains, "We have a specialist integration services team that develops a solution specifically customised for you, which means we start with the business process, not the technology.”
Critical process-related activity is evaluated upfront: How does employee onboarding work? How are shifts created and adjusted? How does payroll need to receive data? Where are the exceptions and edge cases?
From there, integrations are designed to support that flow – not just technically but also operationally. This is particularly important in complex, multi-site environments where no two organisations operate in the same way.
When integration is done properly, it is almost invisible. Data flows automatically between systems, processes continue without interruption and teams no longer need to duplicate effort or check the same information in multiple places.
As Steve puts it: “They maintain it in one place, and it is automatically maintained in the other place.” We understand that this simplicity is what most organisations are trying to achieve, and in practical terms, it means:
With proper integration, the organisation can move from managing systems to managing outcomes.
For many organisations, the first instinct is usually to add another tool to solve a problem, but more systems rarely solve the issue. In fact, they often just add another layer of complexity.
The real opportunity sits elsewhere, as stated by Steve: “It’s the economies that come from only having to do something once," and that is the main principle behind effective integration – do the work once and let the system carry it through the rest of the process.
When workforce systems are properly connected, the manual layer disappears, visibility improves, errors are reduced and decisions become faster and more reliable.
The systems themselves have not changed – the way they work together has – and that is where the real difference is made.
