Announcement Composer

Draft and preview company or team announcements with audience rules, scheduling, attachments, and delivery settings. This example brings Draft and Audience together so team members can find the next task without losing context.

It includes representative records such as Quarterly product update and Office policy change. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Announcement Composer
Use this template in Figr

Template facts

Screen

Builder

Primary action

Publish announcement

Pattern

Builder

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to publish announcement while keeping audience, channels and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Draft gives users an obvious place to start.
  • Supporting view: Audience keeps the related context close.
  • Primary action: Publish announcement stays visible when people need it.
  • First signal: Audience shows a useful value (842).
  • Second signal: Channels gives additional context (4).
  • Sample record: Quarterly product update.
  • Next record: Office policy change.

States worth designing

  • No configuration selected: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Invalid rule or block: say what changed, protect progress, and offer a clear next step.
  • Preview generated: say what changed, protect progress, and offer a clear next step.
  • Publish blocked: say what changed, protect progress, and offer a clear next step.
  • Version restored: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Draft → Audience → Publish announcement → Review outcome

Patterns used

Builder, Draft, Audience, contextual actions, error recovery

Why these choices work

Show constraints before adding blocks, keep a usable preview and protect unsaved changes as people test a different direction.

Pay attention to draft and audience. People need to distinguish Quarterly product update from Office policy change. Keep audience visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Publish announcement”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Message Search, Notification Center, Channel Directory.

Start from this in Figr

Design a announcement composer screen inside our existing product. Use our current components, tokens and content language. Include Draft and Audience views, credible records like Quarterly product update, and a clear “Publish announcement” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr