Overall Checklist Notes | OpsAnalitica University

When building Checklists, they do not auto-save, so make sure you are saving often.
When building Checklists, be mindful of how many questions you are putting in a category. There are tons of buttons and switches on the questions and if you put too many in one category it will eventually slow your browser down to a crawl. Try to use more categories.
- Also, close categories when you are not using them, this will free up memory and keep your browser snappy.
Building Checklists is a cut-and-paste game.
- We build the checklists first in a spreadsheet and then cut and paste them into the platform.
- When you are building a checklist, take extra time on the first couple of questions or the first of every type of question to ensure that you have it configured perfectly.
- Then you can just cut and paste that perfectly configured question down and change the question text.
When it comes to using colors for questions, whether it is the foreground or background, it is best to know that we use the # 6-character letter color hex codes
- This way you can search the color on the web if you would like, or you can manually use the clicker and select the color you like.
- If you are going to color code alternating questions, like an excel template, just make sure the checklist is set in stone before you start coloring. If you add a question later, you will have manually adjust the coloring on every question below.
Once a checklist is submitted, you are unable to change the responses. You can add notes and tasks, but you cannot change what was submitted
- To learn more about why this is, please see our FAQ

Editing Question Text

Bold, Indent, Underline
Bullets: Number and Text
Links: We allow you to hyperlink to an outside url within the question text.
- This could be a shared document, video link, webpage, etc.
Photos: We allow you to upload screenshots or photos and put them into your checklist questions.

WE DO NOT ALLOW YOU TO UPLOAD FILES INTO CHECKLISTS. THIS IS BECAUSE CHECKLISTS NEED TO BE AVAILABLE OFFLINE AND THEY GET DOWNLOADED AND STORED IN THE APP. LINKS AND PHOTOS ARE HOW YOU CAN ADD MORE CONTENT TO A CHECKLIST.

Required Fields on Checklists and Checklist Questions

Field	Required/Not Required	Explanation
Category	Not Required	This allows you to put similar checklists in similar categories. Ex: you could put all the above store checklists in their own category and all the daily checklists in another. The biggest benefit of using categories is on the Checklists Dashboard where the checklist stats are rolled up by category.
Title	Required	Name of the Checklist
Status	Required	Active means the checklist is visible to end users. Inactive means the checklist and its results are not visible to end users. You should leave a checklist inactive while building and use a Location Filter to send it to a corporate or test location. This will allow you to test the checklist before releasing it to the field teams.
Inheritable	Not Required	By checking this box you will make this checklist available to be worked by your descendants.
Tags	Not Required	These tags show up in the Checklists List in the Admin portal to give you more information on the checklist. These tags also appear on the Checklists Dashboard.
Location Filter	Not Required	If you select a Location Filter for a checklist, the checklist will only be visible to those locations.
Show Scores	Not Required	By checking this box you will show the current score of the checklist to the End User that is completing the checklist. This should only be used by people who understand that the truth is more important than the score. The score will drive behavior and you will see more 100% and A's and your data quality will suffer. Don't do this unless you are giving it to an auditor and expect the score to change behavior and cloud data.
Delete Responses After	Not Required	By entering a number into this box, you are telling the system to delete response sets, completed checklists, automatically. If you enter 90 into this box. The platform will only keep the last 90 days worth of data and it will automatically delete any response sets older than 90 days every night. Remember, deleted data is gone forever, it cannot be retrieved. You should only use this setting if you don't want to keep data around. Ex: this was invented for a client that didn't want to hold compliance data for more than 90 days to limit risk exposure and law suits. Every night we delete the older response sets.
Notify On Complete	Not Required	You can apply a user filter to this box. Every time this checklist is completed, the platform will look at the User Results in the Notify on Complete User Filter. It will then evaluate the User Results from the Location where the Checklist was completed. It will find the Users on both result lists and it will message them to let them know the Checklist was Completed. This is good to use on Checklists that aren't done every day, like an audit, or for checklists where someone outside of the location needs to be notified this was Completed.
Notify On Late	Not Required	You can apply a user filter to this box. Every time this checklist is not completed before its scheduled To Time, the platform will look at the User Results in the Notify on Late User Filter. It will then evaluate the User Results from the Location where the Checklist was completed. It will find the Users on both result lists and it will message them to let them know the Checklist is late. This provides a real-time notification when an important checklist is late and will notify the users who opt into this notification. It will allow them to follow up same day vs. finding out about a missed checklist after it is too late to complete.
Notify on Critical	Not Required	You can apply a user filter to this box. Every time this checklist is completed, the platform will look to see if there were any critical violations on this response set and it will send out a Critical Violations Notification. The platform will look at the User Results in the Notify on Critical User Filter. It will then evaluate the User Results from the Location where the Checklist was completed. It will find the Users on both result lists and it will message them to let them know about the critical violations This is good to use on Checklists that have compliance and safety implications that could hurt the business. This is also good for identifying issues that need to be resolved immediately.
Sections	Not Required	Sections are the way to organize large checklists. Sections don't show up in the scoring. They break up large checklists and make them more manageable to complete. When a checklist loads it only displays the current Section, you have to use the left-hand navigation bar to click on the next section to load it. You can only be in one section at a time. It is a best practice to put a No Response Question at the bottom of each Section telling people how to navigate to the next Section. It is a best practice to put 1 required question at the very end of the checklist that says to Double Check that you have answered every question and you are ready to submit. This will stop people from clicking Done at the end of the first Section and submitting the Checklist before they completed it. It is a best practice to require more questions on Checklists with Sections to prompt users to not skip any because they don't see them in other sections.
Categories	Required	Categories are how you group similar questions. Categories are required to have Questions. Close Categories when you are done editing them to speed up the browser. Don't put too many questions in one category or it will slow down your browser.
Questions	Required	These are the Questions you are asking. You can only have Questions in a Category.

Next Section