Executive summary
No provider chooses a fragmented systems environment. It is built one reasonable decision at a time. A program is funded and needs a client system. Payroll changes and brings a time capture tool. A new regulator requires evidence and a compliance register appears. Each decision is defensible and the accumulated result is not.
The cost of that accumulation is real but rarely appears in any budget line, because it is distributed across every team in small increments. It shows up as a service manager working late on reconciliation, an intake worker asking questions the organisation already knows the answers to, and an executive who cannot answer a straightforward question without a week's notice.
This paper describes the three costs, explains why integration projects often fail to remove them, and sets out a consolidation sequence that can be run without interrupting service delivery.
1. How the environment is built
Fragmentation in this sector is a consequence of funding structure. Money arrives per program, with its own conditions, reporting requirements and timeframe, and systems get selected within that boundary. Nobody is responsible for the whole, so nobody notices the whole becoming unmanageable.
2. The three costs
- Duplication. The same fact entered more than once. A client's address, a worker's qualification, a delivered service. Each re entry is time, and time in this sector is the scarcest input.
- Divergence. Once a fact exists in two places it will eventually differ. When it does, staff learn to distrust the systems and begin keeping their own records, which multiplies the problem.
- Blindness. Questions that span systems become projects. How many people do we serve. What is our real cost per service hour. Which program is under delivering. These take days instead of seconds.
Blindness is the most expensive of the three because it changes decisions. A provider that cannot see a problem does not manage it, and by the time it becomes visible in the financial statements the options are narrower.
3. Why integration underdelivers
Synchronisation is not consolidation. Copying data between systems keeps them aligned but preserves every workflow boundary. The worker still switches applications, and the reporting still requires assembly.
Integrations are fragile and undocumented. They are commonly built once, by a person who leaves, and break silently when either system updates.
The awkward data never maps. Custom fields, program specific status codes and local conventions are exactly the information that matters, and exactly what integrations tend to drop.
4. Measuring the cost
The business case does not require precision. It requires a defensible number that the board recognises.
Count the re entries. Walk one client from referral to invoice and one worker from recruitment to first shift. Count every place a fact is typed a second time.
Time the questions. Pick four cross system questions an executive should be able to answer and record how long each takes to answer accurately.
Ask where the shadow spreadsheets are. Every spreadsheet maintained alongside a system is a documented gap, and staff will tell you about them if asked without blame.
5. A consolidation sequence
Start with people, not programs. Establish one authoritative client record and one authoritative worker record. Almost every other consolidation depends on these two.
Then connect service delivery to funding. Attribution at the point of capture removes the largest single source of month end work.
Then compliance evidence. Credential, incident and policy evidence attached to the people and services already consolidated.
Retire deliberately. A system that is not switched off is still being maintained. Set a decommission date for each system at the point of migration, and hold it.
6. Limitations
This paper does not quantify savings for any organisation and does not compare named products. Alvacomm operates the Konetic One platform and has a commercial interest in this subject, which readers should weigh when considering the recommendations.
References
- 1.Australian Charities and Not-for-profits Commission, Australian Charities Report, ACNC, Australian Government.
- 2.Department of Social Services, Data Exchange, program reporting and the SCORE outcomes framework.
- 3.Australian Institute of Health and Welfare, Health workforce, web report, Australian Government.
- 4.Australian Charities and Not-for-profits Commission, Governance Standards for registered charities.
About the publisher
Alvacomm Pty Ltd, ABN 61 627 262 873, is an Australian technology and cybersecurity organisation. Konetic One is a platform and service operated by Alvacomm.
This paper is published under the Alvacomm name and is general in nature. It is not legal, financial or clinical advice.