Before You Sign the Implementation SOW - The Pre-Implementation Diagnostic
The weeks between choosing an ERP and signing the implementation statement of work are the cheapest point in the entire program to prevent a bad start. A pre-implementation diagnostic settles scope, data, integrations, phasing, resourcing and go-live criteria before the partner's clock begins. This article describes what one covers, drawn from a fabricator's preparation phase after an IFS Cloud selection and a distributor's six-week diagnostic inside a Dynamics 365 program.
Why the gap matters
Implementation partners quote against assumptions. If the assumptions are still open when the SOW is signed, they close later as change orders, delays or a go-live that quietly moves. The diagnostic closes them while the client still holds the pen.
What a diagnostic settles
Scope boundary - What is in the first phase and, just as important, what is explicitly deferred. A written deferred-scope list with an executive approval process for additions is the single most effective control against scope creep.
Retained systems - Which existing tools stay through Phase 1, how each will integrate or be bridged manually, and who owns the bridge. CRM, CAD and product-data management, HR, expense and quoting tools are the usual candidates.
Data readiness - Items, vendors, customers, bills of material, routings, inventory, locations and opening balances, each with a named owner, a readiness measure and a weekly review the sponsor can see. Data is the most common reason a go-live moves.
Engineering and operational hand-offs - For manufacturers, a design-validation session with real CAD and PDM data before signing: metadata, BOM import, revision control. For distributors, pricing, rebate and branch structures. For regulated companies, the validation approach and audit-trail expectations.
Warehouse and shop-floor transactions - Handheld, tablet and scanner flows for pick, move, issue, receive, labor reporting and labels, confirmed by the vendor rather than assumed.
Integration and reporting strategy - Systems of record, interface inventory, monitoring and reconciliation, and a clear separation between Phase 1 reports and later dashboards. Dashboards are a distraction during a minimum viable product.
Phasing and resource plan - The partner's staffing by role and week set against the client's real availability: who the business-process owners are, how many hours they can give, and where the gaps get filled.
Commercial assumptions - License counts and user types, device counts, optional modules, price protection, named roles, replacement rules, on-site cadence and escalation paths, all reconciled before the order form and SOW are signed.
Go-live criteria -
What must be true before the company moves off its current system. Written down, agreed by the steering committee, and used to make the go-live decision rather than the calendar.
How it runs
A diagnostic takes four to seven weeks depending on the size of the program. At the distributor it ran as a seven-week program with working sessions on functional scope validation, reporting and integration strategy, and the project plan, phasing and resource model, closing with a two-day on-site leadership readout that set the direction for the next SOW. At the fabricator it ran as a pre-implementation preparation phase immediately after contract signature, finishing well under its hours budget because scope was cut once the team had what it needed.
Frequently asked questions
What is the difference between a diagnostic and a selection? Selection chooses the platform and partner. The diagnostic prepares the organization and the contract for the implementation that follows. It applies whether the platform was just chosen or has been in place for years.
Who leads it? Someone on the client's side of the table who has run implementations of this size before. The partner will contribute, but the partner should not define the client's scope, data readiness or go-live criteria.
What does ERP implementation project management look like after the diagnostic? The diagnostic produces the plan, the RAID log, the governance and the readiness tracker that client-side project management then runs. Most clients keep an independent program leader through Phase 1 and take over from there.
How much of our team's time does it take? Business-process owners four to six hours a week for the working sessions; IT six to eight; the sponsor an hour a week plus the readout.
If your program looks like this, talk to John about your ERP program.
