This document covers the following topics:

• Scheduled Status & Scan Status MATCH
• Scheduled Status & Scan Status DO NOT MATCH
• Compliancy by Date
• Compliancy by Person
• Compliancy by Card

Once you understand what each 'Status' means, you can begin to assess whether your organization is, or is not, compliant.

The 'Scheduled Status' and 'Scan Status' MATCH

Where the 'Scheduled Status' and the associated 'Scan Status' match (show the same status colour) there is little more you need to do to investigate.

• Example 1: The 'East Work Yard' has been closed for maintenance. As such, no Wallet holders have been scheduled to be dispatched to this site resulting in a 'Not Scheduled' status.
  
  The relevant 'Scan Status' displays a result of 'No Scan', indicating that there were no Wallet holders scanned by a Worksite admin associated to that site. 
  
  
  
  
• Example 2: The 'South Work Yard' is showing 'Compliant' within both the 'Scheduled' and 'Scan' status sections.
  
  This indicates that all Wallet holders that were scheduled for the site had the the relevant mandatory card requirements within their Wallet when the pre-qualification record was created and that each Wallet scanned by an admin associated to the site was also compliant. 
  
  

The 'Scheduled Status' and 'Scan Status' DO NOT match

Where the 'Scheduled Status' and the associated 'Scan Status' do NOT match (do NOT show the same status colour) it is recommended you complete some further investigation. 

The system provides you with the ability to drill down into the record to determine which Wallets were scanned by a Worksite admin. For more information on 'Investigating Site Compliancy' click here. 

• Example 1: The 'West Work Yard' is displaying a 'Scheduled Status' of 'Not Scheduled' indicating that no Wallet holders were scheduled for this site on the relevant date. 
  
  However, the associated 'Scan Status' is displayed as 'Compliant' indicating that while there were no Wallet holders scheduled, the Wallet holders that were scanned into the site had the necessary qualifications within their Wallet. 
  
  
  
  
• Example 2: The 'North Work Yard (Remote)' is displaying a 'Scheduled Status' that is 'Compliant' indicating that all Wallet holders that were scheduled for the site had the the relevant mandatory card requirements within their Wallet when the pre-qualification record was created.
  
  However, the associated 'Scan Status' warns that a Wallet scanned by a Worksite admin via the Field Scanner app did NOT meet those same requirements and should be investigated further. 
  
  

Investigating Site Compliancy

Regardless of the 'Status' outcome, you can drill into each record to determine the:

• Compliancy by Date - Provides an overview of the site compliancy status for each date within the selected date range. 
  
  
• Compliancy by Person - Provides a summary of who was, and who was not, compliant on a relevant date. 
  
  
• Compliancy by Card - Provides an overview of the compliancy status of the cards and certifications contained within a Wallet as they relate to the mandatory card requirements established for the relevant site. 

Compliancy by Date

1. Select the relevant 'Site' to view the details:
   
   
   
   You will be presented with some general details of the 'Site' along with the 'Compliancy by Date' section. Here you can review the site compliancy status for each date within the selected date range.
   
   
2. Select a 'Date' entry to view it in greater detail:
   
   
   
   

Compliancy by Person

You will be presented with the 'Compliancy by Person' sub-section. By default, only non-compliant results will be displayed.

1. To include compliant results also, select the 'Include Compliant?' toggle such that it is enabled:
   
   
   
   
2. You will be presented with a summary of who was, and was not, compliant on the date selected.
   
   In the example below, we can determine that:
   
   Contract Worker - Had the relevant mandatory card requirements within his/her Wallet when he/she was scheduled for the site (when the pre-qualification record was created) and had a compliant scan result via the Field Scanner app.
   
   Union Member 2 - Had the relevant mandatory card requirements within his/her Wallet when he/she was scheduled for the site (when the pre-qualification record was created) but was not scanned on-site via the Field Scanner app. 
   
   Union Member 1 - Was not scheduled for the relevant site. However, the 'Non Compliant' scan status indicates that when the Wallet was scanned via the Field Scanner app, he/she received a non-compliant result and were turned away. 
   
   
   
   
3. Select an entry to view the details for a relevant Wallet holder:
   
   

Compliancy by Card

You will be presented with the 'Compliancy by Card' sub-section. By default, only non-compliant cards will be listed.

1. To include a listing of compliant cards also, select the 'Include Compliant?' toggle such that it is enabled:
   
   
   
   
2. Here, you can determine which cards within the Wallet were, and more importantly, were not, compliant with the requirements of the relevant site:
   
   
   
   In the example above, you can determine that the 'Non Compliant' scan was the result of (2) mandatory card requirements that were missing from the Wallet as demonstrated by the 'Does Not Exist' notification within the 'Issued Date' column.