Information that lands, and can be shown to have landed.

The problem is rarely the volume. It is the accountability.

A new security requirement goes out by email. Two teams read it, one misses it among 60 other messages, and the site crew never sees it because nobody there opens a mailbox during the day. Three weeks later someone asks, and the same thing is explained a second time. When the auditor wants to know who acknowledged the policy, the search begins in mailboxes and in a spreadsheet somebody maintained by hand. Communication was not missing. Proof of it was.

80 employees, four policies a year, a record instead of a search.

Work it out with your own numbers. If four binding notices a year go to 80 employees and follow-up today runs through mailboxes and a spreadsheet, that is four rounds of collecting, chasing and reconciling. Anyone who has done it knows the order of magnitude: half a day to a full day per notice, plus the questions that come back because something could not be found. The real gain, though, is not the hours. It is that in an audit a list exists, rather than a recollection that the email was sent.

Who this is built for.

The Newsroom is built for Swiss companies whose staff do not sit at a screen all day: trades and construction, hospitality, care and nursing, production, retail with several branches. Typically twenty to three hundred employees, several sites or shifts, and a management that informs people today through a mailing list, a group chat and a notice in the break room. Size alone does not decide it. What decides it is that a message concerns more than one department.

It pays off most where there are notices to send that carry consequences: safety requirements, working-time and hygiene rules, quality instructions, changes to the staff regulations. There it does not count that people were informed. What counts is that months later you can show who acknowledged it, by name.

What managing directors and HR leads ask first.

We have a mailing list and a group in a messenger. Why another channel?

Because both show that something was sent, not that it arrived. In the Newsroom the confirmation hangs on the person and on the post, and it stays there even when someone leaves the company or changes phone. And no channel is added, one of them pulls several together: announcement, question, poll and event all sit on the same post.

How do we reach employees without a company e-mail address and without a fixed workplace?

Through the phone. The post arrives as a push notification, the confirmation is one tap, and the view looks the same on a phone as at the desk. A private device is enough, a company phone is not a prerequisite. And anyone who is in their mailbox all day anyway gets the same post as an e-mail and confirms through the link in it.

What exactly does mandatory reading mean, and what happens if someone does not confirm?

A post is marked as mandatory reading when it is published, with a deadline. For the people it concerns it stays visibly open until they have confirmed. After the deadline the missing people stand by name on a list, and you remind precisely those. A confirmation records who read it and when; if you want to check understanding beyond that, you attach a short poll to the same post.

Can management publish something that concerns only part of the workforce?

Yes, the audience is set on the post: department, site or role. A notice for senior staff goes to senior staff, a shift instruction to the shift, a house notice to everyone. Publishing itself hangs on the role too, so production management writes for its own area without anyone from the executive management having to read every line first.

Where is this data, and what about the revFADP?

Your data is hosted in Switzerland. Before anything is sent to an external AI model, our Sensitive Data Guard masks or blocks personal, contract and financial data, only the released, non-identifying content is forwarded, under no-training agreements. Who confirmed which post, and when, is processing of personal data and stays in Switzerland. Requests for access and erasure under the revFADP can be evidenced through the audit chain, with person and timestamp.

What if someone contradicts a post in public?

Then the objection stands where management sees it, rather than in the coffee break. Comments hang on the post and are visible to the audience, with names. One answer that everyone reads saves the individual e-mails that would otherwise ask the same question. If a notice is purely for information, comments can be switched off for that one post.

We run training sessions and company events regularly. Does that help here?

An event runs as an event post: date, place, accept or decline directly on the post, and an attendee overview instead of replies sitting in several mailboxes. Whoever accepted gets the reminder on the same channel as the invitation. After the event the post stays, documents included, and who was there at the time remains visible.

What does this give us in a statutory review or an audit?

For every binding notice it is established who received it and who confirmed it, and when. Those are exactly the records regularly asked for in occupational safety, quality standards and internal regulations. The overview can be output and attached to an audit report, and the entries sit in the same audit chain as your bookings, not quietly alterable after the fact.