How a post gets published
Configured once per content typeDraft and schedule
Content is created against a slot on the calendar, with the channel, campaign and intended publish window attached.
Route for review
The chain is applied automatically by content type — some posts need one reviewer, some need comms, legal and a leader.
Reviewers respond
Comments and changes stay on the item rather than in a thread, so the next reviewer sees the full context.
Approve and publish
Approval releases the post to its scheduled window, and the trail is retained against the item.
Approval logic is approval logic
One workflow layer, many uses
The mechanism routing a leave request to a manager and a department head is the same one routing a post to comms and legal. Because approval logic is data rather than code, both are configured, not built.
It follows your real structure
A regional post can route to the regional head; a group announcement to leadership. That works because the organisation model already knows who those people are.
A trail that survives the thread
Who approved, when, and on which version. Chat approvals disappear into scrollback; this does not, which matters the one time someone asks.
Deadlines that mean something
A hiring push tied to an open role has a date. Overdue reviews escalate rather than quietly missing the window.
