Module 22 · Core · 9 min read
The Business Blueprint and sign-off
You will be able to: List the sections of a Business Blueprint; Run a review and obtain a meaningful sign-off; Keep an assumptions and risks register.
- Read not done yet
- Self-check: not taken not done yet
- Lesson complete not done yet
The Business Blueprint is the agreed design of the future system: what will be configured, how each process will work, and what is outside the project. It is the contract of understanding between consultant and client, and the reference every later test is written against.
| Section | Content |
|---|---|
| 1 Objectives and scope | Why the project exists, modules, sites, users, exclusions |
| 2 Organisation setup | Company, branches, warehouses, users, roles |
| 3 Process designs | For each process: to-be flow, Zeyto documents used, roles, controls, exceptions |
| 4 Master data and migration | Which data comes from where, mapping rules, owners, cut-off date |
| 5 Configuration decisions | Chart of accounts approach, tax codes, numbering, approvals, credit control, print formats |
| 6 Reports and outputs | Reports management needs and who receives them |
| 7 Fit-gap register | Every gap with its decision and owner |
| 8 Infrastructure | Deployment model, devices, printers, backup plan |
| 9 Test and training approach | Test levels, UAT owners, training plan |
| 10 Assumptions, risks and open issues | The register below |
| 11 Sign-off page | Names, roles, date, version |
Getting a sign-off that means something
- Walk through the draft in a review workshop. Do not email a 60-page document and wait.
- Collect comments in one list and resolve each: accept, reject with reason, or move to a change request.
- Issue version 1.0 and agree a review period, for example five working days, in the contract.
- Collect signatures from the sponsor, finance lead and each process owner.
- After sign-off, changes go through change control.
Watch outSilence is not agreement unless the contract says so. If nobody replies, escalate to the sponsor with the dates. Do not start configuring against an unsigned design.
Assumptions and risks
| ID | Item | Impact if wrong | Owner | Response |
|---|---|---|---|---|
| A-01 | Client supplies cleaned customer and item files by day 15 | Migration slips by up to 5 days | Client lead | Weekly check; escalate on day 12 |
| A-02 | Two key users available 2 hours a day in UAT | UAT extends | Sponsor | Confirm in kickoff |
| R-03 | Accountant unavailable in VAT filing week | Opening balance sign-off delayed | Project manager | Plan around the filing date |
| R-05 | E-invoicing provider not chosen by go-live | Compliance exposure | Accountant | Decision at blueprint sign-off |
A change after sign-offThe blueprint says one approval step for invoices above AED 50,000. Three weeks later the owner wants two steps above AED 200,000. The consultant records a change request, estimates 0.25 day, and the sponsor approves it in writing. Nothing is configured until approval.
Practise in the demo
- Write the headings of a blueprint for a small trading company and add one assumption and one risk.
- Open Settings, then Approval Rules in the demo and read how a rule is described. Imagine writing it as a blueprint entry.
- Open https://demo.zeyto.app/demo-app/ and sign in with the demo login. This is a public demo with sample data, so nothing you do there affects a real business.
Public demo company, sign in as admin / demoAdmin123. Data refreshes nightly.
Key takeaways
- The blueprint is the signed design that all tests and changes are measured against.
- Review it in a workshop, collect comments in one list and agree a review period.
- Silence is not sign-off, and later changes go through change control.
Check yourself
5 questions on this lesson. Not timed, not the exam, and you can try again. Score 60% or more, and read the lesson, to complete it.
1. Which document is signed to freeze the agreed design before configuration begins?
2. Which TWO are sound, testable assumptions for a blueprint?
Select all that apply.