Users can create and structure their Playbook Plans in Excel and import them into Playbook, rather than building them directly within the platform.
How Do I Download the Import Plan Sheet?
On your Playbook Dashboard, click + Create New Plan.
In the Create Plan pop-up, select Import Plan.
In the Import Plan pop-up, click Download the sample CSV file here.
The Excel sheet will be downloaded.
How Do I Fill in the Excel Sheet?
Open the Excel file.
Click Import Sheet in the Instructions tab, or select Plan_Data from the tabs at the bottom.
In the Plan_Data sheet, several columns are available.
Complete all fields in the Project Data section, as these are mandatory.
Complete all required columns in Plan Data.
Fore more information on these columns, see Plan Data Fields.
Return to the Instructions sheet.
Click Validate.
Any issues will appear in the Playbook_ValidationLog sheet.
Resolve the issues, and click Validate again.
Repeat this process until no errors remain.
For more information on the errors, check Errors.
Once validation is successful, a JSON file will be generated and saved in the same folder as the Excel file.
How Do I Import the JSON file into Playbook?
Access the Asite platform and open Playbook 2.1 Beta.
Click + Create New Plan.
Click Import Plan.
Click Click to choose file.
Select the generated JSON file from the local drive.
Once uploaded, click Save in the Import Plan pop-up.
Review and Finalise the Plan
Once the JSON file is uploaded, the Import Plan pop-up will display the full Playbook structure.
Select a Project to store the Plan.
Additional fields will become editable.
Update these as required.
NOTE: The Row Required and Column Required fields cannot be edited at this stage. These can be modified later within the Playbook matrix.
Click Save.
The Playbook will then be created and displayed.
Plan Data Fields
Column | Description | How to Fill |
Package | Defines the name of the Package being created in the Playbook structure.
This column is used for all hierarchy levels, including Packages (level 0), Subpackages (level 1) and Subpackages of Subpackages (level 2). | Package (Level 0): Enter the name and leave the Parent Package column empty.
Subpackage (Level 1): Enter the name and reference its parent in the Parent Package column.
Subpackage of a Subpackage (Level 2): Enter the name and reference Level 1 Subpackage in the Parent Package column. |
Parent Package | Defines the hierarchal relationship between items. | Package (Level 0): Leave empty for top-level Packages.
Subpackage (Level 1): Enter the name of the Package it belongs to.
Subpackage of a Subpackage (Level 2): Enter the name of the Subpackage it belongs to. |
Package Start Date | The date the Package is expected to commence. | Enter in DD/MM/YYYY format. |
Package Due Date | When the Package is expected to conclude. | Enter in DD/MM/YYYY format. |
Package Owner (Email ID) | The email address of the person responsible for managing the Package and ensuring completion. | Enter a valid email address (e.g. name@company.com).
|
Discipline | The row header the Package will be assigned to in the Playbook matrix. | Enter the required Discipline name. |
Stage | The column header the Package will be assigned to in the Playbook matrix. | Enter the required Stage name. |
Stage Start Date | The date the Stage (column header) is expected to commence. | Enter in DD/MM/YYYY format. |
Stage Due Date | The date the Stage (column header) is expected to conclude. | Enter in DD/MM/YYYY format. |
Errors
Errors may appear during validation. Refer to the table below for descriptions.
Error Colour | Description |
 | Value not in a valid date format. |
 | Value contains invalid special characters (|<>#) or mandatory fields are not completed. |
 | Parent Package value does not exist. |
 | Value does not match the Parent Package value. |
 | Invalid date or missing date (format: DD/MM/YYYY). |
 | Invalid email address. |
 | Invalid Package or Parent Package. |