ERP Pilot
Free template

ERP Requirements Template: Free Word Document and Excel Checklist

A vendor-neutral template for your ERP requirements: a Word document with guidance and an Excel checklist that scores vendor responses for you.

Free. No spam. Your details go to partners, vendors or selection consultants only if you tick the box above.

  • Word template, 12 pages: 10 chapters from company profile to scoring weights, with examples
  • Excel requirements checklist: 61 example requirements, Must/Should/Could, scoring for up to 5 vendors
  • Compliance built in: US GAAP, IFRS, SOX, sales tax, e-invoicing, GDPR and CCPA

What is an ERP requirements document?

An ERP requirements document states what your company needs from a new ERP system. It captures processes, volumes, compliance rules, technical constraints and the rules of the selection in one place. Every vendor gets the same basis, which is what makes their proposals comparable in the first place.

You write it as the buyer. It describes what you need, never how a particular product does it. Vendors and implementation partners answer the how, first in their proposal and, after the decision, in the solution design. How the document fits into the whole process, from longlist to signed contract, is covered in our guide to the ERP selection process.

What is in the template?

Two files that belong together. The Word document carries context and scope, the Excel checklist the detailed requirements and the scoring. Every requirement has the same ID in both, for example SA-03 for the committed delivery date in sales.

Chapter 2

Company and current situation

Profile, current system landscape, why you are changing now

Chapter 3

Goals and scope

Measurable goals with today and target values, clear boundaries

Chapter 4

Volumes

Users, transactions, entities and growth, so vendors can size the proposal

Chapter 5

Process requirements

Sales, purchasing, warehouse, manufacturing, services, finance, master data

Chapter 6

Compliance

US GAAP and IFRS, SOX, multi-state sales tax, e-invoicing, GDPR and CCPA

Chapter 7

Technology and operations

Deployment, access control, integrations, data migration, AI

Chapter 8

Vendor and partner

References, project team, support, licensing, exit terms

Chapter 9

Timeline and selection process

Milestones, budget, resources, proposal contents, scoring weights

Blue guidance boxes explain what belongs in each section and where projects usually go wrong; you delete them before sending. The Excel checklist comes with 61 example requirements, drop-downs for priority and fit, and a scoring sheet that shows per vendor the knockouts, the open must-haves and the weighted fit score.

How do you gather ERP requirements?

Six steps work for most mid-market projects. The template removes the structuring work, so the time goes where it matters: agreeing priorities between departments.

  1. Name the team. One key user per department, plus a project lead and IT. Without the business, the document describes technology instead of processes.
  2. Write down the situation and the goals. Why are you changing, and how will you measure success? Three to five measurable goals are enough, for example closing the books in five working days instead of twelve.
  3. Settle the must-haves. Countries, accounting standards, deployment model and hard industry rules rule out most systems. Agree on them before you collect detailed requirements.
  4. Describe processes and requirements. Per area: today's process, the pain points and the requirements in the checklist, each with a priority and a short rationale.
  5. Add volumes and constraints. Users, transactions, integrations, data migration, timeline and, optionally, a budget range.
  6. Fix the scoring, then send. Criteria weights, what the proposal must contain, deadlines. Only then does the document go to the longlist.

How do you write a good requirement?

A good requirement states one testable outcome in one sentence and names no solution. That lets each vendor show how its standard product gets there, instead of quoting a customization that rebuilds your old system.

We need the same availability check we have today.

Order entry returns a committed delivery date based on stock, inbound supply and capacity.

Must integrate with Salesforce.

Won opportunities create sales orders automatically, including price and delivery terms (about 40 per day today).

Good reporting.

Business users build reports without programming and export them to Excel.

Add a one-line rationale to each requirement. It helps vendors propose the right answer and helps you defend the priority when the budget gets tight.

Must, Should, Could: how many must-haves make sense?

