All resources
Template or tool

Business Process Catalog (L1–L4) Template

Build a four-level business process catalog for your ERP program, aligned to the Dynamics 365 end-to-end processes, with scope, owners, fit-gap and test status.

Free

Free Excel workbook. Build a four-level business process catalog for your ERP program, aligned to the Dynamics 365 end-to-end processes, with scope, owners, fit-gap and test status. Download it, add your project details and use it today: no sign-up for software, no paywall.

A process-first backbone for ERP and Dynamics 365 programs. Catalog your processes from end-to-end process (L1) through process area (L2), business process (L3) and scenario (L4), following the structure of the Microsoft Dynamics 365 business process catalog. Each node carries its owner, personas, scope decision, release, fit-gap result, linked requirement IDs, documentation status and test status, and a check column flags in-scope processes with no owner or requirements. A roll-up sheet counts scope, gaps and test progress per end-to-end process, and the Personas sheet links processes to the people and security roles that run them.

What's inside

  • Process Catalog: One row per process node, L1 to L4. Fill the parent levels on every row so you can filter and pivot.
  • Scope by End-to-End: Pick an end-to-end process in column A; counts roll up from the Process Catalog.
  • Personas: The people who run the processes. Use these names in the Personas column of the catalog.
  • Summary: key numbers calculated automatically from your data
  • Drop-down lists, worked example rows and formulas you can rely on

How to use it

  1. Start at L1 with the 15 end-to-end processes in the dropdown, which follow the Microsoft Dynamics 365 business process catalog. Mark each In scope, Out of scope or Not applicable in the first scoping workshop.
  2. Add L2 process areas under each in-scope L1, named as verb-noun pairs, for example 'Create and manage sales'. Reuse standard names rather than inventing new ones.
  3. Break each L2 into L3 business processes, then add L4 scenarios only where the business runs a meaningful variant, such as drop-ship or intercompany orders.
  4. Fill the L1 to L3 parent columns on every row, even at lower levels, so filters, pivots and the roll-up sheet work.
  5. Assign a process owner to every in-scope node and link the requirement IDs from your traceability matrix. The Check column flags what is missing.
  6. Update fit-gap, documentation and test status as the project moves through design, build and test.
  7. Use the Scope by End-to-End and Summary sheets in design reviews and steering committees to show scope and readiness by process.

Who it's for

Project managers, solution architects, functional consultants and client-side leads who want their ERP program to go live on time and actually deliver value.

Let's connect

I'm Pranshu Shubham, a Microsoft Dynamics 365 F&O Solution Architect and PMP-certified program lead with 8+ years of ERP and AI transformation across the USA, Europe and APAC. I created this resource from real project experience, and I'd love to hear how you use it.