Skip to main content

Understand your Playbook: processes, tasks, and how-tos

Learn how processes, tasks, how-tos, policies, and company roles fit together in Subtrak.

Your Playbook is your company's shared reference for how work gets done. Use it to explain what needs to happen, who is responsible, and how to do the work.

Processes: the sequence of work

A process groups tasks that lead to an outcome. It helps the team understand the order of work and the handoffs between people.

For example, a project startup process might include reviewing the contract, setting up the job, ordering materials, and holding a handoff meeting.

Tasks: the individual actions

A task describes something that needs to be done, such as ordering materials. It can identify the company role responsible and include instructions. Tasks can exist on their own or be included in processes.

How-tos: the instructions for a task

A how-to explains how to complete a task. It can include an overview, step-by-step instructions, images, video links, and supporting files. You may also call this an SOP, or standard operating procedure.

For example, the task Order materials could have a how-to explaining how to check quantities, request pricing, place the order, and confirm delivery.

You do not need detailed instructions for every task before a process is useful. Start with the task list and add how-tos where people need more guidance.

Policies and roles: standards and responsibilities

  • Policies describe company rules, expectations, and standards.

  • Roles describe responsibilities for positions such as Project Manager or Foreman.

A company role describes a person's responsibilities. An account access level controls what the person can view or change in Subtrak.

Playbook content and work in progress

The Playbook describes your standard way of doing things. A process used in a Project or Operation applies that process to actual work, where tasks can be assigned and their completion tracked.

For example, keep your standard project startup process in the Playbook, then use it on each job that needs it.

Next step

Did this answer your question?