Man looking at laptop and tablet devices

Prepare and build

Once you have identified a suitable process, the next step is to prepare it for configuration.

Configuring your process

This section helps you move from process idea to first working version. Use the checklist, examples and practical guides to clarify what needs to be built before you start working in the F2 Service Builder design template.

For detailed instructions on specific configuration steps, use the full F2 Service Builder manual in F2 Docs.

[Open the manual] [Use the checklist]

F2 Service Builder manual

Start with the essentials

Process structure

Map the phases, tasks, decisions and responsibilities before you start building. A clear process structure makes it easier to configure, test and maintain the process

Documents and communication

Identify the documents, templates, emails, receipts and merge fields needed in the process. Clarifying this early helps avoid rework later.

Data and overview

Clarify what data should be captured and what overview users, process owners or managers need during and after the process.

Testing and production readiness

Plan how the process will be reviewed, tested and approved before it is put into use. This helps ensure that the process works as intended for the people who will use it.
Process structure

Map the phases, tasks, decisions and responsibilities before you start building. A clear process structure makes it easier to configure, test and maintain the process.

  • What are the main phases of the process?
  • Which tasks must be completed in each phase?
  • Who is responsible for each task?
  • Which decisions move the process forward?
  • Are there approvals or handovers between units?
  • What should happen when the process is completed?

CTA:

  • Open before-you-start checklist
  • View process mapping template

Documents and communication

Identify the documents, templates, emails, receipts and merge fields needed in the process. Clarifying this early helps avoid rework later.

  • Which document templates are needed?
  • Which information should be inserted automatically?
  • Are merge fields required?
  • Which emails should be sent during the process?
  • Should users receive receipts?
  • Which messages should be standardized?
  • Who owns and maintains the templates?

CTA:

  • Read merge fields guide
  • Read document templates guide
  • View email templates and receipts guide

Data and overview

Clarify what data should be captured and what overview users, process owners or managers need during and after the process.

  • Which information should be registered during the process?
  • Which data is needed for follow-up or reporting?
  • Do managers need an overview of progress or workload?
  • Are calculations needed?
  • Should data be structured in a specific way?
  • Are there requirements related to archive, documentation or handover?

CTA:

  • View calculation sheet example
  • Read management overview guidance
  • Open before-you-start checklist

Testing and production readiness

Plan how the process will be reviewed, tested and approved before it is put into use. This helps ensure that the process works as intended for the people who will use it.

  • Who reviews the first version?
  • Who tests the process?
  • Which scenarios should be tested?
  • Who approves the process before production?
  • What needs to be documented?
  • Who maintains the process after launch?
  • What should be checked after updates or changes?

CTA:

  • Open test and review checklist
  • See known limitations and issues

Practical build guides

Use these short guides when you need help with specific parts of the build.

Layout and headings

Make the process easier to understand by using clear headings, consistent structure and a layout that gives users a good overview.

[Read layout guide]

HTML cheat sheet

Use simple HTML formatting to improve text, links and instructions in self-service forms and process descriptions.

[Open HTML cheat sheet]

Merge fields and document templates

Learn how merge fields and document templates can help generate documents with the right information from the process.

[Read merge fields guide]

Calculation sheet

Use examples to understand how calculations can support your process. Start from a simple example before building more advanced logic.

[View calculation sheet example]

Email templates and receipts

Prepare standard emails and receipts so users receive consistent communication throughout the process.

[Read guide to email templates and receipts]

Common pitfalls

Before you upload or test your process in F2 Service Builder, check for common issues.

Typical pitfalls include:

  • Building before the process is sufficiently clarified
  • Missing agreement on roles and responsibilities
  • Documents or templates that are not ready
  • Unclear use of merge fields
  • Layout that makes the process difficult to navigate
  • Calculations that are hard to understand or maintain
  • Missing plan for testing and review
  • Dependencies on integrations or functionality that have not been assessed

[See known limitations and issues]