> ## Documentation Index
> Fetch the complete documentation index at: https://kb.manage.management/llms.txt
> Use this file to discover all available pages before exploring further.

# Communication

> Use announcements, communications, voting, and meetings to keep residents informed and involved

## Overview

Manage.Management has more than one communication surface:

* **Announcements** as a surface for resident-facing updates and notices
* **Communications** for structured management messaging, templates, batches, and audit history
* **Voting** and **Meetings** for participation and formal decision-making

## Creating Announcements

<Steps>
  <Step title="Navigate to Announcements">
    Open **Announcements** from the sidebar. Use it as the building's update surface for resident-facing notices and operational messages.
  </Step>

  <Step title="Write Your Message">
    Create your announcement with:

    * **Title**: Clear, descriptive headline
    * **Message**: Enough context for residents to understand what is happening and when
    * **Category / priority**: Use a label that helps people scan the update later
  </Step>

  <Step title="Pin or update when needed">
    Use announcements for operational updates, recurring reminders, and resident-facing notices that people may need to revisit later.
  </Step>
</Steps>

### Announcement Best Practices

<CardGroup cols={2}>
  <Card title="Clear Titles" icon="heading">
    Use descriptive titles: "Water Supply Interruption - 15 March" not "Important Notice"
  </Card>

  <Card title="Include Details" icon="list">
    Cover what is happening, who is affected, when it matters, and what residents need to do
  </Card>

  <Card title="Set Urgency" icon="bell">
    Reserve urgent language for genuine emergencies or time-sensitive disruption
  </Card>

  <Card title="Follow Up" icon="reply">
    Close the loop when a repair, vote, or meeting outcome is complete
  </Card>
</CardGroup>

## Using the Communications workspace

The dedicated **Communications** area is aimed at management users who need more structure than a simple announcement.

<Steps>
  <Step title="Choose a template or start fresh">
    The compose workflow begins with a template library so regular building communications stay consistent.
  </Step>

  <Step title="Select recipients">
    Build a recipient list before you customise the message.
  </Step>

  <Step title="Review and customise the content">
    Adjust subject and body text, preview the final message, and then send when ready.
  </Step>

  <Step title="Track batches and history">
    Use batches, inbox, templates, audit log, and linked documents to manage repeated communication at building scale.
  </Step>
</Steps>

## Voting and meetings sit alongside communications

Use the nearby **Voting** and **Meetings** areas when the goal is participation or a formal record, not just an update.

<AccordionGroup>
  <Accordion title="Voting">
    Create polls, monitor participation, and let residents respond from the same building workspace.
  </Accordion>

  <Accordion title="Meetings">
    Schedule meetings, handle meeting requests, run date polls, and keep agenda items, documents, attendees, resolutions, and minutes together.
  </Accordion>
</AccordionGroup>

## Keep messages and records connected

<CardGroup cols={2}>
  <Card title="Link documents" icon="folder-open">
    Store notices, minutes, budgets, and supporting records in the document repository so communications have context
  </Card>

  <Card title="Reuse templates" icon="file-text">
    Standard templates help management teams stay consistent across buildings and repeated workflows
  </Card>

  <Card title="Separate updates from decisions" icon="scale">
    Use announcements for news, voting for decisions, and meetings for structured discussion and records
  </Card>

  <Card title="Think by audience" icon="users">
    A resident update should read differently from an internal management-company communication run
  </Card>
</CardGroup>

<Tip>
  If a message changes money, access, safety, or meeting attendance, pair the update with the relevant document or follow-up workflow instead of relying on one announcement alone.
</Tip>