49A.2.1 As soon as possible after a Service Event has been notified to the Helpdesk or after Sub-hubco has itself or by a Service Provider become aware of a Service Event, if it considers that the Service Event was caused by malicious damage by a person other than a Sub-hubco Party, Sub-hubco must verbally inform the Helpdesk and the [Authority's Representative] (a "Malicious Damage Report"). Where it is reasonably practicable for it to do so without prejudicing its ability to achieve Rectification of the Service Event within the Rectification Period and subject to any immediate steps that it requires to take to make the Facilities safe, it must allow the [Authority's Representative] an opportunity to inspect the evidence it relies on to support its claim that malicious damage caused the Service Event concerned before carrying out Rectification and, where this is not reasonably practicable, Sub-hubco must take reasonable steps to preserve or record in a suitable manner any such evidence and forthwith make that record available to the Authority.
49A.2.2 Provided Sub-hubco has complied with the requirements of Clause 49A.2.1, unless within [two (2) hours] of receipt of a Malicious Damage Report or within [two (2) hours] of the start of the next Core Times where the Malicious Damage Report is made outside Core Times, or, if applicable, within [one (1)] Business Day of receipt of the evidence or record of the alleged malicious damage concerned the [Authority's Representative] notifies Sub-hubco that he agrees that the Service Event referred to in the relevant Malicious Damage Report was caused by malicious damage by a person other than a Sub-hubco Party, the [Authority's Representative] will be deemed to have disagreed that the Service Event concerned was caused by malicious damage by a person other than a Sub-hubco Party.