HRIS Selection
Part of HR technology reviews
Deciding whether to reconfigure or replace an HR platform
Diagnose an HR platform gap, compare repair with replacement and decide what evidence is needed to protect records and handoffs.
Reconfigure an HR platform when a supported change in the current contracted service meets the required outcome with acceptable effort and risk. Investigate replacement when a critical outcome remains unsupported or repeated fixes leave the process fragile. The decision needs an observed gap and workable options, not frustration with one screen.
Define the gap
Describe the failed process outcome: for example, managers cannot tell whether an approved employment change reached payroll. Record who is affected, how often it occurs, its consequence and the evidence.
Before attributing the gap to the product, check settings, permissions, integrations, guidance and source data.
Ask the system owner or supplier for a remedy tied to the actual module, contract and configuration. Keep the proposed remedy separate from what has been demonstrated. A roadmap statement leaves the outcome unverified.
Compare the options
Option / Evidence needed
- Correct data or guidance
- Cause, owner and check of the resulting record
- Reconfigure
- Supported setting, effects on other workflows and maintenance owner
- Add a controlled handoff
- Steps, exception owner and recurring effort
- Replace
- Critical outcomes, transition scope, record retrieval and exit dependencies
Estimate one-off effort, recurring work, disruption and the consequence of failure for each workable option. An unpriced manual step is still work.
Give pay, access and required-record outcomes weight according to their consequences. Where pay may be affected, have a qualified payroll reviewer check the expected result; a successful transfer alone does not establish correct pay.
Before retiring the current service, identify the records it holds and how they will remain retrievable. Treat this as an exit condition, not a reason to retain an unsuitable platform indefinitely.
Check the preferred repair
For reconfiguration, define success before changing settings. Use suitably protected cases for an ordinary path, an exception and a correction.
Inspect each role’s task, the final record and any receiving system. Check other workflows the setting may affect. If the remedy adds a manual handoff, include its owner and ongoing effort in the option.
For replacement, establish the critical outcomes a new service must support and whether the organisation can carry out the transition. Check access, data retrieval, integration and support in the offer being considered; do not assume a general product capability is included in the proposed configuration.
For cloud services, clarify which responsibilities sit with the organisation and which with the provider. Record who would manage access, settings and recovery under each option.
Key Considerations for HR Platform Decisions in Australia
- Pay accuracy riskMust be verified by qualified payroll reviewer — successful transfer ≠ correct pay
- Cloud responsibility splitOrganisation manages access, settings; provider handles infrastructure — clarify under shared responsibility model
- Record retention requirementIdentify records held by current platform and ensure retrievability post-exit — treat as exit condition, not reason to retain
Make a conditional decision
Choose reconfiguration when the checked remedy meets the required outcome and its burden is acceptable. Proceed towards replacement when the current arrangement cannot meet a critical need and a viable transition has been established.
If a new service has not yet been assessed, the decision is to investigate replacement, not to claim that replacing the platform will solve the problem. Record the owner, evidence, remaining risks and the event that will reopen the decision.
