Site Contact List: A Project Handover Checklist
A site contact list for a project handover should identify who handles each operational responsibility at the location. It also needs a backup route and a person who will maintain the information after the handover.
This article uses site to mean a physical work location. If you mean website-owner contacts, the relevant unit is a domain or publisher and the contact-selection process is different.
Begin with responsibilities that remain after handover
A project team may have temporary contacts for installation, testing, and launch. After completion, those responsibilities may pass to maintenance or site operations. Copying the project directory without reviewing the roles can leave staff calling people who no longer own the work.
List the ongoing responsibilities first. For each one, identify the receiving team, approved work channel, backup role, and the date ownership changes.
Use a handover record for each responsibility
| Record item | Question to answer |
|---|---|
| Site reference | Which facility or branch does the entry cover? |
| Responsibility | What request should be routed here? |
| Receiving role | Who owns the work after handover? |
| Work channel | Which approved number or address should staff use? |
| Backup route | What happens when the primary role is unavailable? |
| Review owner | Who confirms corrections after the project closes? |
For an invented example, a receiving-desk entry might route delivery queries to the branch operations team and use the duty coordinator as backup. The record should explain the task; it does not need private employee information to be useful.
Walk through a routine request
Ask a colleague unfamiliar with the project to identify the route for a common issue using only the list. If they cannot tell whether the contact covers deliveries, maintenance, or billing, revise the label.
This is a directory usability check, not a substitute for emergency procedures or a reason to make unnecessary test calls. Review emergency and security arrangements through the organization’s established process.
Remove temporary access details
Keep passwords, access codes, and sensitive technical instructions outside a general contact list. Review whether temporary personal numbers still belong in the final directory and whether a shared work channel can replace them.
Issue the maintained location of the list and identify who should report changes. A correct handover document becomes unreliable if old copies continue circulating without a correction process.
Use external data only for a defined research task
An externally sourced contact does not establish current operational responsibility at your site. Obtain that confirmation from the organization or team handling the handover.
DB TO DATA’s work-location contact guide explains the underlying directory fields. Our staff handover template guide adds an editable workbook for approved internal contacts.
For external business-audience research, Latest Mailing Database’s sample request page is a separate route for discussing fields and selection requirements.