Reference
What is HCM implementation readiness?
The short answer
Implementation readiness is the preparation done before a contract is signed: auditing source data, deciding which of your own policies are load-bearing and which are merely old, naming an internal owner with authority to decide, and sequencing the cutover so at least two full parallel payroll cycles survive the schedule. It is the highest-leverage investment available to a buyer and is almost entirely absent from the standard selection process, which ends at signature.
Why the standard process stops too early
Selection processes are built to answer which product. They conclude at signature, at which point attention shifts to the vendor’s implementation plan — a plan built on assumptions about your data and your decision-making that nobody has tested.
The gap between those assumptions and reality is where mid-market implementations lose their schedule. Not in the software, and rarely in the vendor’s competence. In the discovery that should have happened two months earlier.
Audit the data before committing to a timeline
Every implementation timeline assumes clean source data. Nobody has clean source data. Duplicate employee records, terminated staff still marked active, inconsistent job codes, historical pay elements no one can explain, PTO balances living in a spreadsheet on one person’s laptop.
Discovering this in week six of a twelve-week plan is how twelve-week plans become nine-month plans. Discovering it before the contract changes both the plan and the price, and it is a few days of work by someone who can read a data export.
Decide which of your policies are real
Every suite has a set of things it does natively and a set of things it can be made to do. The second carries cost forever — upgrade friction, brittle integrations, and a configuration only one consultant understands.
Most of what pushes you across that line is policy nobody would defend if asked to justify it. An accrual rule from 2009. A four-step approval chain that has never rejected anything. Auditing your own rules before configuring anything is the single highest-leverage move available, and it is free.
Name one owner who can decide
An implementation needs one person inside the business with authority to settle a question and calendar space to settle it this week. Not a committee, and not a coordinator relaying questions to a committee. Where that role is vacant or nominal, decisions queue, the vendor’s timeline slips, and every slip costs money on both sides of the contract.
Protect the parallel payroll
Running old and new payrolls side by side for at least two full cycles — reconciled to the cent, including taxes, garnishments and every deduction — is the only reliable proof the configuration is correct. It is also the first thing sacrificed when the calendar tightens.
Decide in advance that it is not negotiable, and put the cycle count in the contract. A go-live without a clean parallel is a bet that settles on the first live run, in front of every employee.
Plan the change, do not announce it
Managers and employees frequently meet a new system through a launch email and a link. Adoption stalls, shadow spreadsheets survive, and the reporting the platform was bought for gets built on data nobody is entering properly. Training, communication and a genuine retirement of the old process are part of the project rather than a nice-to-have at the end of it.
| Before signature | What it prevents |
|---|---|
| Source data audit | A timeline built on assumptions that fail in week six |
| Policy review | Configuration turning into permanent customization |
| Named internal owner | Decisions queuing behind a committee |
| Parallel cycles fixed in contract | A go-live proven only by the first live run |
| Change and training plan | Shadow spreadsheets and unusable reporting |
| Delivery team named in contract | A sales team you never see again |
Common questions
How long does readiness work take?
Will the vendor not do this for us?
How long should the whole implementation take?
What if we have already signed?
Where this sits
This page supports HCM | Workforce Management Advisory Services — the practice that does this work.
