A report may be escalated, which represents the requirement to get additional levels of approval prior to being finalised. Some reports will make this mandatory prior to finalisation, but any report can be optionally escalated.
Escalate To
Only the Primary Lead may create an escalation for the report. Once escalated, the report will become read-only to all users except the individual to whom it is escalated.
The escalation can initially be to an individual or team as follows:
Individual
If escalated to an individual, that individual will be notified. Only that individual will be able to edit the report until the escalation is finalised.
The individual will be the only person who can edit the report and update the escalation status (see below).
Team
If escalated to a team, all managers of that team will be notified. No one will be able to edit the report and update the escalation status until the escalation is assigned to an individual user.
Admins and project managers of the owning organisation may reassign the escalation user to anyone. Other users may only reassign the escalation to a user belonging to the team specified.
Mandatory Escalations
Certain reports will mandate an escalation prior to being able to finalise the report. This logic is on a report by report basis as follows:
Environmental Report
The environmental report requires an escalation if certain questions (as pre-determined) are answered.
Status
The escalation can only have its status changed by the user to which it is allocated. If the escalation is allocated to a team, an individual will need to be selected prior to any update to the status being made.
In Progress
The escalation user can mark an escalation as in progress, this simply lets everyone know that the escalation is underway.
For the escalation user, it will also stop the escalation showing in the Dashboard Notifications area. It will continue to show in the Dashboard Escalations area until it is cancelled or resolved.
Cancelled
This can be set to indicate the escalation has not, and will not be dealt with. It restores the report to its original state, noting that if the report required a completed escalation, it will now require another escalation to be raised.
When cancelling, the user is prompted to add a description which can be used to document the reasons for cancellation. This reasoning will become read-only once the ‘cancel’ button is pressed.
Note an escalation cannot be edited after it is cancelled, instead a new escalation must be raised.
Resolved
Resolution indicates successful completion of the escalation process.
When resolving, the user is prompted to add a description which can be used to document the reasons for successfully resolving the escalation. This reasoning will become read-only after clicking the ‘resolve’ button.
Some reports have conditions that must be met prior to successfully resolving an escalation. If this is the case, on clicking the resolution button an error message will be displayed stating what is required to be done in order for the escalation to proceed.