Publish once. Keep everything attached.
See what changed, what’s coming, and what needs your attention. Each update keeps its details, discussion, dates, and acknowledgement together in one place.
01 · Home
What changed, what's coming, what needs attention.
Home puts what needs attention first, with recent activity and what’s coming up close by. Channels keep everything else organized and easy to return to.

02 · Update
One important thing, one permanent home.
An update has a title that says what happened, a channel it belongs to, a person who published it, and a permanent address.
- Published, not sent
- The update has its own place in GroupNews. A notification points people to it.
- Attributed
- Author and publication time are part of the record.
- Context stays attached
- Acknowledgement and discussion stay with this update.
Who can see an update is a choice: a few members, the whole group, or the public. Either way, the group has a place to publish what matters.

03 · Acknowledgement
Two states. No inference.
An update can require acknowledgement. Until a member chooses to acknowledge it, they are Pending. When they choose it, they are Acknowledged, and the time is recorded. Opening is not acknowledgement. Nothing else changes the state — not reading it, not scrolling past it.
Pending
The update asks for acknowledgement and this member has not given it yet. Visible to the member on Home, and to admins in the acknowledgement view.
Acknowledged
The member deliberately confirmed this update. Recorded with the time it happened.
Not a state
Seen. Opened. Read. Time spent. GroupNews does not have read receipts, and will not tell you who looked.


04 · Discussion
Questions stay with the update.
Every discussion in GroupNews belongs to an update. The discussion view lists conversations by the update they are about — so the organization can see where the questions are, and anyone arriving late reads the answer in context.
Replies stay attached to the point they answer, so discussion stays in context instead of becoming a separate chat room.


05 · Events and deadlines
Dates are records, not sentences in a paragraph.
An event is a thing that happens at a time. A deadline is a thing that is due. Both are their own records, both appear on the calendar, and both surface on Home under Coming up.

06 · Search
Find it later — updates, discussions, channels, people.
Search covers the organization's record and separates results by type, so a question about a policy returns the policy, and a question about a conversation returns the conversation. Plain keyword search over what was actually published.


07 · Channels and members
Structure people can predict.
Channels give each kind of information a stable place — announcements where announcements go, training where training goes. A channel is a shelf, not a room.
Members belong to the group with a role: owner, admin, author or member. Authority over publishing is a paid capability; being in the group is not.


One responsive product
The same product, on any screen.
Home, the update, the acknowledgement, the discussion, the calendar and search, on a phone.





Weekly digest
Email has one job here: bringing people back.
The weekly digest shows what needs acknowledgement, what changed, and where discussion is happening. Every line links back to the update. It is a bridge, not the product.

Start with one recurring update.
Do not migrate everything. Put the policy, the deadline or the announcement people keep asking about into GroupNews, and see what stops getting lost.
