The playbook functions like the form and shares the same statuses associated with the project apps. With the appropriate privileges, you can select "Status:" on the left side of the blue ribbon to change the status for an entire plan.

Refer to this article to learn more about changing the status of a form.

Five statuses in the Asite Playbook refer to the stage of the task, package or whole category within the plan.

Whenever you set up a task, package, or entire stage, the initial status is always "To Do". This indicates that the job has not yet started, and it will not be possible to complete any tasks assigned to that part. For example, even if you meet the task requirements and upload a file, it won't count if the status remains "To Do".

When it is time to start working on the project's first column (stage, gate) the Playbook Manager or Admin should change the status from "To Do" to "In Progress". This can be done by clicking the bottom left corner of the stage tile and selecting "In Progress". This change will automatically update the status for packages, sub-packages, and tasks within that column.

Please note that you cannot change the status of an individual package or task to "In Progress" if its main stage is still in the "To Do" status. You need to work from top to bottom. However, you can change the status from "In Progress" back to "To Do" at any point in the plan.

When the Task Owner has finished all the required files or forms for a task, they should change the task status from "In Progress" to "Completed". This should only be done when all necessary attachments for that task are submitted.

Once all tasks in a (sub)package are done, the (sub)package owner should also update the status from "In Progress" to "Completed". The same goes for an entire collumn.

Keep in mind that "Completed" does not mean the work is finished; it still needs to be verified. If changes are needed, the work may be sent back for adjustments. Therefore, we recommend not moving to the next stage until the previous tasks are verified.

When the task is marked as completed, the Playbook Admin or Playbook Manager must verify it. During the verification process, they can either send it back to "In Progress" and request some changes or sign it off by marking it as "Verified" using a button in the bottom-right corner of the task.

Locking a task is useful in two main situations:

1. After verifying a task, you may want to lock it to prevent anyone from making changes to the associated documents or forms.

2. When a task or package in your plan is no longer necessary, you might prefer to mark it as "Locked" instead of removing it entirely. This indicates that it no longer requires completion.

Locking a task, package, or even an entire section prevents any further actions in that area. Once a task is locked, any attached documents and forms cannot be modified, and the process is irreversible. Therefore, it is important to proceed with caution when locking tasks.