One place to check for company news
Policy changes, closures and dated events share one board.
One shared board for the whole organisation. Publish notices, schedule events, collect RSVPs, and keep the conversation going with reactions and comments.
Company news gets pinned, buried under the next message, and asked about again in five separate DMs and nobody knows who is coming to the briefing. Wikidoc puts it on one board with a calendar, an RSVP, and a comment thread on every post.
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.
Policy changes, closures and dated events share one board.
Pick a day to see its events, including ones that started earlier.
Attend, Not sure or Decline, with an optional note. Change it anytime.
Reactions and threaded comments sit under the notice, not in five separate DMs.
One company-wide email per post. Anyone can switch the emails off.
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.
Every notice can point at the SOP it changes, the task it creates, or the work it praises. Same org, same source of truth.
Turn a notice that needs doing into a card with an owner and a due date.
Attach the SOP or policy the notice is about, so both arrive together.
The other org-wide wall, where praise points at the work.
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 organisation and to nobody else. Portal guests are refused before any read, exactly as they are on Recognition.