The first 90 days after HRIS partner selection

Selecting an implementation partner is a milestone, not the start of a self-running programme. The first 90 days should turn the proposal and selection decision into a workable delivery system.

The exact sequence depends on the contract and timetable, but these activities are useful in most programmes.

Days 1–30: mobilise and make the work visible

Confirm the sponsor, programme lead, stream owners and decision-makers. Agree meeting cadence, escalation thresholds, document controls and the decision log. Review the statement of work line by line with the delivery team.

Identify the assumptions that affect price, schedule or scope: client resource availability, data condition, integration access, configuration decisions, third-party dependencies and sign-off timing. Assign an owner and validation date to each.

Days 31–60: test readiness and dependencies

Assess the state of the data, process documentation, integrations, security roles and environments. Identify where decisions are overdue or where different groups hold conflicting views.

Create an initial view of change impacts, affected roles and training needs. Do not wait for configuration to finish before asking who will need to work differently. Confirm how business representatives will contribute alongside their day jobs.

Days 61–90: agree the delivery baseline

Bring scope, workplan, resources, dependencies, risks and acceptance criteria into one integrated baseline. Confirm how changes will be assessed and priced. Make the plan realistic about the client decisions and approvals it requires.

These stages overlap; they are not a rigid checklist. The practical test is whether leaders can see what must happen next, who owns it, what is at risk and what decision is needed.

Early clarity protects the working relationship. If a proposal assumption proves wrong, raise it while there is time to respond. If a dependency is outside the partner’s control, make its owner and impact visible.

A well-run first 90 days creates a foundation for delivery: one shared plan, clear accountability and an honest view of readiness. That is the point at which the implementation can move from selection into controlled execution.