Building & Editing Playbooks with Aero

Building a playbook from scratch can feel like staring at a blank canvas.

Aero is here to help you skip the blank-canvas part — and get straight to a playbook that actually fits how you onboard.

This article covers what Aero can do when you're creating or editing playbooks, how to work with it, and what to expect along the way.

Two Ways to Build with Aero

You can work with Aero in either of these places:

• The Aero chat — Open Aero anywhere in OnRamp and describe the playbook you want in plain language. Aero takes it from there.
• Create Playbook from the Library — Choose the "Create Playbook" option in your Library and let Aero generate a starting point based on your prompt.

Both paths support file uploads. If you've already got an outline, an SOW, a kickoff deck, or a process doc — drop it in and Aero will use it as the foundation (or as supporting context for your description).

Editing Existing Playbooks

Aero isn't just for net-new builds. You can also use it to:

• Edit a playbook directly from the Aero chat
• Refine sections from inside the playbook editor — just open the chat there and tell Aero what you want changed

Whether you're tightening up an existing template or restructuring an entire flow, Aero can shape it without you clicking through every change.

What Aero Can Build For You

Aero can stand up the structural backbone of a playbook, including:

• Modules — including module names and how content is grouped
• Tasks — with descriptions, due dates, visibility settings, and task type
• Portal and module naming — plus other module-level configuration
• Recommendations — for structure, sequencing, and naming based on OnRamp best practices

If you ask Aero to review a playbook, it will also flag things like duplicative tasks, conflicting or unrealistic dates, and naming inconsistencies — so you can catch issues before your customer does.

Working With Files

Uploads are great for adding context, with a couple of guardrails:

• 5MB max per file
• One file at a time
• Recommended file types: XLSX, Doc, PDF, & Image

Best practice: break larger source documents into focused chunks (for example, one module's worth of tasks per upload) and feed them to Aero as you build. You'll get sharper, more relevant output than dumping a 60-page implementation guide in one shot.

A Few Things to Add Manually

Aero handles the structural work so you can focus on the polish. After Aero's done its part, you'll want to layer in the items that still need a human touch:

• Subtasks
• Role restrictions
• Dependencies and blockers
• Automations, tags, merge fields, and data fields
• Resources

Treat Aero as your starting point — then refine the details that make the playbook truly yours.

What Happens When You Save Edits?

Every time you save changes to a playbook, OnRamp tracks the version. To learn more about how versioning works, see Editing and Versioning Playbooks.

Best Practice: Iterate, Don't Perfect

The fastest way to get value from Aero is to treat it like a collaborator:

• Start with a rough description
• Let Aero produce a draft
• Review, prompt for refinements, and add files as needed
• Polish the manual pieces yourself

You'll end up with a tighter playbook in a fraction of the time.

Next Step

Once your playbook is built, you're ready to:

• Configure subtasks
• Add automations, merge fields, and resources
• Launch your first project