Playbook 2.1 Beta
Playbook 2.1 Beta
This release introduced the Playbook 2.1 Beta experience, replacing key limitations in Playbook 1.0 and introducing improved structure, configurability, and workflow control.
Feature | Playbook 1.0 (Previous Model) | Playbook 2.1 Beta | Why This Matters |
New User Interface & Plan Creation | Plan creation was fragmented, with limited guidance and a less intuitive interface. Users had to navigate multiple areas without clear direction, making onboarding slower and more error-prone. | Redesigned interface with guided steppers, improved navigation and Plan creation experience. | Faster onboarding, and more efficient Plan setup. |
Right-Click Plan Editing | Editing actions were distributed across menus, requiring multiple clicks. | Right-click contextual actions available in Editing mode for quicker updates. | Faster editing and reduced effort for both individual and bulk changes. |
Summary View | Limited visibility into overall Package progress, with no flexible way to interpret progress metrics. | Configurable Summary View that allows users to select how progress is calculated (optimistic, average, or realistic). | Better decision-making through flexible and clearer progress insights. |
Advanced Attributes (Geo-Based) | Attributes were limited to basic data types with no support for location-based mapping or spatial data. | Attributes now support map and coordinate-based inputs. | Enables location-aware planning and more meaningful Plan data. |
Bulk Apply Attributes | Attributes had to be applied manually to each Package or Subpackage, making large Plans time-consuming to configure. | Attributes can be applied across an entire Plan in a single action. | Significant time savings and consistency across large Plans. |
Automatic Task Status Assignment | Task statuses required manual updates, increasing admin effort and risk of outdated or inaccurate status tracking. | Task status updates automatically when work begins. | Improved accuracy and reduced manual intervention. |
Rescind Conditions | No automated way to revert Task status based on changing conditions; required manual intervention. | Conditions can be defined to automatically revert tasks to a previous state. | Greater control and accuracy in dynamic workflows. |
Configurable Progress Calculators | Progress calculation was fixed, offering limited flexibility in how completion was measured. | Users can define how progress is calculated via configurable logic. | More accurate and tailored progress tracking. |
Basic Tasks (Without Documents) | Tasks were typically dependent on structured inputs (Forms/files), limiting flexibility for simple or ad-hoc activities. | Lightweight Tasks can be created without requiring Forms or files. | Faster Task creation and greater flexibility for informal workflows. |
Template Version Control | No clear version tracking; users could not easily identify which version of a Template was in use or who made changes. | Full version control with timestamps, ownership, and version visibility. | Improved traceability and consistency across teams. |
Deliverables Linked to CDE Workflow | Limited visibility of deliverable workflow within Tasks; users had to navigate outside Playbook to track status. | Full CDE workflow visibility within the task window. | Centralised visibility and better workflow understanding. |
Review Late Submissions | Limited ability to distinguish between on-time, overdue, or late submissions within Task context. | Clear differentiation between submission timing states within Tasks. | Improved performance tracking and accountability. |
Basic Plan Import (Excel) | Plans had to be created manually, making setup slow and repetitive, especially for large projects. | Plans can be created by importing structured Excel data. | Faster setup and reduced manual effort. |
Duplicate Package (Same Stage) | Repetitive manual setup required for similar Packages within a Stage. | Packages can be duplicated within the same Stage. | Faster configuration and reduced duplication of effort. |
Validation (Missing Dates) | Missing scheduling data could go unnoticed, leading to incomplete or inconsistent Plans. | Missing dates are clearly flagged and must be completed before users can create or configure related Packages, Subpackages and Tasks. | Improved data integrity and reduced configuration errors. |
Import Sheet | No structured method for preparing Plans offline before creation in Playbook. | Predefined Excel import sheet enables offline preparation and bulk upload. | Standardised and scalable Plan creation. |
Task Acceptance Criteria | No structured way to define or validate when a Task is complete; completion relied on manual judgement or basic status updates. | Tasks can include defined Acceptance Criteria to validate completion. | Ensures consistent completion standards and reduces ambiguity in Task closure. |
Share Template | Templates were isolated, limiting reuse across users or teams. | Templates can be shared, including Stages, Packages, Subpackages, and Tasks. | Promotes reuse, consistency, and faster setup across Plans. |
Filters & Sorting in Views | Limited filtering and sorting options restricted how users could view and analyse Plan data. | Enhanced filtering and sorting capabilities provide greater control over how information is displayed. | Improves usability and allows more efficient navigation and analysis of Plan data. |
Playbook 2.2 Beta
Playbook 2.2 Beta
This release improves how users manage and review changes in Playbook, with clearer visibility during Plan updates.
Feature | Playbook 2.1 Beta (Previous Model) | Playbook 2.2 Beta | Why This Matters |
Template Version Tracking & Audit Visibility | Basic Template version control with limited visibility into changes. Users could not navigate between versions to review them. | View and navigate between Template versions, with version-specific timestamps, dates and owner details. | Improves traceability and accountability when managing Template updates. |
Copy Package Across Stages (with Tasks) | Packages could only be duplicated within the same Stage, limiting reuse across the Plan. | Allows Packages to be copied across Stages at the same hierarchy level, including all associated Tasks. | Reduces repetitive setup and improves efficiency when structuring Plans. |
Draft Mode for Editing | Changes to Templates and Plans were applied directly, with no isolated draft state. | Introduces a Draft mode to create and refine changes before publishing. | Prevents unintended changes and allows controlled updates to Plans and Templates. |
Workflow Stage in Deliverables | Workflow Stage was not visible within the Task view, requiring users to navigate outside the Task to understand progress. | Workflow Stage is now visible as a column within the Files tab in Tasks. | Provides clearer visibility of deliverable status directly within the Task, reducing the need to switch between areas. |
Attribute Indicator in Edit View | No clear visual indication of where Attributes were applied within Packages or Subpackages. | Displays visual indicators for Packages and Subpackages with applied Attributes. | Helps users quickly identify and manage Attribute usage during editing. |
Enhanced Icon Differentiation | Placeholders and files were not clearly distinguished visually, which could cause confusion. | Improved icon differentiation between placeholders and files. | Enhances clarity and reduces errors when working with deliverables. |
Column (Stage) Copy and Insert Options (with Tasks) | Stages could not be duplicated or repositioned easily, requiring manual recreation. | Allows full Stages (including Tasks) to be copied and inserted before or after existing Stages. | Speeds up Plan creation and improves flexibility in structuring workflows. |
Package Summary Fixes | Package Summary View could display inconsistent or inaccurate information in some cases. | Fixes applied to ensure accurate data display and smoother interaction. | Improves reliability and user confidence in summary data. |
General Bug Fixes | Minor issues across features impacting stability and usability. | Multiple bug fixes applied across Playbook features. | Enhances overall system stability, performance, and user experience. |
