Managing Defects (Unresolved Failed Item)

Modified on Tue, 25 Oct, 2022 at 7:25 AM

If a driver marks an item as 'failed' in a submitted checklist, the defect will appear in the 'Defect Management' dashboard under ‘Unresolved failed items’ table to alert you take action to resolve the issue.


You can open the individual defect by clicking on the red spanner icon next to any failed item. 


A pop-up box will appear to enable you to mark the item as resolved by ticking the 'Resolved' tick box, you can also add a comment to explain how this has been resolved. To update the status, select ‘Add Comment’



This will then mark the item as resolved and remove the item from the list of unresolved items.



Alternatively, should a defect take longer to resolve – any user with Company Manager permission on the account can add comments to the item by just adding a comment and selecting the ‘Add Comment’ to save. The defect will remain at unresolved status, but you can see an explanation as to why this is pending. 



This will the present a line in the audit trail for any other uses to view the defect status and history when clicking on the red spanner icon.

 

Once the defect is resolved you can tick the resolved tick box, add a comment and select the ‘Add Comment’ button to save.


The item will then be marked as ‘Resolved’ in the audit trail.


 


You can also click 'Detail' next to each defect line entry to view the full checklist. 




The item you enter the checklist through will be highlighted yellow, any other flagged defects will appear be highlighted red.



When viewing the defect in the individual checklist the icon will change from showing a red spanner icon at the unresolved status.

 


To a green spanner icon once resolved.



You can click on the spanner at any status to review the history.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article