HS Logbook ASC: Task List Best Practice

Introduction

Designing a Task List that works for all the supported platforms (web, iOS iPads, iPhones, Android tablets, and phones) can be challenging. Before designing your Task List, we recommend that you consider the following tips/best practices to make sure the Task Lists that you design are easy to understand and use. We hope this list will reduce the time it takes to create and maintain your Task Lists.

Note: Task Lists are created in the Above Store Console. If you do not have ASC access, please reach out to your Corporate office.

• Task List Naming Convention
• (A) Task List Name
• Add a descriptive Task List Name to easily identify and differentiate the Task List.
• Consider appending a short shift or station description to the Task List name to uniquely identify the differences between task lists.
• (B) Task List Description Field
• The description field is intended to help you better identify a Task List and will only be seen by yourself and other ASC Users. We recommend that you add a description explaining who the Task List applies to and the frequency that the task list will be scheduled (e.g. Daily Temperature Log - Amarillo Store).
• (C) Schedule
• The Completion Schedule will drive the number of instances that a Task List will be available within a selected duration. We recommend that you keep the Schedule Name simple to describe the frequency (e.g. daily, 4-6PM). 

• Task List Design Layout
• We recommend that you have 6-8 columns per Task List.  
• We also recommend that you have 60 or fewer task rows. Consider organizing your Task Lists by position, station, or shift for better chances of completion and faster Task List load times.
• For task rows, the first column should always have a label to give users a description of the adjacent controls on the row.
• Also on task rows, each control should have an adjacent label located to the left of the control.
• Any time you increase, or decrease the width of a column, you do so in increments of 5% of the width of the entire Task List.  With that being said, we recommend that all columns be at least 10% (or 2 clicks), with a preference of 15% (3 clicks).
• Possible Exception: Columns that contain simple checkboxes with very short column headers.

• Task List Controls
• Labels
• We recommend that labels with descriptions longer than the column width have the Allow Text Wrapping option turned on for easier readability.
  
  

• For longer label descriptions consider using instructions instead of labels whenever it makes sense since instructions span across all columns.
• Instructions
• Consider using the instruction row control whenever additional guidance or an explanation is necessary to complete a specific row.
   

• N/A Button Control
• Consider using NA buttons for tasks that may not be applicable under certain situations. 
• Temperature Controls
• If there is a chance that Bluetooth will be used to complete the Task List, the column width should should be at minimum 15% (3 clicks)  This will accommodate for the Bluetooth indicator and Bluetooth button that is added when the Bluetooth thermometer is paired.
• You can learn more about Bluetooth pairing with Logbook here.
• If there is a need to alert appropriate users that a temperature value is out-of-tolerance, we recommend to always include a minimum and maximum value.  
• e.g. Water Boiling Point should be 100° we recommend to set a min. value of 100° and a max. value of 500°.
  
  

• Number Controls
• Only include min./max. values when necessary
• Text Entries
• Assume text entries are optional unless there is a requirement for completion
• Headers, Sub-headers, and Spaces
• Consider using Headers, Sub-headers, and Space controls to help break Task Lists into categories or sections. 

• Task List Structure
• Consider duplicating Task Lists by shift for higher chances of Task List Completion and Reporting
• Consider using custom tags if a certain task does not apply or apply to a block of locations
• e.g.  Drive Thru, restaurants in a mall