When designing onboarding processes in OnRamp, work is organized into Modules and Tasks. Understanding how these two components work together helps teams build playbooks that are clear, scalable, and easy for customers to follow.

In simple terms:

• Modules represent phases or milestones of onboarding

• Tasks represent the individual actions required to complete those phases

Using modules and tasks effectively helps structure onboarding work for both your internal team and your customers.

What is a Module?

A Module groups related work together and represents a phase of the onboarding process.

Modules typically align with key milestones or stages of implementation.

Examples of modules might include:

• Kickoff & Planning

• Account Setup

• Integration Configuration

• Training

• Go Live

Modules help organize tasks into logical sections and make the overall project easier to navigate.

Modules also appear as sections in the customer portal, allowing customers to clearly see the stages of their onboarding journey.

What is a Task?

A Task represents a specific action that needs to be completed.

Tasks live inside modules and define the actual work required to move onboarding forward.

Examples of tasks include:

• Schedule kickoff meeting

• Upload required documentation

• Configure SSO

• Complete onboarding survey

• Review training materials

Tasks may be assigned to:

• Internal users

• Customer users

• Task roles

Tasks can also include sub-tasks, which provide instructions, collect information, or request files.

How Modules and Tasks Work Together

Modules provide structure, while tasks provide execution.

Example:

Module: Account Setup

Tasks inside that module might include:

• Create customer organization

• Configure user permissions

• Upload initial data

• Verify environment configuration

This structure makes it easier for both internal teams and customers to understand where they are in the onboarding process.

How Modules Appear in Projects

When a project is created from a playbook, modules appear as sections in the project task list.

This helps break the project into manageable stages.

Benefits include:

• Clear organization of work

• Easier progress tracking

• Improved visibility for customers

• Better onboarding flow

Modules also influence how tasks are grouped in the customer portal, improving the customer experience.

When to Create a New Module

A good rule of thumb is to create a new module when the work represents a new phase or milestone of onboarding.

For example:

Good module separation:

Kickoff → Setup → Training → Launch

Avoid creating modules for very small pieces of work. If tasks belong to the same stage, they should usually remain in the same module.

Modules should represent meaningful stages in the customer journey.

When to Add More Tasks Instead

If the work is simply another action within the same phase, it should likely be a new task rather than a new module.

For example:

Module: Integration Setup

Tasks:

• Connect CRM integration

• Configure API credentials

• Validate data sync

• Run initial test

All of these tasks belong to the same onboarding stage.

Why Modules Matter

Using modules effectively helps teams:

• Structure onboarding processes clearly

• Improve the customer portal experience

• Track milestone progress

• Enable conditional automation later

Modules can also be used in automation workflows, such as:

• Adding modules when a task is completed

• Adding modules conditionally based on customer responses

Designing playbooks with clear modules makes automation easier as your onboarding process evolves.

Best Practices

✔ Use modules to represent onboarding milestones or phases
✔ Keep modules focused on a single stage of work
✔ Use tasks to define the individual actions required
✔ Avoid creating too many small modules
✔ Use modules to improve structure in the customer portal

Well-structured modules and tasks make onboarding easier to manage and easier for customers to follow.