Managing On Hold and No Access Inspections
When you've got a lot of inspections to manage, it could be easy to lose track of the ones that are problematic and waiting for a resolution to a no access issue.
You don't want to spend your time accessing each inspection to check no access reasons. You want to easily view the inspections and reasons at a glance so you can get issues sorted and get the inspection process moving again.
The Web Console's inspection list makes it easy for inspectors and managers/underwriters to separate out responsibility for resolving no access issues. No Access inspections are split into 2 categories:
- On Hold - displays those inspections assigned a no access reason that the inspector can try to resolve before any escalation is required.
- No Access - displays those inspections assigned a no access reason that require intervention from a manager or the underwriter.
On Hold Inspections
To view those inspections that have an On Hold status, press the On Hold button in the Inspections Menu:
This will filter your inspections and only show inspections that are 'on hold' and the issue can be resolved by the inspector.
No Access Inspections
To view those inspections that have a No Access status, press the No Access button in the Inspections Menu:
This will filter your inspections and only show inspections that are in No Access state and waiting for a manager or underwriter to resolve the issue.
Viewing and Filtering of Inspection List
Furthermore, there's enhanced viewing and filtering of No Access reasons with:
- No Access reasons displayed in the Inspection List. So no more going into each inspection overview page to find the reason! It's clearly displayed in the list:
- A 'Filter by Access Status' dropdown in the On Hold and No Access list pages, allowing you to display only inspections assigned a certain No Access reason:
Want to learn more about No Access and On Hold Inspections?
How does a No Access reason affect the status of an inspection?
How can I view inspections that have a No Access reason logged?