Playbook 2.3
Playbook 2.3
This release introduces Playbook 2.3, expanding Playbook with enhanced Task verification, Template management, reusable Attributes, and greater control over the Plan lifecycle.
Feature | Playbook 2.0 (Previous Model) | Playbook 2.3 | Why This Matters |
Reopen Completed or Verified Tasks | Tasks marked Completed or Verified could not be returned to the Task Owner for further work through the verification process. | Users with the Can Verify Task permission can reopen Completed or Verified Tasks when additional work is required. Reopened Tasks return to the Task Owner and can be completed and verified again. Previous completion and verification records are retained in the Task history. | Supports rework without losing the previous completion or verification record, maintaining a clear history of Task progress. |
Manage Attributes at the Template Level | Attributes and Attribute Sets could not be created and managed directly within Plan Templates for reuse in cloned Plans. | Authorised users can create and manage reusable Attributes and Attribute Sets within Plan Templates. When a Plan is cloned from a Template, these configurations are included and become independent of the source Template. | Reduces repeated configuration when creating Plans from Templates while allowing Attributes to be managed independently after cloning. |
Template Manager Role | Template management was handled through existing Playbook roles without a dedicated Template Manager role. | A dedicated Template Manager role allows users to manage assigned Plan Templates, including Packages, Tasks, dependencies, and Template revisions. The role does not provide management access to Plans created from those Templates. | Separates Template management from active Plan management, providing more targeted control over Template responsibilities. |
Playbook 2.2
Playbook 2.2
This release introduces Playbook 2.2, adding a controlled Task verification process and new Plan lifecycle statuses for greater visibility and control over Plan progress.
Feature | Playbook 2.1 (Previous Model) | Playbook 2.2 | Why This Matters |
Task Verification | Tasks could be completed without a separate verification stage or designated Verifier. | The Can Verify Tasks permission allows designated users to verify completed Tasks. Package Owners can assign a Verifier during Task creation to provide an independent review of completed work. | Introduces a controlled verification stage and maintains a clear audit trail between Task completion and verification. |
Plan Lifecycle Statuses | Plans did not have Draft, Open, Overdue, and Closed lifecycle statuses. | Plans can move through Draft, Open, Overdue, and Closed statuses. Plans automatically become Overdue after the due date, while authorised users can close or reopen Plans as required. | Provides clearer visibility and control over the Plan lifecycle and prevents further changes when a Plan is Closed. |
Playbook 2.1
Playbook 2.1
This release introduces Playbook 2.1, improving Plan authoring with row copy and paste functionality, clearer file revision visibility, and an updated Plan selection experience.
Feature | Playbook 2.1 (Previous Model) | Playbook 2.2 | Why This Matters |
Copy and Paste Rows Across All Disciplines | Complete rows could not be copied and pasted across all disciplines within the Playbook Matrix. | Complete rows can be copied and pasted within the Playbook Matrix across all disciplines. | Reduces repetitive manual entry when creating or updating similar Plan content. |
Revision Column in Files View | File revision information was not displayed directly in the Files View, requiring individual files to be opened to view revision details. | A Revision column displays document revision information directly in the Files View. | Provides quicker visibility of file revisions without requiring individual files to be opened. |
Updated Plan Selection Interface | The Select Plan dropdown used the previous interface design. | The Select Plan dropdown has been updated to align with the approved interface design. | Provides a clearer and more consistent Plan selection experience across Playbook. |
Playbook 2.0
Playbook 2.0
This release introduces Playbook 2.0, replacing key limitations in Playbook 1.0 and introducing improved structure, configurability, and workflow control.
Feature | Playbook 1.0 (Previous Model) | Playbook 2.0 | 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. |
Row and Column Header Action Menus | Row and column header actions were not available.
Users could not directly edit, insert, colour-code, or apply attribute sets from the grid headers. | Three-dot action menus are now available on row and column headers, giving users options to edit details, customise colour, insert rows or columns, apply attribute sets, and delete where available. | Added control directly from the grid, making plan setup and updates faster and easier. |
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. |
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. |
