Begin with the outcome
Describe the problem your team needs to solve before deciding on software modules. Examples include organising client enquiries, coordinating approvals or improving internal reports.
Map the information
Identify the source of each record, the people allowed to use it and the system that should remain authoritative. Include retention and access questions for appropriate review.
Plan the exceptional path
A useful workflow covers missing information, duplicate events, rejected requests and service interruptions. Decide what should happen and who will review each exception.
Agree acceptance and handover
Specify how the outputs will be checked and who will own the configuration, documentation and support after implementation.
General project-preparation information, not a legal, regulatory or tax opinion. Confirm the requirements of the actual activity with the appropriate professionals.
Read our activity scope 