Start with a process your team already knows, such as project startup or closeout. Your first version can be a clear task list. Add detailed how-tos where they will help someone complete the work.
Before you begin: You need permission to create Playbook content, such as Editor or Administrator access. This guide covers the standard company Playbook on desktop.
1. Create the process
Open Playbook and select Processes.
Open Create and choose Process.
Enter a clear Process name, such as Project startup.
Add a short description of what the process covers. Choose departments or project types if they help organize it.
2. Choose how to build it
You can use either method:
Build it for me: Describe the process and let AI prepare a starting point. Explain the goal, main tasks, responsible roles, and anything specific to your company. Review the result before using it.
Build it manually: Write the tasks yourself. Use this when you already know the steps or want to outline them one at a time.
3. Add tasks in the order they happen
Give each task a clear action name. For example:
Review the signed contract.
Set up the job in the project management system.
Confirm the material order.
Hold the project handoff meeting.
Use Add task to add more tasks. Arrange them in the order your team should follow and choose the responsible company roles.
4. Add instructions where they are needed
Open a task to add or review its how-to. Explain what the person needs to do and include relevant steps, images, links, or files. Focus first on tasks that cause questions, mistakes, or inconsistent results.
Check any AI-generated instructions against how your company actually works.
5. Review and publish
Check that the task list is complete and in the right order.
Confirm the responsible roles and review the instructions.
Choose Save draft if you want to keep working on it, or Publish process when it is ready for your team.
Publishing a Playbook process makes it available as company guidance to people with access. It does not, by itself, create a project or assign the process to a particular job.
Try it with one team member
Ask someone to read the process and use one of its how-tos. Update anything they find unclear. When you are ready to track it on actual work, add the process to a project or operation.