Must-haves are knockouts: a system that misses one is out, whatever its score. Should requirements are important and weighted, Could requirements are welcome. In practice 20 to 30 real must-haves are enough. Beyond that they tend to exclude every system and stop doing their job.

Fewer requirements eliminate systems than most buyers expect. In the runs of our comparison analyzed in the selection guide, only two answers cut the field sharply: on-premise or private hosting, and parallel ledgers for two or more accounting standards. You can test your own knockouts before you send anything: the free ERP comparison checks industry, countries, accounting standards and deployment against 20 ERP systems and shows which drop out.

Requirements template or ERP RFP template?

The requirements are the core of any ERP RFP. A request for proposal adds the commercial frame: what each proposal must contain, deadlines, contacts and how responses will be scored. Chapter 10 of the template covers exactly that, so you can send the Word document and the Excel checklist together as your RFP package.

Which mistakes should you avoid?

Describing the old system

Requirements written around today's screens and workarounds get you proposals for customizations instead of standard functionality. Describe the outcome, not the path your current system takes to it.

Too many must-haves

With 150 must-haves no system qualifies and the priority loses its meaning. Real knockouts are rare: countries, accounting standards, deployment model and hard industry rules.

No volumes

Without user counts and transaction volumes, every vendor sizes the proposal on its own assumptions. The quotes are not comparable, and the gap shows up during the project.

Weights set after the proposals

Weights chosen once the proposals are in tend to drift toward the favorite. Put the scoring weights in the document before it goes out.

Business users left out

A requirements document written only by IT describes technology instead of processes. Every area needs a key user who writes its requirements and later scores the demos.

How do you score the responses?

Vendors mark each requirement in the Excel checklist as met out of the box, by configuration, only with an extension, or not at all. The scoring sheet turns that into points, weights them with your priorities and flags every vendor with a must-have it cannot meet as excluded.

Functional fit is only part of the decision. The template proposes an overall score in which five-year cost, partner and references, technology and contract terms together weigh more than the checklist. For the cost side, see our ERP pricing guide; for where the systems stand, the independent overview of the best ERP software.

ERP requirements FAQ

What is an ERP requirements document?

An ERP requirements document describes, from the company's point of view, what a new ERP system must do: processes, volumes, compliance, technology and the rules of the selection. It is written solution-neutral and gives every vendor the same basis for their proposal.

Is a requirements template the same as an ERP RFP template?

They overlap. The requirements document is the core of an ERP RFP (request for proposal). An RFP adds the commercial part: what the proposal must contain, deadlines, contacts and how responses are scored. This template covers both: the requirements in Word and Excel, plus the proposal contents and scoring in chapter 10.

How many requirements should an ERP requirements list have?

For a mid-market company, 100 to 300 requirements in the checklist are typical, of which 20 to 30 are real must-haves. More detail rarely changes the outcome; clear must-haves, volumes and scoring weights do.

How long does it take to gather ERP requirements?

Plan three to six weeks when the key users from each department are involved. A template removes the structuring work; most of the time goes into agreeing priorities between departments.

Is the template really free?

Yes. You get the Word template and the Excel checklist in exchange for your email address. Your address goes to implementation partners, vendors or selection consultants only if you explicitly tick the box for it.

Does the template work for any ERP system?

Yes. It is vendor-neutral and contains no product names. It works for NetSuite, SAP, Microsoft Dynamics 365, Acumatica, Odoo or any other system, cloud or on-premise.

Shorten the longlist first

See in about two minutes which of 20 ERP systems meet your must-haves at all. Vendor-neutral and free.

Start free comparison
Tobias Trost, Independent SAP S/4HANA Cloud Consultant, Founder of ERP Pilot

About the author

Tobias Trost

Independent SAP S/4HANA Cloud Consultant, Founder of ERP Pilot

Tobias Trost is an independent SAP S/4HANA Cloud consultant specializing in Sales and Distribution and Order-to-Cash, and the founder of ERP Pilot. He writes and reviews the comparisons on this site.

Last updated: November 2026