I totally agree Jonny — there’s huge potential for labels across the platform to connect various elements and bridge any gaps in analysis and reporting, particularly in supporting teams to quickly identify areas for improvement and track leading and lagging indicators more effectively. I shared this internally and can say that it’s an exciting direction that we’re moving towards  

I have just been speaking with a support advisor from SC and it is apparent that when i speak about labels then at first they do not know what i mean.

Then i explain what i am looking for and they start to show me exactly what i already know.

To me and surely the community the following is logical.

• Actions raised -Label option is available
• Issues raised -Label should be available as an option
• Templates - The Label option should be available
• Training - The Label option should be available
• Heads Up - The Label option should be available
• Credentials - - The Label option should be available
  
  I believe this is a quick win as a company creates and expands the number of unique labels. When looking at gaps, trends and improvements then surely this is a great way across the whole platform to find things that need to be improved.
  
  It is even irrelevant what location or site it is as long as the labels are applicable.

I use labels a lot and it makes it much easier to sort and filter inspections and actions. Labels for other applications would definitely be useful.

We actually don’t use labels yet, but I like the potential for them. So this comment may be complete off from what the tool is meant to be/do. But something I would love is to be able to assign a label or a tag to sites (for example, whether a site is a restaurant or a store or a ride). From there, at least two things come to mind that would be really helpful: 1) being able to assign users based on a label within a location (for example, a Foods leader for Area A can see all sites labeled with “restaurant” within Area A), and 2) the ability to set up logic in templates based on site labels, similar to how Asset selection can be limited to certain types (for example, a Foods template would only show sites labeled “restaurant” for selection, even if the auditor has other sites available to them).

Going even further, it would be amazing if sites could have fields or more specific tags that could then be tapped into for logic within templates. To continue with the Foods example, a restaurant could be tagged with certain things like whether it has a back dock or a kitchen. Then a generic template for all restaurants could include back dock and/or kitchen questions that only display if a location with a back dock and/or kitchen is selected in an inspection. While it would mean lots of configuration to set up, it would prevent users from having to answer whether their location has a back dock/kitchen to see those questions, and potentially selecting “No” when in fact they do.