An escalation list is only useful if the people on it know what they are expected to do. A list of names without hours, responsibilities, or a fallback path can fail when the normal contact is unavailable. Build the list around roles and agreed coverage.
State what each contact can decide
For every role, note whether it can report an issue, authorize a change, approve access, or coordinate a supplier. These are different responsibilities, and one person may not hold all of them.
Confirm the contact method and the hours that apply. Do not infer round-the-clock coverage from the presence of a mobile number or from a supplier's general marketing language.
Review the fallback path
Describe what the service process requires if the first contact cannot be reached. Make any limits or dependencies visible to the customer and support team.
Review the list when people change roles and during routine service meetings. A brief walkthrough of a hypothetical issue can reveal missing decision-makers without creating a real interruption or an unnecessary emergency exercise.
Practical takeaway
Use a role-based contact list with confirmed hours, authority, and the agreed next contact if the first is unavailable.