Delete an Inspection and Delete a Repair Attempt

Deleting an inspection and deleting a repair attempt are controlled by the Delete Inspections and Repair Attempts role. See Change user’s roles for a database on how to edit users roles.

To delete an inspection in Chateau:

  1. Open the Inspection grid on the Inspection & Attempts tab.

  2. Query the Inspection grid.

  3. Select the inspection you wish to delete.

  4. Click the Delete Inspection button up at the top of the grid.
    • Note: Only one inspection can be deleted at a time.

  5. Enter the reason why you are deleting the inspection in the text box.

  6. Click Delete.

  7. Deleting an inspection will delete any AVO events and/or leaks created because of that inspection. It will also unsatisfy any inspection requirements satisfied by that inspection.

    This will cause the inspection requirement to be returned to the schedule or be reported as missed inspection if there is no future inspection that satisfies the inspection requirement. Deleting an inspection on a component will trigger the rules rerunning on all inspections occurring after the deleted inspection so Chateau can satisfy any inspection requirements, or trigger the opening of a new leak if needed.


To delete an attempt:

  1. Open the Attempts grid in the Inspections & Attempts tab.

  2. Query the Attempts grid.

  3. Select the attempt you wish to delete.

  4. Click the Delete Attempt button at the top of the grid.
    • Note: Only one attempt can be deleted at a time.

  5. Enter the reason why you are deleting the attempt in the text box.

  6. Click Delete.

 

It is also possible to delete inspections in Chateau Mobile. Please refer to the Chateau Mobile Training Manual for that procedure.

You can turn on the Deleted Inspections porch if you want to maintain a list of these deletions and provide feedback to technicians and users whenever this occurs.

  • Note: If a leak was created by an inspection on a misidentified component, instead of deleting the inspection, you can close the leak with “Comp Misidentified” as the reason.

Was this article helpful? If not, please submit feedback below.