Summary / When to Use This
In OnRamp, you can launch projects in two main ways: from a Playbook or as a One-Off Project. Playbooks are best for repeatable processes you want to standardize, while one-off projects give you flexibility for unique, ad-hoc work. Choosing the right option helps you balance consistency with customization.
Before You Begin
Make sure you have the Admin or Creator role to launch projects.
Review your organization’s Playbook Library before creating a new one — there may already be a reusable workflow you can start from.
Steps to Follow
1. Understand Playbooks
Playbooks are reusable blueprints for projects you run often.
Include preset tasks, stages, roles, and logic.
Ensure every new project follows the same structure for consistency.
Can be updated centrally — future projects launched from that playbook use the new version.
Save time by reducing repetitive setup.
Example: If you onboard every new customer with the same 4-stage workflow, launch each project from your Customer Onboarding Playbook.
2. Understand One-Off Projects
One-Off Projects are created manually without starting from a Playbook.
Great for unique, non-repeatable work.
Build tasks and stages from scratch as needed.
Offers flexibility but takes more effort to set up.
Changes stay specific to that project and aren’t reusable later.
Example: If a customer asks for a custom pilot with special milestones, you’d create a one-off project.
3. Decide Which to Use
Ask yourself:
Will I run this project type again?
Yes → Use a Playbook.
No → Create a one-off project.
Do I need consistency across teams/customers?
Yes → Playbook.
No → One-off.
Do I want to save setup time?
Yes → Playbook.
No → One-off.
Tips & Troubleshooting
Tip: Test new workflows in a one-off project. If they work well, save them as a Playbook for future use.
Troubleshooting: If you can’t launch from a Playbook, check that it’s published in the Library and that you have permission to access it.