Because urgent issues can arise at any time - including outside normal working hours or requiring rapid, senior risk decisions - explicitly identifying emergency contacts and a clear escalation path (distinct from routine day-to-day project management contacts) ensures the engagement can respond quickly and appropriately if something serious occurs. This is a distinct, necessary element of scoping documentation, not redundant given a Rules of Engagement document (B), which typically defines the process but should still reference specific named contacts; emergency escalation is equally relevant to technical engagements, where issues such as accidental service disruption can and do occur (C); and escalation should route to the accountable governance/risk contacts (such as the Control Group), not to media relations, which is neither the appropriate first point of contact nor typically involved at all in most engagements (D).