Configuration ‣ Anomalies

The various Configuration ‣ Anomalies menu items allow you to create, edit and delete Checklists, anomaly and finding Codes, anomaly and finding Code Categories, anomaly Priorities, anomaly Sets, anomaly Severities, and anomaly Statuses.


You can tie checklists to Findings, such that when an inspector raises a finding, they are reminded to carry out the items on the checklist.


Findings and Anomalies can be given a Code, describing their type.

Code Categories

Are used to group Codes. If your database contains different kinds of data, for example some below-water and some above-water data, you might like to create one Code Category for “Above water” and another for “Below water”.


Anomalies can be given a Priority.


Anomalies can be grouped in Sets.


Anomalies and Findings can be given a Severity.

When you set up Anomaly Triggers on fields, you can specify a Severity. You can set several triggers on a single field, with a variety of different severities. If that anomaly trigger is violated on an event field, a finding of that code and severity will automatically be created. Severities let you equate dissimilar problems: you can decide that a problem in one field is of the same severity as a problem in a different field.


Anomalies can be given a Status. This intended to convey the current situation with the anomaly: “Rectified - Closed”, “Not Anomalous - Closed”, “Monitor”, “Temporary Repair”, etc.

Action Status

Anomaly Actions can be given a Status. This intended to convey the current situation with the action. The default action statuses are Approved, Assigned, Completed, Proposed, and Rejected; but you can customise these to meet your needs.

Action Types

Anomaly Actions can be given a Type. This lets you specify an event type to be associated with an Action Type. When a Task is created from an Anomaly Action, then the Event Type of the Task is determined by the Event Type associated with the Action Type.