Question
- How is the VPASS score calculated?
- Why is my VPASS score this number?
Overview
Disclaimer
If your company is a part of a TPA or franchise please note that VPASS Calculates separately for both Program and Local jobs. Your VPASS-P (Programs) is generated from the completion of Program Compliance Tasks originating from ADMIN-generated jobs only. Likewise, your VPASS for local jobs is generated from the completion of Work Flow Builder Compliance tasks controlled locally through the Work Flow Builder. Please reach out to your franchise or TPA for more questions regarding your VPASS-P score.
VPASS, or Value Progression Adjusted Sigma Score, is a scoring system based on the Six Sigma methodology of tracking opportunities for success, which can both succeed and fail. VPASS allows for the placement of higher levels of value on more critical business needs, while also progressively adjusting scores for degrees of failure. VPASS Scores are calculated and updated every night, so every morning has the potential for a new and better score!
VPASS Calculations
A VPASS Score is calculated based on taking the total number of opportunities for compliance metrics that were completed on time and comparing them to the number of late compliance metrics. When tasks are completed on time, your score will rise. Simple as that. As you constantly prove that your company is compliant with all tasks, these successful opportunities will continue to positively affect your score. Late compliance metrics are penalized by considering two pieces of information: the level of lateness as well as the priority.
Lateness
See this article for more information about pausing compliance tasks - Pausing a Compliance Task
- Level 1: If a task is completed anywhere from the moment a task is late until it is 20% late, it is a Level 1. For example, if you have 1 hour to complete a task and you complete the task within the first 12 minutes after the initial hour has past, your task will be a Lateness Level 1.
- Level 2: If a task is completed between 20% - 45% late, it is a Level 2. For example, say you have 1 hour to complete a task: if you complete the task between 12-27 minutes after the time it is due, your task will be a Lateness Level 2.
- Level 3: If a task is completed between 45% - 75% late, it is a Level 3. For example, say you have 1 hour to complete a task: if you complete the task between 27-45 minutes after the time it is due, your task will be a Lateness Level 3.
- Level 4: If a task is completed later than 75% of its due time, it is a Level 4. For example, say you have 1 hour to complete a task: if you complete the task later than 45 minutes after the time it is due, your task will be a Lateness Level 4.
Priority
The next factor taken into consideration is the Priority of the task. Task priorities are set by the Program Requirement settings, whether the program is a standard program or a client program. The Priority can be one of 4 levels, each of which causes a greater penalization to the Provider.
The priorities are as follows, and each holds an increasing value in penalization: Low, Medium, High, and Critical.
So for example, if you have a High priority task that was to be completed in four (4) hours, and it was completed in 5 hours and 20 minutes, your task will be penalized as a “Level 2 High”, which will not as severe as a Level 2 Critical, but is more severe than a Level 2 Medium and a Level 2 Low.
Exceptions
There are two types of exceptions that will now be tracked for compliance metrics:
- Exceptions for late service standards
- Exceptions for service standards that are no longer applicable.
Exceptions for late service standards will apply to service standards that are missed for valid reasons but will still need to be completed. For example, during the initial customer contact, some customers will ask to schedule the inspection for the following day. If a service standard dictates that the inspection is within hours of the customer contact, this will result in a missed service standard.
Exceptions for invalid service standards will apply to service standards that will not be completed because the task in question is no longer applicable. For example, a contractor might arrive onsite after customer contact only to find out that another contractor has been assigned to a claim and is currently performing mitigation services. At this point, the Date Contacted will have been entered into Admin, and the service standard for ”Arrive Onsite” will have been created. However, this task is no longer applicable because there is no reason for the inspection to take place
See this manual for more information about VPASS - VPASS Manual
Questions? Contact Us!