Skip to main content
Communications Hub

​
Overview

Communications in Manage.Management has two layers:
  • Announcements for building-wide updates that residents need to read and revisit
  • Communications for management-led messaging with templates, batches, inbox views, and audit history

​
How the tools differ

Announcements

Best for resident-facing updates, reminders, notices, and ongoing building information.

Communications workspace

Best for structured communication runs where templates, recipients, previews, and history matter.

Voting and meetings

Use adjacent workflows when the goal is participation, scheduling, or a formal record rather than a simple update.

Documents

Pair important messages with the documents residents need to understand the context.

​
What management users can do

Start from a template when you need a repeatable communication pattern across one or more buildings.
Build the audience first, then review how the final communication will appear before sending it.
Use the wider communications surface when the message needs traceability beyond a one-off announcement.
Finance changes, maintenance work, meetings, and governance updates are easier to trust when the communication points back to the source workflow.

​
Good public-facing practice

Choose the lightest-weight tool that fits

Use an announcement for a straightforward update, and the communications workspace when the job needs more structure.

Write for residents first

Even when the trigger is an internal workflow, the published message should explain what residents need to know or do.

Link supporting records

Important updates are stronger when they reference the relevant notice, budget, minute, or issue record.

Keep the trail tidy

Reuse templates and shared records so repeated building communications stay understandable over time.