A
Term | Definition |
Acceptance Criteria | The requirements that must be met for a Task or Deliverable to be considered completed and accepted. |
Acceptance Status (Forms) | Defines the Form statuses that contribute to Task progress in Playbook. Only Forms that match with a configured Acceptance Status will contribute to Task progress. |
Actual Deliverable | A Deliverable that has been completed or submitted, as opposed to its planned delivery. |
Actual Task | A Task that has been completed or carried out, as opposed to its planned schedule. |
Allowed Delay (Optimism Bias) | An additional period of time allowed after a Task's due date before the Task is considered overdue or triggers non-compliance rules in Playbook. Also referred to as the grace period. |
Attribute | A field used to capture specific information about an item in Playbook. |
Attribute Library | A central location where reusable Attributes can be created and managed for use across Playbook. |
Attribute Set | A predefined group of Attributes that can be applied together to capture a consistent set of information. |
Average Bias | Calculates progress based on the number of Deliverables expected to be completed across the Task or Package duration. |
B
Bias | Biases control how Playbook calculates and classifies progress statuses for Tasks and Packages within a Plan. Playbook includes three Bias types: Average, Optimism and Realism Bias.
Each Bias applies with a different tracking logic to determine whether work is progressing as expected, delayed, late, overdue, completed or verified.
For more information, see Status Criteria - Biases. |
C
Calendar View | A calendar-based layout that displays scheduled Tasks, Deliverables, or other planned activities by date. |
Card / Matrix Card | A square tile in the Playbook Matrix that contains a Package and represents it within the Matrix. |
Checklist Item | An individual action or requirement within a Task that defines what must be completed for the Task to be considered done. |
Clone (for Templates) | A function used to create a copy of an existing Template that can be modified independently. |
Common Data Environment (CDE) | Asite's central environment used to collect, manage, share and control Project information throughout the Project lifecycle. |
D
Dashboard | A visual overview of key Playbook information, progress, and performance data. |
Deliverable | An item that must be delivered for a Task to be completed, typically a file or Form. |
F
Form | A structured record used to caputre, submit, review, and manage Project information. |
G
Guidance | Instructions or reference information that helps a Task Owner understand how to complete a Task correctly. |
I
Information Delivery Plans (IDPs) | The CDE settings used to manage Playbook-specific permissions within a Project. When Playbook is enabled, IDPs allow permissions to be configured for CDE roles that require access to Playbook functionality. |
L
List View | A structured list-based layout used to view and manage Playbook items and other associated information. |
O
Optimism Bias | A progress calculation based on the Task or Package due date that includes an allowed delay before work is classified as late or overdue. It provides additional flexibility for short delays when work is already in Progress.
For more information, check Optimism Bias. |
P
Package | A group of related work, Tasks, or Deliverables organised together within a Playbook structure. |
Package Owner | The user responsible for delivering the Package and ensuring that all Tasks within it are completed. |
Permission Matrix | A structured view of the permissions assigned to different Playbook roles, showing which actions each role can perform. |
Plan | A structured set of activities, Tasks, Deliverables, and schedules used to manage work within Playbook. |
Plan Code | A unique code used to identify a Plan. |
Plan Manager | A user with permissions to manage Plan information, including adding rows and Packages and assigning or editing responsibilities. |
Planned Deliverable | A Deliverable that is expected to be completed or submitted according to the Plan. |
Planned Task | A Task that is scheduled to be completed as part of a Plan. |
Playbook | An Asite solution used to structure, plan, manage, and monitor Project activities and information delivery. |
Playbook Admin | A user with permissions to restructure a Plan, manage permissions and Attributes, and perform other administrative actions within Playbook. |
Playbook Matrix / Grid | A structured view used to organise and manage Packages, Subpackages, Stages, and their associated information. |
Project / Workspace | A dedicated area in Asite where teams manage information, processes, users, and Project activities. |
Project Finder | The area used to find, filter, and select Projects. |
R
Realism Bias | A progress calculation that compares planned Deliverable dates against actual progress. Tasks or Packages are classified as late or overdue when required work is not completed by the expected due date.
For more information, check Realism Bias. |
Recurring Forms | Forms associated with a Task that are automatically scheduled or required at defined intervals throughout a Plan. |
Rescind Condition | A condition that determines when previously achieved Task progress should be recalculated if associated files no longer meet the required criteria. |
S
Save as Plan (for Templates) | A function used to create a new Plan from an existing Template. |
Schedule Performance Index (SPI) | A performance indicator that compares completed Deliverables against planned Deliverables to measure schedule performance. A lower SPI indicates that fewer Deliverables have been completed than planned. |
Singular Forms | Forms associated with a Task that are completed as a one-time activity rather than on a recurring basis. |
Stage | A defined phase within a Playbook structure used to organise work according to a particular point in the Project or process. |
Subpackage | A smaller grouping of work within a Package used to organise related Tasks or Deliverables in greater detail. |
Subpackage Owner | The user responsible for overseeing and managing a Subpackage and its associated activities. |
T
Task | An individual activity or piece of work that must be completed as part of a Plan. |
Task Checklist | A list of individual checks or actions that must be completed as part of a Task. |
Task Verification | The process of reviewing a completed Task to confirm that it meets the required criteria. |
Task Verifier | The user responsible for reviewing and verifying that a Task has been completed correctly. |
Template | A reusable predefined structure used as the basis for creating new Plans. |
Template Code | A unique, six-character alphanumeric code used to identify a Playbook Template. |
Template Name | The name used to identify a Template. |
Timeline View | Displays the Playbook Plan in a time-based layout, with Packages and Subpackages listed on the left and their scheduled durations shown on the right. |
W
Workflow | A defined sequence of steps, actions, or approvals used to manage how information or activities progress through a process. |