Guide

Website handover checklist for a new board

Everything an outgoing board member should hand over, and everything an incoming one should check, so the website, email and money don’t get lost in the change.

By Mike Andersen · Updated October 2026

When a board changes, the website is where things quietly get lost: a domain registered to someone’s personal email, a Stripe login nobody can reach, a password last changed three presidents ago. A handover checklist prevents it. Run through the list below every time an officer changes, ideally in the same meeting.

Mike Andersen, who builds every Purple Pushpin site, works with volunteer boards that change every year or two. This is the checklist he uses.

Before the outgoing person leaves

The website

  • Who has administrator access, and who should?
  • Give the incoming person their own login. Don’t pass on a password.
  • Where is the site hosted, and who pays for it?
  • When was the last backup, and who knows how to restore one?

The domain

  • Which registrar holds the domain?
  • Is it registered to the organization and an organization email address?
  • When does it renew, and is auto-renew on with a current card?

Email

  • Which addresses belong to roles, like president@ or treasurer@? Move them to the new person.
  • Who can send the member newsletter?
  • Are SPF, DKIM and DMARC set up? See our guide.

Money

  • Add the new treasurer to the bank and payment processor with their own login.
  • Note every recurring charge: hosting, domain, software, email.
  • Confirm where payouts land.

Accounts and documents

  • Social media accounts and who can post.
  • Google Business Profile and Search Console access.
  • Bylaws, minutes, contracts and insurance documents, and where they live.
  • Vendor contacts: web developer, venue, caterer, printer.

After the change

  1. Remove the outgoing person’s access to the website, payment processor, bank, email lists and social accounts, unless they’re staying on in another role.
  2. Change any shared passwords they knew.
  3. Turn on two-step verification for the new person on every account.
  4. Update the board page on the website, and keep the outgoing officer on your past board list.
  5. Write down anything learned in a one-page “how we run the website” note for next time.

Frequently asked questions

What should a board transition checklist include?

Website and domain access, email accounts, payment and bank access, social media, documents and vendor contacts, plus removing access from people who’ve left.

Who should own an association’s website accounts?

The organization, using role-based email addresses, with at least two current board members holding their own access.

How do we avoid losing access when a volunteer leaves?

Never let a key account depend on one person’s personal email. Use organization addresses, a shared password manager and two people per account.

Where Purple Pushpin fits

Purple Pushpin was built for boards that change. Each officer gets their own login, the board page keeps your past board history, your domain and Stripe account stay in the organization’s name, and the admin has one screen per job so a new volunteer can find their way around. More in what never to share.

See it for yourself

Click around a real one.

The Purple Pushpin demo is a complete fictional chamber and association. Log in to the admin side your board would use, no sales call needed.

Try the demo See pricing