Simple Check is very configurable, which allows you to configure checklists for your team setup and compliance goals.


Three simple questions will help you estimate your usage:


Visit the Plans page to select your plan and get started.


What do you need to log?

Think about your compliance requirements and configure Simple Check for your team's process. 


What will you be audited against? Whether a formal audit by an outside organization or an internal check, be sure your checklists are sufficient to pass your audit.


Does each space or person need its own log, or would a summary checklist be sufficient? 


How specific is the location information for each checklist? If building a space inventory or employee team list, needing to provide checklists for each tag of a large Location hierarchy will result in more checklists.


Reduce your team's effort by configuring checklists to contain only the items necessary. 


How will you use the logs?

Will the logs be looked at daily/weekly or only when necessary? Many individual checklists can be hard to summarize. 


Will the checklist results be sent to anyone? Do not combine checklist items or info that should not be viewed by someone else. 


Will tenants want to view the checklists, especially the latest timestamp? This will require a checklist to be completed for each space that tenant would look at.


Who will fill out the checklist?

Does the person who fills out the checklist have a mobile device? A checklist can only be filled out when using a mobile application, by a signed in user. 


The user who completes the checklist will appear in the log record. For your compliance record, can this be a supervisor in a summary checklist, or must it be the person that "did the work"?


Examples

See our Use Cases for other ideas!


Say you have a contract to clean 2 buildings, each with 3 floors, and each floor has 2 restrooms and 5 offices.


Depending on your compliance requirements, you could log these cleanings in a few different ways, depending on your answers for the questions above

  1. Per contract.  
    1. This would be a single checklist each time the Standard Operating Procedures (SOP) are executed, with very few items. Perhaps only one, "Did you complete the SOP?" 
    2. The location tree would not be necessary, or perhaps would only be a list of other contracted locations.
    3. Logs would only be visible when needed, perhaps monthly or quarterly when invoicing.
    4. The location supervisor would fill out the checklist.
    5. This could result in 31 checklists a month for daily cleaning.
  2. Per building or Per Cleaning Team. 
    1. This checklist will still reference against a SOP, and can have a small number of items to check like #1.
    2. The location tree would be a little larger, perhaps a first branch of Contract Locations and second level of Supervisor/Teams or the Buildings
    3. A QR codes at the entry of each building so tenants can see the last time the cleaning team was through.
    4. Logs might be looked at weekly, and the supervisor would fill out the checklist
    5. This could result in 62 checklists per month for daily building cleaning.
  3. Per space.
    1. This checklist would be driving by logging requirements, namely Restroom Cleaning Logs - Occupants Can Check Last Result. Any tenant can check the last time a space was cleaned.
    2. The checklist items will be the important cleaning questions, such as "was the trash emptied?" "are dispensers filled?" "High touch points disinfected using approved cleaner?" etc.
    3. Cleaners at each space will need a device to fill out the checklist, so the time stamps are up-to-the-minute.
    4. Cleaning could happen weekly for the offices, and up to 2 times daily for the restrooms. This could result in 30 offices 4x a month (120), and 12 restrooms 2x daily (720) for a total of 840 checklists each month.
    5. Logs in bulk will rarely be used as there will be many, but could be exported as needed.