The meeting time was in an email. The revised time went into the group chat. Someone shared a screenshot, but it showed the earlier arrangement. Now an organiser is answering the same question for the fourth time: when are we meeting?
This is an example, but the pattern will be familiar to many community volunteers. Everyone involved may have communicated carefully. The difficulty appears later, when someone needs to retrieve one dependable answer.
An announcement and a reference have different jobs
An announcement brings something to people’s attention. A reference gives them somewhere to check the details when they need them. A chat message can do the first job well and still be difficult to use for the second.
Consider instructions for using a community room. Members might read them when they are first shared, but need them again months later when arranging a gathering. Remembering which conversation contained the instructions should not be part of booking the room.
Follow one piece of information
Example: a change to community room access. A volunteer emails the new opening arrangements. Another adds them to a social post. The website still has the previous hours because its editor has not received the change.
A member searches the website and arrives at the wrong time. The answer was published, but there was no agreed place where it was kept current.
Adding another announcement may help the next person, but it leaves the conflicting information in place. First correct the page that people will return to, then share its address through the channels the community already uses.
Choose a home for the answer
Start with the questions your organisers repeatedly receive. For each one, identify where the current answer should live and who can confirm it. That might be an existing website page, a shared resource area or a community noticeboard. You do not need to move every conversation or document.
- Current changes: a notice explaining what is happening and when.
- Regular arrangements: a maintained page for opening times, instructions or recurring questions.
- Dates and locations: an event entry with the confirmed details.
- People to contact: an agreed contact list with someone responsible for checking it.
Use the same link whenever you share that information. A short message can explain the change; the linked page holds the fuller answer. If details change again, update that page and send a correction wherever people may have relied on the previous announcement.
Make “current” visible
People need a reason to trust what they find. Give temporary notices explicit dates, remove expired instructions from prominent positions, and put a review date on lasting guidance where it helps. Agree who checks each resource when circumstances change.
A link alone does not solve conflicting information. Someone still needs to keep its destination accurate. Our guide to keeping notices current suggests a simple routine.
Try it with three recurring questions
Choose three questions you answered recently. Give each a clear, maintained answer at a dependable address. Over the next few weeks, use those links in replies and ask members whether they could find the information without help. Their difficulties will tell you what to improve next.
PutBoard is one way to provide that shared information home while keeping your website, emails and conversations. You can explore the demo Board to see how notices, reference information and events sit together.