Process map notes
Start with the event that begins the process and the result that ends it. List each step, owner, input, output, and exception.
Example: Purchase request | Equipment needed | Manager reviews request | Manager | Cost and reason | Approved or returned | Manager absent.
| Field | What to record |
|---|---|
| Process name | Add your notes. |
| Start event | Add your notes. |
| Step | Add your notes. |
| Owner | Add your notes. |
| Required information | Add your notes. |
| Result | Add your notes. |
| Exception | Add your notes. |
| Open question | Add your notes. |
Requirement template
Write the need in business terms and define an expected result. Record the owner who can approve it.
Example: R-01 | Purchasing team | Return incomplete requests | Avoid wrong orders | Missing delivery address prevents approval | Purchasing lead.
| Field | What to record |
|---|---|
| Requirement ID | Add your notes. |
| User or team | Add your notes. |
| Need | Add your notes. |
| Reason | Add your notes. |
| Acceptance check | Add your notes. |
| Owner | Add your notes. |
| Priority | Add your notes. |
| Assumptions | Add your notes. |
Test script template
A test needs a known starting point, clear steps, and an expected result. Record the actual result and evidence separately.
Include at least one exception and one access check. A normal happy-path test alone gives limited confidence.
| Field | What to record |
|---|---|
| Test ID | Add your notes. |
| Related requirement | Add your notes. |
| User role | Add your notes. |
| Starting data | Add your notes. |
| Steps | Add your notes. |
| Expected result | Add your notes. |
| Actual result | Add your notes. |
| Pass or fail | Add your notes. |
| Evidence | Add your notes. |
| Tester and date | Add your notes. |
Decision log template
Record the options and reason for the choice. This helps a later team understand the design when conditions change.
Example: D-01 | Who handles an absent approver? | Delegate or reassign | Approved delegate | Keeps ownership clear | Incorrect delegation | Process owner.
| Field | What to record |
|---|---|
| Decision ID | Add your notes. |
| Question | Add your notes. |
| Options | Add your notes. |
| Chosen option | Add your notes. |
| Reason | Add your notes. |
| Risks | Add your notes. |
| Owner | Add your notes. |
| Date | Add your notes. |
| Review trigger | Add your notes. |
Handover template
Explain how the work runs and how to find help. Ask another person to follow the notes before calling the handover complete.
Use approved internal storage for real project documents. Keep passwords, tokens, and private data out of notes and public portfolios.
| Field | What to record |
|---|---|
| Purpose | Add your notes. |
| Scope | Add your notes. |
| Owners | Add your notes. |
| Access needs | Add your notes. |
| Routine checks | Add your notes. |
| Common failures | Add your notes. |
| Recovery steps | Add your notes. |
| Escalation | Add your notes. |
| Known limits | Add your notes. |
| Related records | Add your notes. |
Practice task
Your practice checklist
Tick off each task as you finish. Progress stays in this browser.
0 of 4 done
Sources and further reading
Use these sources to check product details and find learning material. Check exam and course details before booking.
- Microsoft Learn: Dynamics 365
- Microsoft: roles in an implementation team
- Microsoft: exam retirement dates
Work examples are learning exercises. Duties and job titles vary between employers. How we write and update our guides.
Suggest a correction