All Docs
FeaturesBlockManOSUpdated March 11, 2026

Mission Gap: Owner Communication & Noticeboard

Mission Gap: Owner Communication & Noticeboard

Status: 🔴 Unbuilt
Severity: High
Identified in: v1.0.17
Category: Core Functionality

Overview

The Owner Communication & Noticeboard feature is a critical missing capability in the platform. As of v1.0.17, there is no way to send development-wide notices to unit owners via email or the owner portal. This page documents the gap, its impact, and the planned scope of the feature when it is built.


What is Currently Missing

1. Broadcast Messaging to Unit Owners

There is no mechanism to compose or send a notice to all owners in a development. Common notices that must be sent in Irish block management include:

  • AGM and EGM scheduling
  • Emergency service interruptions (water, electricity, lift outages)
  • Planned maintenance and access restrictions
  • Service charge demands and reminders
  • General management circulars

None of these can currently be delivered via the platform.

2. Owner-Facing Noticeboard / Portal

The owner portal has no noticeboard section. Owners have no in-portal destination to view current or historical notices from their management agent.

3. Owner-Facing Email Templates

The email template library is scoped entirely to internal agent and team-member notifications. There are no templates for:

  • AGM / EGM notice
  • Works or planned maintenance notice
  • Service interruption alert
  • General owner circular

4. Notification System Scope

The existing in-app notification system serves agents and team members only. There is no owner-facing notification or alert delivery channel.


Impact

Affected PartyImpact
Management AgentsCannot meet OMC communication obligations through the platform; must use external tools
Unit OwnersReceive no platform-originated communications; unaware of AGMs, maintenance, or urgent notices
OMC ComplianceAGM notice obligations under the Multi-Unit Developments Act 2011 cannot be fulfilled via the platform
Audit TrailNo record of owner communications exists within the system

Planned Feature Scope

The following capabilities are required to fully close this gap. None of these are implemented yet.

Broadcast Notices

  • Compose a notice with subject, body (rich text), and attachments
  • Send to all unit owners in a development, or target a specific block/staircase
  • Delivery via email and owner portal simultaneously
  • Schedule notices for future delivery

Owner Portal Noticeboard

  • Dedicated noticeboard section visible to authenticated owners
  • Notices displayed in reverse-chronological order
  • Unread indicator per notice
  • Historical archive of all past notices

Email Templates for Owners

  • AGM Notice — formal meeting notice compliant with MUD Act 2011 requirements
  • EGM Notice — extraordinary general meeting notice
  • Works Notice — planned maintenance or contractor access
  • Service Interruption — urgent, time-sensitive service alerts
  • General Circular — free-form management communication

Delivery & Audit

  • Per-notice delivery report (sent, bounced, opened)
  • Full audit log of all owner communications stored against the development record
  • Resend capability for bounced or undelivered notices

Related Legislation

  • Multi-Unit Developments Act 2011 — imposes obligations on OMCs to give adequate notice of AGMs and EGMs to unit owners
  • GDPR / Data Protection Act 2018 — owner contact data used for communication must be managed lawfully; opt-out and consent records required

Notes for Developers

  • The existing notification system (/notifications) must be extended or a parallel owner-communication service created — the current system is not architected for external (owner-facing) delivery
  • Owner email addresses are held in the unit owner record and must be the source list for broadcast sends
  • Bounced email handling will require webhook integration with the transactional email provider
  • The noticeboard must respect development-level data isolation (owners in Development A must not see notices for Development B)

This page will be updated when implementation begins and again upon feature release.