.png)
One shared board for the whole organization. Publish notices, schedule events, collect RSVPs, and keep the conversation going with reactions and comments.
Write the notice, or set a date and let it land on the month calendar too.
One email per post to the active roster, under a single category anyone can switch off.
React, reply in a thread, or RSVP, and the counts sit on the post itself.
A notice is read; an event is dated. Both share one board, because splitting them is how a noticeboard becomes two things nobody checks.
A notice for a policy change, a new SOP, or a closure, newest first
An event for a town hall or a stocktake dated, and on the calendar
Attach the document, process map, or checklist the notice is about
Pick a day and the list below it narrows to that day. An event is indexed on every month it overlaps, so October knows about the thing that started in September.
Dots on the days that carry an event, with a day list underneath
All-day or timed, stored so neither shifts by a day in another timezone
Indexed by occurrence, so a multi-day event marks every month it touches
Attend, Not sure or Decline, with a note if there is something to say. One per person and always changeable, because an RSVP that cannot be withdrawn is a number nobody trusts.
Attend, Not sure, or Decline. One per person, changeable at any time
An optional note, because "on shift until 3:30" is what moves a meeting
Counts on the post, with no automatic chasing of the people who are silent
The same reaction glyphs and threaded comments the rest of Wikidoc uses. The question a notice provokes is answered underneath it once, for everyone.
Five reaction glyphs, one per person, counted in people rather than glyphs
Threaded replies with edit, and a delete that tombstones the comment
A comment emails the thread, never the whole organisation
This is the first thing in Wikidoc whose default audience is the entire roster. Restraint is built into it rather than bolted on afterwards.
One email per post to active members, with the author excluded
One category to switch off. Muting the email never mutes the board
Never visible to portal guests or clients, only members of your org
Instructors who never share a shift see the same timetable change on the same board, with the class SOP attached so the change and the instruction arrive together.
The rota briefing gets an attendance list instead of a guess, and the notes on the RSVPs tell the manager to run it twice rather than once.
A policy change is posted once with the document attached, and the questions are answered underneath it on the record, instead of in five separate inboxes.
Closures and training days live on one month calendar every practitioner can open, rather than on the wall of a staff room half the team never stands in.
Admins and Managers author notices and events, and manage what they authored. Everyone else in the organisation reads, reacts, comments and RSVPs.
A notice is a thing to read, a policy change, a new SOP, a closure, and it appears in the list, newest first. An event is dated, so it appears on the month calendar as well, with Attend, Not sure or Decline and an optional note.
Each new notice or event sends one email to the active roster, under a single Noticeboard category anyone can switch off in Settings. Comments are different: a comment notifies the author and the people already in that thread, never the whole org.
Yes. A Viewed by panel on each published notice gives the count plus names, shown to the author and Admins only. You also see reactions, comments and an event's RSVPs. For a notice that must be acknowledged, use a checklist item or a training module with attestation required, which captures a signed "read & understood".
Yes. An RSVP is one per person and mutable, move between Attend, Not sure and Decline as often as you like, and the counts update with it. Nobody is auto-chased for an answer.
Never. The Noticeboard is visible to active members of your organization and to nobody else. Portal guests are refused before any read, exactly as they are on Recognition.
