A Playbook is a reusable operational process. It captures the steps, tasks, documents, and known risks from a completed trip so you can apply the same structure to future trips without starting from scratch.
Getting to Playbooks
Click Playbooks in the sidebar under the Standardize section.
What a Playbook contains
A Playbook is made up of components — individual steps or items organized by phase. Each component has:
- A title and optional description
- A phase (for example, Before Trip, Before Departure, At Stop, After Trip)
- A component type (for example, Task, Checklist Item, Document, Meeting)
- A required flag — required components must be completed before the trip can be closed
Playbooks can also include Known Risks — documented hazards or issues encountered on previous trips, with severity levels and mitigation notes.
Playbook phases
Components are organized into phases that correspond to stages of a trip:
- Before Trip
- Before Departure
- Travel Day
- Arrival
- At Stop
- Post Stop
- End of Day
- Return Home
- After Trip
Visibility
Each Playbook has a visibility setting:
- Personal — only you can see and use it
- Team — shared with team members in your organization
- Organization — available to all members of your organization
Playbook status
- Draft — being built, not yet ready to apply
- Active — ready to apply to trips
Playbooks saved as Draft are listed separately on the Playbooks page. Activate a playbook when it is ready to use.
Effectiveness tracking
The Playbook detail page shows effectiveness metrics once the playbook has been applied to at least one trip:
- Times used
- Trips completed
- Required step completion rate
- Open follow-ups
- Helpful / Not Helpful feedback ratings
Feedback
After using a playbook on a trip, you can submit feedback (Helpful, Partially Helpful, or Not Helpful) with an optional note. Feedback is visible on the Playbook detail page.
Version history
Each time a playbook is edited and saved, a new version is recorded. The version history is visible on the Playbook detail page. If two or more versions exist, you can compare them.
Tips
- Start by creating a playbook from a completed trip that went well. The system extracts components automatically.
- Review the extracted components and remove anything that was specific to that one trip rather than reusable.
- Activate the playbook only when you are satisfied with the components.
- Apply the playbook at the start of a new trip to pre-populate the Execution page.