Checklists in AutoTask

Checklists in AutoTask

Important Caveats


Because you're responsible for items that you check off in Autotask checklists: 
1. Do not check off an item unless you personally completed it or you personally verified it was completed. 
2. Always check off the item if you completed it or you personally verified it was completed.`

Alert
Once you check off an item, your name is attached to it on the ticket's checklist. 

How to Access Checklists in Autotask

From the Checklist Library

Checklists can be added to a ticket from the checklist library. Some checklists are already included as part of a ticket template. If a checklist is part of a ticket template, the checklist will automatically be added when a ticket is created from that template. 

All the checklists that are available to be added to a ticket are visible in the checklist library: Left hand menu>Admin>Automation>CHECKLISTS & TEMPLATES>Checklists.

Info
You must have Autotask permissions set to view or edit the checklist library. If you need access to the library and don't have it, please ask Roberta.

Even if you don't have direct access to the checklist library, you can add a checklist from the library to a ticket. The checklist choices change based on the ticket category. If you don't see the checklist you need for the ticket category you are using, ask Roberta to make that checklist available in that category. 

In a Ticket Template

To view a checklist that's part of a form template:  
  1. Autotask left-hand menu > click Admin 

  1. Click Automation then click Form Templates and you’ll be able to see each template and view any checklists items attached to it.



Helpful tip: Add the checklist library and other frequently used items to your Autotask Favorites to access them quickly. 


How to Approach Checklists

Note: Many of these items apply to technicians, but it is helpful for administrative personnel to understand them. 
  1. In general, checklist items should be completed in the order they are listed. (There may be special circumstances where this isn't always possible, but this is the goal.)
  1. Don't change a ticket status to Complete without first checking off all the checklist items. If you change the status of a ticket to Complete without all the checklist items being checked off, a workflow rule will automatically change the ticket status to Follow-Up Needed.  
  1. If an item in a checklist is not applicable to that particular ticket and therefore will not be completed, prepend the item with "NA: " or "Not Applicable: " before checking it off. That way anyone looking at the ticket in the future will know that this task was not performed. If necessary, in order to clarify, add a note in the ticket or time entry explaining why the item was not applicable (e.g., it required installing a piece of software the user didn't need). That way anyone looking at the ticket in the future will know why this task was not performed. If the note is brief, you can instead prepend it to the checklist item. 
  1.   If an item in a checklist was completed prior to the creation of the ticket (e.g., a machine already has a piece of software installed because it was used by a previous user),  prepend the item with “PC: ” or “Previously Completed: ”
  1. If  work on a ticket cannot be completed (e.g., in a situation in which the customer does not respond after repeated attempts) and you want to change the ticket status to Complete, you will need to check off all the checklist items. If you don't (as mentioned above) the ticket status will change to Follow-Up Needed when you try to "Complete" it. Before checking off the remaining items , prepend the item with "NCTC” for "not completed, ticket closed."  This is only to be used for tickets that we are closing without finishing the ticket work. A note should be added to the ticket stating that the work was not completed and the reason why. 

Warning
Please do not delete checklist items from the ticket. If you notice that a checklist item is continually not used, please discuss it with Roberta. We may need to edit the library (permanent) version of the checklist for future use.

  1. If you're working on a user's machine, when possible do "front end" items first so computer access can be returned to the customer while you work on items from the back end. When you stop work, whether the checklist is completed or not, let the user know so he can get back on his computer. There is a note template available for this purpose in Autotask:  NYGG-283T. See also: List of Note Templates in AutoTask (Partial).

  1. Make sure to read the checklist item fully; there can be more than one action in each item. (If the checklist is long this may be unavoidable because there is a limit to the number of items that can be contained in a checklist. When creating shorter checklists, it's advisable to break each step in to a separate checklist item.)
 
  1. Always look for improvements to the checklist that can be added to the checklist in the Autotask checklist library. Because the checklist libraries cannot be automatically backed up, before editing the checklist in the checklist library, it's best to discuss any changes with senior staff first.) 

  1. Ideally you should complete all checklist items on a ticket in one session unless this is not possible (e.g., you’re waiting for a device to show up in a dashboard to complete another step). If this is consistently unrealistic please discuss it with the appropriate team member, as we may to allot more time in the schedule for certain tasks. 

  2. If you can't complete all applicable checklist items at once, create an internal ticket note clarifying why the checklist items could not be completed. If you need to connect to the machine on the front end, schedule with the user so user can be off the machine. If you are having trouble reaching the user, ask the Office Admin to coordinate the appointment and set the ticket status to Follow Up Needed - Office Admin. If the work can be done on the back end, you are responsible for scheduling yourself to finish the work within a realistic time frame. The bottom line is that if you are assigned the ticket as primary resource, you are responsible for getting it completed promptly.


  1. When working on a ticket with a checklist, there still needs to be a time entry to account for the time you spent working on the checklist. The checklist is not a substitute for your ticket time entry. It is acceptable for your time entry to say something like, "performed steps as indicated in the checklist." Do not use the word “completed” ("completed checklist items") unless there are no more open checklist items left on the ticket. It’s confusing because it’s unclear if you completed the whole checklist or just some items. Instead say something like, “performed steps according to the checklist,” unless the entire checklist has been completed. 

  2. For onsite assignments, checklists help us confirm everything is done before leaving the site. For onsite, either print the checklist (you will need to go back later and check off the items in the ticket) or just open the ticket on your laptop/tablet. Try to check off items in real time to make sure they are actually completed and you don't leave anything out.


Alert
Check off items in real time as you complete them to make sure you don't leave anything out.


    • Related Articles

    • Entering Ticket Time Entries in AutoTask

      This article is about ticket time entries. This is not about task time entries. The purpose of the time entry is to: document time spent on assignments, help us decide what to bill the customer for, justify the charges to the customer document ...
    • General Info on How Mission Control Works with AutoTask

      The information below is provided for technical reference. Most team members won’t need to review it, but it’s included here for informational purposes. Checklists get sent over but checked items on their side will not show as checked on our end. ...
    • List of Note Templates in AutoTask

      Here is some info about Autotask Notes to start with. Once you understand notes, you'll find it helpful to be familiar with note templates. Notes are a type of form template in Autotask. Here are some of the more common note templates we use. Not all ...
    • Merging Contacts in Autotask

      From the left-hand menu of your Autotask Dashboard click on Admin. Click on "Features & Settings" tab, then called "Accounts & Contacts" Under the "Utilities" section, there should be an option for "Contact Merge" Once you select that, a new window ...
    • Send a "to do" ticket assigned to a specific tech to AutoTask via email

      Anyone with an internal email account can send a ticket from the nygeekgirls.com email to NEWTICKET@geekgirlsIT.com: The ticket subject must include the tech's first name (or in the case of a temporary employee, the employee's user name; e.g., ...