Checklist for Board Changes in Associations
So that your association's online presence doesn't stall during a board change: a checklist for handing over website access, roles, and responsibilities.
The board change is coming up and you're wondering how best to hand over website access and responsibilities to the new team? A structured handover is important so that your association's online presence doesn't stall. This checklist helps you not forget anything.
Why a regulated handover is important
During board changes, important access data is often lost or responsibilities are unclear. This can lead to the website no longer being updated or, in the worst case, even going offline. A thorough handover prevents such problems and ensures that the association remains capable of acting even after the change.
Checklist for handing over website access
This checklist guides you step by step through the handover. Adapt it to your association's needs.
1. Collect and document access data
Create a list of all relevant accesses. This includes:
- Access to the web hosting panel (e.g., at Webhosting)
- FTP or SSH accesses
- Access to the content management system (e.g., WordPress)
- Access to domain management (if separate)
- Email accounts and passwords
- Access to social networks and Google Analytics
Document all usernames and passwords in a secure place. A password manager is ideal for this.
2. Review roles and permissions
Not everyone on the new board needs full access. Consider who needs which rights. Often there are different roles in the CMS (administrator, editor, author). Remove old accounts and create new ones with the appropriate rights. This maintains security.
3. Clearly distribute responsibilities
Who takes care of which tasks? Put in writing who is responsible for content, technical maintenance, backups, and domain management. A simple responsibility plan helps avoid misunderstandings.
4. Test backups and restoration
Make sure the new team knows how to create and restore backups. At Dezhost, daily backups are created automatically. Explain how to restore a backup in an emergency.
5. Check domain and contracts
Clarify in whose name the domain is registered and which contracts exist. If changing the hosting provider or domain, timely planning is important. The Domains can often be transferred to the new team.
6. Document and test the handover
Create a handover protocol that records all accesses and responsibilities. Have the new team test the accesses before the old board leaves. This way, problems can be identified and fixed early.
Practical example: How the handover works
A sports club changes its board. The previous webmaster hands over an encrypted password file with all accesses to the new team. Together, the roles in WordPress are adjusted: The new chairman receives administrator rights, the secretary may publish posts. The domain is registered to the association, and the contracts continue. A backup is created and successfully restored. After a week, the new team tests all functions and confirms the handover in writing.
Avoid common mistakes
These mistakes should be avoided:
- Passing on access data only verbally
- Not deleting old accounts
- Not recording responsibilities in writing
- Not testing backups
- Not registering the domain to the association
With a thorough handover, you avoid these pitfalls.
A good handover takes time and care. If you go through the checklist point by point, nothing stands in the way of a smooth transition. Your association stays online and capable of acting.

