Decide public content and editor handover before building
A neighbourhood association site may serve people learning about activities and residents receiving notices. Distinguish public information from member-only communications.
Document editors, approvals, and access transfers so maintenance continues after committee changes. Avoid keeping the only copy of content on one person’s device.
Publish activities, event dates, meeting places, and participation instructions. Use exact dates and remove misleading invitations once registration closes.
Use an organisation-managed contact channel. Do not copy membership lists, individual consultations, or address records directly onto public pages.
Decide publication scope and approval
Check publication permission and identifiable people in event photographs. Deliver member-only messages through a separate communication method.
Record authors, approvers, and change dates. GOV.UK guidance describes reviewing outdated content for revision or removal; use a similar review for expired events. (GOV.UK: Manage existing content)
Transfer editing access when the committee changes
Document the editor location, content storage, contract owner, and update steps. Transfer access through the publishing service’s account controls and keep passwords out of public content.
Have the new editor try publishing a changed event date. Review unnecessary former-editor access and appoint a backup.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To publish public neighbourhood events and activities, give SpreadSite a try!
Build a website with SpreadSite →