It is the Thursday before go-live. The data migration consultant has slept four hours a night for nine days. The finance functional lead is also covering inventory because a colleague left in the build phase. The client calls at ten at night to ask about a failed invoice run, and nobody on the partner's side is surprised, or rested.
Most partners know this scene. The project may finish on time, yet two people resign within a month. This guide helps a delivery or programme head plan staffing so the team arrives at go-live able to support it.
Why the load is uneven by design
An ERP implementation is not a steady stream of work. Blueprint needs functional consultants who can listen and write. Build needs configuration and development hands. Testing needs many people for a short time, including client users. Cutover needs nearly everyone at once, often through a weekend. Hypercare needs a smaller group on call.
If you staff the project at a flat level, either you pay for idle people in some weeks or you overload the same people at the end. Most enterprise software teams face this and solve it with planning, not heroics.
Plan staffing phase by phase
- 1
Map roles to phases at kick-off
Make a simple sheet with phases across the top and roles down the side. Mark who is full time, part time or on call in each phase. Share it with the project manager and the people named.
- 2
Name a deputy for each critical role
For data migration, the finance lead and the integration owner, name one person who has sat in the meetings and can take over for a week. Cross-cover is a plan, not a favour.
- 3
Fix the cutover roster early
Draft shifts for the cutover fortnight before the date is final. Include weekly offs, handover times and who is reachable at night. Adjust when the date moves.
- 4
Hold a load review every two weeks
List hours worked, offs taken and open issues per person. Ask each consultant one question: what would you drop if you could? Act on the answers.
- 5
Plan the landing after go-live
Agree in advance a rest day or short break for those who carried cutover, and a hypercare rota that does not repeat the same names every night.
Early signs that a team is running hot
- Commits and emails at hours that are normal for nobody, repeated for more than a week.
- A consultant who used to challenge requirements now agrees to everything.
- Weekly offs quietly dropped from the timesheet.
- One person named as owner of two modules for 'just this phase'.
- Small errors in configuration notes from people who were previously careful.
- Questions about leave or a sudden interest in other roles.
Staffing choices that ease the pressure
Decide early which work needs a permanent employee and which can be handled by outside specialists under a written scope. Where you engage outside consultants, put the scope, system access and exit handover in writing. The same applies to the data and network access of anyone who leaves mid-project. Your own qualified legal adviser should check those agreements.
Hiring ahead of need also helps. A new functional consultant needs weeks to learn a client's process, so a joiner arriving at the start of testing cannot lift cutover. Our workforce planning work gives partners a rolling view of which projects will need whom, quarter by quarter. For hiring itself, read how to test process knowledge when hiring ERP consultants.
Talk to the client about people, too
Burnout is partly a client management problem. Ask the client to name their own key users early, with time released from their daily work. When business users are missing from testing, the partner team fills the gap by working nights. Put the client's commitments in the project charter and review them at every steering meeting.
Be open about what a cutover weekend needs. A client who sees the roster understands why a request for a late change costs a rested team. Most clients accept a clear trade-off when it is shown on one page.
A staffing and load sheet to adapt
Project, client type, modules in scope, planned go-live window, project manager.
Phase table: blueprint, build, test, cutover, hypercare. Roles needed and level of involvement in each.
Critical roles with a named deputy: data migration, finance, supply chain, integrations, basis or infrastructure.
Cutover roster: dates, shifts, owner per shift, escalation contact, rest days after.
Fortnightly load check: hours, offs taken, open issues, one concern per person.
Change log: date moves, scope additions, extra people requested and the decision.
Hypercare rota: who is on call each day, handover time, review date to reduce cover.After go-live, protect the people who carried it
A team that has just finished a hard cutover is most likely to look around. Thank them in a specific way, give the promised rest, and talk about their next assignment within weeks. The question of what happens next is covered in keeping consultants after go-live. Without a next step, good people read silence as a message.
Careers matter here too. A consultant who sees a route from functional lead to solution architect is more likely to accept a hard project. See career paths in an implementation firm for ways to lay that out.
