A single source of truth
Information governance
Every published update points back to the record it describes, so there is one reality — and anyone can drill from the message to the data behind it.
One formally published reality — inside the company and out to customers.
“Where do we align on formal status and customer engagement?”
Every company runs on status updates, and most of them disagree. The deck says one thing, the program tracker another, the customer email a third. Broadcast makes formal communication part of the model. Anything in Dotwork — a strategy change, a decision, a program’s status, a roadmap, a release, a banked outcome — can be drafted, approved and published to the right audience, internal or external, through the channels they already use. Feedback comes back attached to the record it is about, so the published picture and the working model stay one reality. And everything published can be consumed by the LLM of your choice, so your AI tools share the same formal understanding of the company as your people do.
Rooms you open
- Announcements
- Roadmaps
- Formal Status
- Feedback
- Audiences
- Engagement
Part of Steer · What should we do — and why?
The pressure
Status lives in a hundred places — and none of them agree.
Leaders write updates by hand from data they had to chase. Product publishes release notes in one tool, the PMO sends status in another, and customer success forwards roadmap slides of its own. Nothing is formally approved, nothing is versioned, and the feedback that comes back lands in inboxes nobody connects to the plan.
What it looks like today
- Status reports rebuilt by hand every week
- Different versions of the truth for executives, teams and customers
- Roadmap promises made without the plan behind them
- Customer feedback that never reaches the decision it should change
- No record of what was communicated, to whom and when
What changes
What changes.
TodayWith Dotwork
Updates written from scratch
Updates drafted from the records they describe
Status in decks, emails and chat threads
One formally approved status for each audience
Release notes and roadmaps in a separate tool
Announcements and roadmaps published from the same model as the work
Feedback in inboxes
Feedback tied to the record it is about and routed to its owner
No record of what was said
A versioned history of every published update and who it reached
One published reality
Publish from the model — and let the feedback flow back into it.
Broadcast reads from the same model as strategy, money and work, so a published update is never a separate version of the truth. A status change, a banked outcome or a shipped release becomes a draft for the right audience; once approved, it goes out through the channels people already use. Replies, votes and ideas come back attached to the record they are about, where the owner can act on them.
Where other tools stop
Release-note tools announce releases. Status reports live in decks. Neither is connected to the plan, and the feedback they collect never reaches the decision it should change.
The communication thinking built in
Formal communication, run as a system — not a send button.
Broadcast encodes the practices communications, product and change teams already rely on, so every update follows them by default.
Formal approval and disclosure
Governance practice
Contributors draft, owners approve, and every version is kept — the discipline of formal disclosure, applied to everyday status.
Stakeholder mapping
Stakeholder management
Audiences are defined by interest and influence, so the board, the teams and the customers each get the right depth — from the same source.
Closed-loop feedback
Customer experience practice
Feedback is linked, routed and answered, and the person who gave it hears what happened — the loop closes in the model, not in an inbox.
Now, next, later
Outcome-based roadmapping
Roadmaps show commitments by horizon rather than false precision, and change automatically when the plan behind them changes.
Communicating the change
John Kotter · Leading Change
Strategy and transformation only land when they are communicated again and again. Broadcast makes that rhythm routine and measurable.
The rooms
The rooms inside Broadcast.
Each room answers one question a leader actually asks, with the view that answers it and the measures that say whether it is working.
A room is a ready-made view that answers one leadership question, built on the same shared data as every other room.
Room 01
Announcements
“What changed, and who needs to know?”
Branded announcements for releases, decisions, strategy changes and program milestones — drafted from the records, scheduled and published to each audience.
How you know it is working
- Updates drafted from live records, up
- Time from a change to its announcement, down
Room 02
Roadmaps
“What are we committing to — and who can see it?”
Internal and customer-facing roadmaps published straight from the plan, with visibility set by stage so each audience sees the right level of detail.
How you know it is working
- Roadmap items backed by funded work, up
- Promises published without a plan behind them, to zero
Room 03
Formal Status
“What is the official status — and who approved it?”
The approved status of programs, outcomes and bets, published as the company’s single reality, with every version and approval kept.
How you know it is working
- Status reports drafted from live data, up
- Conflicting versions of the same status, down
Room 04
Feedback
“What are customers and teams telling us — and where does it go?”
Ideas, votes and comments on any announcement or roadmap item, linked to the records they concern and routed to the people who own them.
How you know it is working
- Feedback linked to a record and an owner, up
- Time to respond to feedback, down
Room 05
Audiences
“Who hears what, and through which channel?”
Teams, executives, the board, customers and partners as audiences, with categories, cohorts and subscriptions across email, Slack, Teams, RSS and an in-app widget.
How you know it is working
- Audiences with a named owner and channel, up
- Duplicate sends across tools, down
Room 06
Engagement
“Did the message land?”
Opens, clicks and feedback by audience and by update, beside the outcomes the communication was meant to support.
How you know it is working
- Engagement by audience, up
- Important updates nobody read, visible
Agents and skills
AI drafts, tailors and routes. Owners approve what goes out.
Dotwork agents draft updates from the model and from tools like Jira, Confluence and Loom, tailor them for each audience and route what comes back. Nothing is published without an owner’s approval — and Broadcast can be driven from any AI tool through its MCP server.
Smart Draft
Every changeTurns a status change, a shipped release or a banked outcome — plus the tickets, docs and videos behind it — into a draft update in your voice.
- What you get
- A ready-to-edit announcement, linked to its records
- Where you decide
- Contributors draft; owners publish
Status Composer
On cadenceDrafts the formal status for programs, outcomes and bets from the live model — what moved, what is at risk and what is needed.
- What you get
- A versioned status update for approval
- Where you decide
- The owner approves the version that becomes official
Audience Tailor
Before publishingProduces a version of one update for each audience — the board, the teams, customers — and flags anything internal-only in an external version.
- What you get
- One message, tailored per audience, with flagged content
- Where you decide
- The approver reviews each version before it goes out
Feedback Router
ContinuousClassifies incoming feedback, removes duplicates, links it to the roadmap item, outcome or bet it concerns and routes it to the owner. Feedback that bears on strategy becomes evidence in Strategy Validation.
- What you get
- Feedback linked to records and owners
- Where you decide
- Owners accept the link and respond
Roadmap Sync
When the plan changesWhen funded work changes stage or date, updates the roadmap views that show it and notifies the people subscribed to it.
- What you get
- Roadmaps that match the plan, with subscribers notified
- Where you decide
- The roadmap owner approves changes to customer-facing items
Engagement Analyst
WeeklyReports who read what, which audiences are missing important updates and which messages drew feedback.
- What you get
- An engagement digest by audience and update
- Where you decide
- Communication owners decide the follow-up
Use cases
Where companies put it to work.
CEO · Chief of staff
Formal company status
Publish the official weekly or monthly status of the company’s priorities — drafted from the model, approved once and sent to every audience in the right form.
- One approved status, many audiences
- A versioned record of what was said
Chief strategy officer · Chief transformation officer
Strategy and transformation communication
Tell the organization what changed in the strategy and how the transformation is going, straight from Steer — and hear back from the people doing the work.
- Strategy changes announced from the record
- Feedback that reaches Strategy Validation
All employees · People leaders
Why maps for every employee
Show every person how their work contributes to the company’s goals — from their team’s work, through the programs and outcomes it serves, up to the strategy. Published from the model, so it stays current when the plan changes.
- A line of sight from each team’s work to company goals
- Updated automatically as the plan changes
Product · Product marketing
Release notes and product announcements
Turn shipped work into branded announcements and changelogs, published to customers by email, in-app and on a public page.
- Announcements drafted from shipped work
- A branded, searchable changelog
Product · Customer success
Customer roadmaps and feedback
Share a roadmap that matches the plan, collect ideas and votes, and show customers what happened to their feedback.
- Roadmaps that stay true to the plan
- Ideas linked to the work they inform
Customer success · Marketing
Customer engagement at scale
Reach every customer segment with the updates that matter to them, through the channels they use, and see who engaged.
- Segmented updates by cohort
- Engagement tracked by audience
CEO · CFO · Portfolio company leaders
Board, investor and sponsor updates
Send the board, investors or a private equity sponsor a formal update drawn from the same records the leadership team runs on.
- Board and sponsor updates from live data
- One version of the truth for every stakeholder
Chief risk officer · Compliance · General counsel
Compliance status for governing bodies
Report the formal status of controls, remediation programs and regulatory commitments to regulators, auditors, boards and other governing bodies — drafted from the controls and evidence in Dotwork, approved, versioned and on record.
- Compliance status drafted from live controls and evidence
- A versioned record of what was reported, and when
Risk & compliance · Enterprise architecture · HR
Policy and standards rollout
Publish new policies and standards to the people they apply to, see who has seen them, and collect questions in one place — linked to the controls and standards they come from.
- Policies sent to exactly the people they apply to
- Reach tracked by audience
How it compares
Release notes, roadmaps and formal status — published from one model.
Companies usually run release notes and roadmaps in one tool and send status through decks, email and chat. Broadcast does both jobs from the same model as the strategy, money and work it reports on.
| Capability | Release-note & roadmap tools | Decks, email & chat | Broadcast |
|---|---|---|---|
| Release notes and announcements | Partly | ||
| Public and private roadmaps | Partly | ||
| Customer feedback and ideas | |||
| Publishes status on strategy, programs and outcomes — not just releases | Partly | ||
| Drafted from the live model, not rewritten | |||
| Formal approvals and versioned status | Partly | ||
| Feedback linked to the plan and the decision it affects | |||
| Internal and external audiences from one source | Partly | Partly | |
| One published reality across the company | |||
| Formal company context available to any LLM |
Channels
Reach people — and their AI — where they already are.
Publish once and deliver everywhere your audiences work, with subscriptions so people choose what they hear about. The same formally published updates are available to the LLM of your choice, so every AI assistant and agent works from approved company context.
Email and digests
Branded announcements and scheduled digests, with subscriptions by category.
Slack and Microsoft Teams
Updates posted where teams talk, with feedback collected in the same place.
In-app widget and public pages
Announcements, roadmaps and feedback embedded in your product and on a branded, searchable page.
The LLM of your choice
Every approved status, announcement and roadmap is available to your AI assistants and agents through Dotwork’s MCP server — formal company context instead of guesses.
Who it is for
Who opens it, and what they ask.
CEO
“Is everyone hearing the same version of where we are?
Chief of staff
“What is the official status this week, and who has approved it?
Chief product officer
“Does our customer roadmap match what we have actually funded?
Customer success leader
“What are customers telling us, and have we closed the loop?
Chief transformation officer
“Does the organization understand what is changing and why?
Board and investors
“What changed since the last update, and what is management asking of us?
What it replaces
Retire the workarounds — on your schedule.
- Status decks rebuilt every week
- Stand-alone release-note and roadmap tools
- Customer feedback lost in inboxes
- Roadmap slides circulated by sales and success
How it is licensed
Broadcast is an optional add-on to Steer. It can publish from anything in Dotwork — strategy, programs, roadmaps, releases and outcomes.
Always enterprise-wide. One Industry Strategy Edition is included with every Steer license.
See pricingMore in Steer
Same model. Next question.
The model underneath
Every module makes the next one smarter.
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating ModelBe Decisive.Build Fast.Connect Everything.
Start ConnectingSolutions
Platform
Resources
© 2025-2026 Dotwork, Inc. All rights reserved.