Usethis checklist to prepare a process before you begin configuration in F2 Service Builder.
The checklist helps the process owner, business unit, superusers, and digitalization team agree on the information needed to build, test, and maintain the first version.
You can also download a printer-friendly version of the checklist.
How to use the checklist
Go through the sections below before you start working in the design template. For each question, check one of the three boxes:
- Clear: The point has been clarified and is ready to use in the build.
- Needs clarification: More information or alignment is needed before you build.
- Not relevant: The point does not apply to this process.
If several items need clarification, resolve them before you begin building the process.
1. Process purpose and ownership
Start by clarifying why the process should be built and who is responsible for it.
- The purpose of the process is clearly described
- The expected value of the process is understood
- The process has a clear owner
- The business unit or subject-matter team has been identified
- The digitalization team or superuser responsible for the build has been identified
- The process has been prioritized for development
2. Users, roles and responsibilities
Clarify who will use the process and who is responsible for each part of it.
- The main user groups are identified
- Roles and responsibilities are described
- It is clear who creates or starts the process
- It is clear who completes each task
- It is clear who reviews or approves the process
- It is clear who maintains the process after launch
3. Process structure
Describe the process in enough detail to make it ready for configuration.
- The main phases of the process are known
- The main tasks in each phase are described
- The order of tasks is understood
- Key decisions and outcomes are described
- It is clear when the process starts
- It is clear when the process ends
- Mandatory and optional steps are identified
4. Documents and templates
Identify the documents and templates that the process depends on.
- Required document templates are identified
- Standard letters, decisions or responses are identified
- Ownership of document content is clear
- Required merge fields are identified
- Existing templates that can be reused are identified
- Documents have been reviewed by the relevant business or legal owners where needed
5. Communication
Clarify which messages, emails and receipts are needed during the process.
- Required email templates are identified
- Required receipts or confirmations are identified
- The wording of standard messages is agreed
- It is clear who receives each message
- It is clear when each message should be sent
- Communication ownership and maintenance are clear
6. Data, overview and reporting
Clarify what data should be captured and what overview users or managers need.
- The data to be registered during the process is identified
- Reporting or management overview needs are described
- It is clear which data is needed for follow-up
- Any calculation needs are identified
- Documentation, archive or handover requirements are known
- It is clear how the data will be used after launch
7. Dependencies and limitations
Identify dependencies that may affect the process design or build.
- Dependencies on other systems are identified
- Integration needs have been assessed
- Manual steps outside F2 Service Builder are identified
- Relevant F2 configuration dependencies are known
- Known limitations have been considered
- The digitalization team or cBrain has been involved where needed
8. Testing and review
Plan how the process will be tested before it is put into use.
- The person or team responsible for review is identified
- The person or team responsible for testing is identified
- Key test scenarios are described
- Time has been reserved for testing and adjustments
- Approval before launch is agreed
- It is clear who will handle changes after launch
9. Readiness summary
Use this summary after completing the checklist.
Ready to build
The process may be ready for configuration if:
- The purpose and owner are clear
- Roles and responsibilities are agreed
- The process structure is detailed enough to build from
- Documents, templates, communication and data needs are known
- Dependencies and limitations have been assessed
- Testing and review responsibilities are agreed
Recommended next step:
Prepare the first version in F2 Service Builder and plan review with the relevant business unit.
Needs clarification
The process may need more clarification if:
- The process is only described at a high level
- Roles or responsibilities are unclear
- Required documents, templates or data are not ready
- Dependencies have not been assessed
- Testing and maintenance responsibilities are unclear
Recommended next step:
Clarify the open points with the business unit, process owner or digitalization team before building.
Next step
Once the process is sufficiently clarified, continue with the relevant build guides or open the full F2 Service Builder manual in F2 Docs.
Open the F2 Service Builder manual
[Browse templates and examples]
