A committee handover should leave the incoming team able to find, correct and publish information without depending on someone who has stepped down. Passing over a folder is only part of that job. Access and responsibility need to move with it.
Separate ownership from everyday publishing
List the services the community relies on: its website, noticeboard, email, domain name and any booking or membership systems. Record who owns each account, who maintains it and who deals with renewals. Keep credentials and recovery material in a suitable secure location, separate from a public handover document.
Give incoming people their own accounts and the access their role needs. Avoid passing around one person’s password. Complete any ownership transfer before the outgoing owner becomes unavailable.
Prepare a useful handover record
- Access: the services used, responsible owners and outstanding invitations.
- Current information: where the authoritative rules, instructions and contact details live.
- Upcoming work: meetings, seasonal changes, planned closures and notices still awaiting confirmation.
- Maintenance: which pages need review and who confirms their accuracy.
- Subscriptions: renewal dates, the responsible payer and where account records are held.
- Open questions: outdated documents, uncertain ownership or arrangements that are still being decided.
Walk through an actual update together
A practical handover exercise: ask the incoming publisher to sign in with their own account, find the community room instructions, locate the current contact, and preview a draft announcement about an upcoming closure.
Then check how a reader would find those instructions on a phone. This reveals missing access and unclear organisation while the outgoing team can still help.
Use a draft or an agreed real correction for the exercise. Do not publish a fictional closure to the live community Board.
Confirm the transition
Once the new team has working access and ownership is correct, review the outgoing team’s permissions and remove access that is no longer appropriate. Update public contact information at the same time. Keep access for anyone with an agreed continuing role.
Arrange a short follow-up after the incoming team has handled its first updates. The practical questions often appear only when someone needs to publish without help.
How this applies to PutBoard
PutBoard distinguishes Account ownership from Board publishing roles. Check both during handover: being able to edit a notice is not the same responsibility as owning the Account. Choose a plan that supports the people who need to maintain the Board, and review access across all Boards if the Account has more than one.
The aim is continuity. Keep the community’s familiar Board address and useful information available while the people maintaining it change.
Use the plan comparison to check shared-management options, and read how to organise the documents the next committee will inherit.