The accounts list
Write down every online account your organisation depends on: domain registrar, hosting, email, website administration, app stores, payment providers, social media, file storage and any software subscriptions. For each, note who owns it, which email address it is registered to, whether two-step sign-in is on, and where the recovery details are kept. Store passwords in a shared password manager, never in the list itself.
A renewal calendar
Domains, security certificates, hosting plans and software licences renew on different dates, often charged to a card that may have expired. Put each renewal into a shared calendar with a reminder a month ahead. Expired domains are one of the most common, and most avoidable, reasons a small organisation's website and email suddenly stop.
Asking for a website
Before you speak to any supplier, write a page covering: who the site is for, the three things those people most need to do, what content you already have, who will update it and how often, any systems it must connect to, and a deadline only if it is real. This helps you compare answers fairly.
When someone leaves: a calm two-week plan
Week one: list what they look after, confirm every account is in the organisation's name, and transfer ownership where it is not. Week two: ask them to talk through each system while someone else takes notes, test a backup restore together, and change shared passwords after they go. Thank them properly; their goodwill matters.
Choosing a support arrangement
Ask any supplier: what hours are covered, how urgent issues are flagged, how quickly they acknowledge them, what counts as included work, and how you leave if it is not working. Clear answers in writing are a good sign.
Backups you can trust
A backup is only proven when it has been restored. Once or twice a year, restore your website or data to a test location and check it works. Keep at least one copy somewhere separate from the original system.