When a familiar coordinator is away, a support process can suddenly depend on someone remembering another person’s number. A role-based directory makes the route easier to maintain. It explains which team handles the request and where that team can be reached.
List responsibilities before names
Start with the functions a department actually needs: service intake, equipment location, site access, application ownership and escalation. Add the approved contact route for each function. Identify a backup where the service arrangement provides one. Keep individual contact details in an appropriate internal system and avoid publishing a directory that invites unrestricted access to technical staff.
Check the directory through a sample request
Take a routine example, such as arranging a scheduled equipment visit, and follow the directory from start to finish. Note where a request could bounce between teams or reach a person with no authority to act. Give the directory an owner and review it when roles change. Include the original request reference in handoffs so users do not need to open a new conversation at every step.
Practical takeaway
Organize contacts by the work they own, then test whether a new coordinator can follow the route without personal introductions.