Escalation Processes Clause Samples
The Escalation Processes clause defines the procedures for resolving disputes or issues that arise during the course of an agreement. Typically, it outlines a step-by-step approach, such as requiring parties to first attempt resolution through informal discussions, then escalating to higher management, and finally, if necessary, proceeding to formal mediation or arbitration. This clause ensures that conflicts are addressed systematically and efficiently, helping to prevent misunderstandings from escalating into costly or protracted legal disputes.
Escalation Processes. Where there are concerns operationally regarding any aspect of the protocol not being adhered to, resulting in poor practice; escalation should be enacted. Concerns must be taken to respective supervisors, if this fails to yield appropriate impact, then Heads of Service should be notified as a means of addressing matters. If needs be the Deputy Director must also be cited, if matters remain unresolved, leading to a detrimental impact on the well-being of a child.
Escalation Processes. 2.1 Upon registration of a software incident by the Customer’s nominated Representatives, the MSM Supplier’s Service Desk will attempt to provide an immediate answer. At this point, the person registering the software incident will receive an Incident Reference Number. If the software incident cannot be resolved immediately it will be referred to a MSM Supplier 2nd line Service Desk Analyst.
2.2 If a satisfactory response has not been received to the software incident, or a workaround provided, in accordance with the timescales detailed in the Response Timetable, it will be referred to the MSM Supplier’s Service Desk Manager. Thereafter, the MSM Supplier’s Technical Director is responsible for ensuring the software incident is dealt with satisfactorily.
Escalation Processes. Based on the priority of the requests/reports, NETCARE shall use the following internal escalation processes in general: · Priority 1: A problem report shall be processed immediately after receipt. The first preliminary status report to FME shall be due within one hour. FME shall be kept constantly informed on the progress until submission of the final status report. The recipients of the problem reports are defined in Attachment 3. · Priority 2: If no solution or workaround has been found for a problem within four hours after receipt, a specialist or the Second Level Support shall be entrusted with a problem solution. The first status report to FME shall be due after one hour. · Priority 3: If no problem solution or workaround is perceived by the First Level Support 24 hours after receipt, a specialist or the Second Level Support shall be entrusted with a problem solution. The first status report to FME shall be due after 24 hours. · Priority 4: Since no critical problem demanding immediate action has been reported, Second and Third Level Support will not be involved automatically. Only in case that the First Level Support fails to reach a problem solution independently the Second or Third Level Support shall be involved. The first status report shall be due after seven days.
Escalation Processes