HRIS Implementation Readiness Pack
What to have signed before anyone configures anything.
What’s inside
What you’re getting.
- A data audit checklist, clean before kickoff
- The decision docket: what has to be decided, and by whom
- An ownership map for the recurring work after go-live
- Manager-hierarchy and comp checks that catch the usual gaps
- Sign-off lines, because readiness is a decision rather than a feeling
Guide PDF + the three artifacts in editable Word
Email me the toolkit
The data migration guide as a PDF, plus the three readiness artifacts in Word.
One email, with the file attached. No sequence.
When you need this
Before kickoff, and before anyone on the vendor side configures anything. A migration planned as a four-week import turns into a configuration project in week three, when the team discovers that approvals and permissions do not come across with the records. The three artifacts in this pack sort that out first, and none of them needs the vendor.
Inside the pack
- A data audit checklist, clean before kickoff. One record per person, legal names that match tax documents, a current manager for everyone, comp with effective dates, balances and elections reconciled to the last register. The guide beside it sorts everything into what moves as data, what has to be rebuilt and what stays behind, with the load order from legal entities down to payroll history.
- The decision docket. What has to be decided, and by whom, before configuration starts: the permission model, the approval chains, which workflows survive and which reports the board pack needs.
- An ownership map for the recurring work after go-live. Who owns the request queue and the monthly report once the implementation team hands over.
- Manager-hierarchy and comp checks that catch the usual gaps. Effective-dated compensation history, people with nothing to report to, and the exceptions a random sample never finds.
- Sign-off lines, because readiness is a decision rather than a feeling.
How to use it
- Sort before you export. Three buckets decide a migration, and sorting them after the export is how a data project grows a configuration project inside it.
- Work the docket with the people who will live with the answers. The permission model deserves the most time, because the old one grew by accident and an AI layer is about to sit on top of it.
- Name the owners for month four now. Platform implementation teams hand over at go-live by design.
- Spot check by exception. One employee with a mid-year comp change, one in a second state, one on leave, one rehired, one part-time with a non-standard schedule.
- Sign the three artifacts. Then kickoff.
One thing to get right
Cut year-to-date figures at the cutover boundary and nowhere else. A figure taken from the wrong date loads without complaint and fails at the tax cap or at the W-2.
Stop being the only one who knows how it works.
Bring your setup and whatever broke this week. In 20 minutes you’ll know what you need and whether we fit.