A late ERP project rarely needs more people everywhere. It needs clear ownership at the point where decisions, data, testing, or cutover work has stopped moving. Find that constraint first. Then add a specialist who can close it and transfer the work back to the core team.
Reviewed August 3, 2026.
Start with the blocked deliverable
Do not open a broad requisition for an ERP consultant because the schedule is red. Name the deliverable that is late, the decision that is unresolved, and the person who owns acceptance. A useful recovery brief might say:
- Complete the finance design decisions needed to start configuration.
- Reconcile customer and supplier data before the next migration cycle.
- Turn undocumented integrations into an owned build and test plan.
- Reduce the open critical defects that prevent user acceptance testing.
- Build a cutover plan with named owners, dependencies, and rollback decisions.
Each problem calls for different evidence. A functional lead should be able to explain design decisions and business-process tradeoffs. A data lead should show reconciliation, exception handling, and business signoff. A test lead should show traceability from requirement to defect and retest.
Diagnose the five common staffing gaps
| Where work is stuck | Likely ownership gap | Evidence to request |
|---|---|---|
| Design decisions remain open | Functional or solution lead | Decision log, fit-to-standard workshop output, process design, and escalation examples |
| Migration cycles keep failing | Data conversion lead | Source profiling, mappings, reconciliation rules, exception handling, and business approval |
| Integrations lack owners | Integration architect or developer | Interface inventory, error handling, security, test evidence, and production support model |
| Testing produces defects but not decisions | Test lead with functional authority | Coverage, triage rules, severity definitions, retest process, and exit criteria |
| Cutover tasks are incomplete | Cutover or release lead | Dependency plan, rehearsals, checkpoints, go or no-go criteria, and rollback ownership |
The title is secondary. Ask who can decide, who can execute, and who can approve the result. If those are three different people, put all three in the recovery plan.
Separate capacity from authority
A project can have enough hands and still lack the person authorized to resolve cross-functional choices. Adding developers will not fix an undecided chart of accounts. Adding testers will not fix unclear acceptance criteria.
Write the temporary specialist's decision rights before the search begins. Can the person recommend a solution, approve it, or only implement it? Who resolves a disagreement between a business owner and an implementation partner? What must be documented before the specialist leaves?
Use a short recovery assessment
Before interviewing, assemble a small evidence packet. It should include the current schedule, open decisions, defect or issue summary, architecture or process documents, upcoming milestone, and the internal owner. Candidates do not need confidential production data to explain how they would structure the work.
Ask the candidate to identify:
- The facts they need before changing the plan.
- The first deliverable they would stabilize.
- The dependencies that could move the critical path.
- The decisions that require an executive or business owner.
- The artifacts and knowledge they would leave with the permanent team.
A credible answer will contain conditions and tradeoffs. Be cautious when a candidate promises to rescue the project without asking about scope, ownership, data, environments, or acceptance.
Match the specialist to the implementation phase
A recovery search should reflect the phase the project is actually in, not the phase shown on an old plan. A team may call the work testing while functional design is still changing. It may call the work deployment while data reconciliation is incomplete.
Use Crosscheck's guide to ERP staffing by implementation phase to map the blocked deliverable to the right functional, technical, data, testing, change, or cutover owner. Platform experience still matters, but it should sit beside phase-specific proof.
Choose contract or direct hire deliberately
A contractor can fit a bounded recovery assignment: close a design backlog, lead a migration cycle, stabilize testing, or prepare cutover. A permanent employee is usually a better fit when the company needs continuing platform ownership, roadmap decisions, and support after stabilization.
Define the end of the assignment. List the deliverables, acceptance owner, handoff materials, and support period. That makes the engagement easier to screen and prevents an emergency role from becoming an indefinite dependency.
Interview for recovery evidence
Ask for one project that was already behind when the candidate joined. Then follow the work from diagnosis through handoff:
- What was late, and how did the candidate verify the cause?
- Which decision changed the plan?
- What did the candidate personally own?
- Which artifact showed that the constraint had been removed?
- What remained unresolved at the end?
Crosscheck recruiting guidance: Bennett starts recovery searches with the blocked deliverable, required platform evidence, and interview proof. That produces a narrower search than a generic ERP consultant title and gives the client a shared acceptance standard.
Review Crosscheck's ERP recruiting practice, compare SAP S/4HANA consultant hiring criteria, or send the stalled deliverable and recovery brief.