# Infor M3 Implementation Statement of Work Template

> Source: https://netray.co/tools/m3-implementation-statement-of-work-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Starter statement of work for an M3 implementation or enhancement project with scope, deliverables, assumptions and acceptance.

## Category

erp-migration

## Erp

Infor M3

## Audience

- M3 consultant
- Project manager
- Procurement

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Customer

**Key:** customer

**Type:** text

**Default:** Acme Precision Ltd

#### Service provider

**Key:** supplier

**Type:** text

**Default:** Example Consulting Partner

#### Project name

**Key:** project

**Type:** text

**Default:** M3 Phase 1: Order to Cash and Inventory

#### Planned start

**Key:** start

**Type:** date

**Default:** 2027-01-11

#### Planned go-live

**Key:** end

**Type:** date

**Default:** 2027-06-14

#### Commercial model

**Key:** model

**Type:** select

**Options:**

- Fixed price
- Time and materials
- Fixed price with change control
- Capped time and materials

**Default:** Fixed price with change control

#### In scope

**Key:** scope

**Type:** textarea

**Default:** Customer order, delivery, invoicing, inventory, warehouse, item and customer master data, two facilities, five interfaces, 20 reports.

#### Out of scope

**Key:** out_scope

**Type:** textarea

**Default:** Manufacturing execution, HR and payroll, historical transaction migration beyond open items, hardware procurement.

#### Assumptions

**Key:** assumptions

**Type:** textarea

**Default:** Customer provides subject matter experts for workshops, test data and UAT. Environments are provisioned on time. Scope changes follow change control.

**Blocks:**

#### Parties and project

**Body:** Customer: {{customer}}
Service provider: {{supplier}}
Project: {{project}}
Planned start: {{start}}
Planned go-live: {{end}}
Commercial model: {{model}}

#### In scope

**Body:** {{scope}}

#### Out of scope

**Body:** {{out_scope}}

#### Deliverables and acceptance

**Table:**

**Columns:**

- Deliverable
- Acceptance criteria
- Due
- Accepted by

**Rows:**

**0:** Solution design document

**1:** Reviewed and signed by process owners

**0:** Configured test environment

**1:** Smoke tests passed

**0:** Data conversion, final mock

**1:** Reconciled within agreed tolerance

**0:** UAT completion

**1:** No open blockers, majors agreed

**0:** Go-live

**1:** Go or no-go criteria met

#### Milestones and payments

**Table:**

**Columns:**

- Milestone
- Date
- Payment trigger
- Amount

**Rows:**

**0:** Kick-off

**0:** Design sign-off

**0:** UAT sign-off

**0:** Go-live

#### Assumptions

**Body:** {{assumptions}}

#### Change control

**Body:** Any change to scope, schedule or price is requested in writing, assessed for effort and impact, and approved by both parties before work starts.

#### Signatures

**Signatures:**

- Customer sponsor
- Service provider director
- Customer project manager
- Service provider project manager

**Notes:** This is a starting point, not legal advice. Have your legal counsel review it, and align it with the master services agreement that governs your relationship.

## Content

**Intro:** A good statement of work keeps an M3 project from turning into an argument. This template gives you a balanced starting structure for scope, deliverables, assumptions, acceptance and change control.

**Sections:**

#### How to use the template

**Body:** Fill in the parties, project name, dates and commercial model. Write the in-scope list in terms of business processes, facilities and interfaces rather than software menus. State what is out of scope just as clearly. Complete the deliverables table with acceptance criteria that can be tested. Link milestones to payments in a way both parties accept. Export to Word and send to legal and procurement for review.

**Bullets:**

- Count interfaces, reports and facilities explicitly
- State who provides data, environments and test resources
- Include a clear definition of done for each deliverable
- Keep a short, written change control process

#### Scope clarity for M3

**Body:** M3 projects commonly dispute the same items: number of custom reports, number of interfaces, depth of data conversion, level of testing, training and hypercare. Put a number on each. Say whether configuration of multiple companies, divisions, facilities and warehouses is included, and how many. Say whether the provider or the customer runs the UAT. If the project uses cloud tenants, say who provisions and who pays for non-production environments.

#### Commercial models

**Body:** Fixed price suits a well defined scope with a completed fit-gap. Time and materials suits discovery or uncertain scope, preferably with a cap and regular forecasts. A hybrid is common: fixed price for design, time and materials for build until requirements stabilize. Whatever the model, the acceptance criteria and change control process decide whether the arrangement works in practice.

#### Common mistakes

**Body:** Vague scope statements such as 'all standard processes' lead to disputes. Missing customer obligations cause delay claims. Acceptance based on opinion rather than criteria delays payments. Another mistake is leaving data quality to the provider alone, when the customer owns the data and must cleanse it. State these responsibilities directly.

**Cta:** If you need a second opinion on your M3 scope before signing, Netray partners can review the draft and point out gaps in assumptions and acceptance.

**Faq:**

#### What is the difference between an SOW and a contract?

**Answer:** The contract or master services agreement sets legal terms. The statement of work defines the specific project: scope, deliverables, timeline, price and acceptance. Many organizations use a master agreement with a separate SOW for each project phase.

#### Should the SOW name the people?

**Answer:** It helps to name key roles such as project manager and solution architect, and to include a clause about replacement. Naming every consultant is rare. Focus on roles, responsibilities and the minimum experience required.

#### How do I handle change requests?

**Answer:** Use a written change request that describes the change, effort, cost, schedule impact and risks, approved by both sponsors. Work on the change should not start until approval. Keep a log so cumulative changes are visible at steering meetings.

#### Is this template legally binding?

**Answer:** Only if you adapt it, add the legal terms of your agreement and both parties sign. The text is a general starting point and not legal advice. Always involve your legal counsel before signing any statement of work.

## Search terms

infor m3 statement of work template, m3 implementation sow, erp statement of work template, m3 consulting sow, m3 project scope document, erp implementation sow template word

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json