Accountability,
feature by feature.

01 — Uptime tracking

Uptime for elevators & amenities

CondoPulse treats your building's systems the way a status page treats servers. Elevators, the pool, the gym, the parking garage door, the fire alarm system - each one is a tracked asset with a live status: operational, degraded, down, or maintenance.

Every asset gets a 90-day history bar - one slat per day, colored by the worst thing that happened that day - plus 30-day and 90-day uptime percentages computed from actual incident intervals. Overlapping outages are merged so nothing is double-counted, and every number traces back to incidents anyone in the building can open and read.

“The elevator is fine” and “Elevator A2 was down 26 hours last month - 97.10% uptime” are very different conversations. CondoPulse makes sure you're having the second one.

02 — Incident timelines

Incident timelines with photos

Every incident is a record, not a complaint that evaporates. It opens with a title, description, severity, and optional photos. From there, every status change and update is timestamped and attributed: who acknowledged it, when work started, what the vendor said, when it was resolved.

Photos matter for the problems that are easy to deny and easy to forget - the garden bed that's been weeds for three weeks, the recurring mess in the Tower B stairwell, the third false fire alarm this quarter. A dated photo on a public timeline is the end of “I'll look into it.”

Resolved incidents don't disappear. They stay in the asset's history, which is exactly what makes recurring problems visible: when the same elevator has six entries in 90 days, the pattern is on the record, not in someone's memory.

03 — Reporting

Per-unit & common-area reporting

Problems don't only happen to elevators. A leak in unit 1204, urine in the stairwell on floor 3, a broken light in the parking garage - residents can report against their own unit or any common area, from the web or the mobile apps, in under a minute.

Reports are structured, not a free-for-all: each incident is tied to a specific asset or unit, carries a severity, and lands in front of the people responsible. The board's queue stays triaged, and residents can see their report exists instead of wondering if the email got read.

04 — Roles & accountability

Roles for residents, board, management

Everyone in the building sees the same public record - statuses, incidents, timelines, and the contacts directory. What differs is what they can do with it.

Residents report incidents and comment. Board members and managers acknowledge, post updates, resolve incidents, and manage assets and contacts. Admins handle user roles. Status changes are restricted to board, manager, and admin roles - so a problem is only “resolved” when someone accountable says so, in writing, with a timestamp.

Privacy is part of the design: residents never see each other's personal contact details. The directory of people is for the board and management; the directory of problems is for everyone.

05 — Kiosk & TV mode

Put the status board in the lobby

The record is public - that's the point. Every building gets a public status page, and a full-screen kiosk mode designed for the TV in the lobby: dark background, oversized type, big slat bars readable from the mailboxes, a ticker of open incidents, and the upcoming maintenance strip.

It refreshes itself every sixty seconds with no navigation and no login. Mount a screen, open one URL, walk away. When the elevator's been down for 14 hours, everyone walking in knows - including the board members walking in.

Nothing changes behaviour like ambient visibility. A number on a wall is a promise someone has to keep.

06 — SLA escalation

Issues can't quietly rot

Every incident starts a clock. Time-to-acknowledge targets are set by severity - 4 hours for critical, 24 for high, on down - and a sweep checks them continuously.

If a report sits unacknowledged past its target, CondoPulse doesn't wait politely. The severity is bumped one level, every board member and manager is notified, followers get a push, webhooks fire, and the incident wears an SLA-breached badge in every list until someone deals with it. All of it lands in the audit log.

The result: the cost of ignoring a report is higher than the cost of acknowledging it. Which is the entire idea.

07 — Weekly digest

The week's record, in the board's inbox

Once a week, every board member gets the same email: downtime hours per tower and per asset, new / resolved / verified counts, the oldest still-unacknowledged reports, and what maintenance is coming up.

No one has to remember to check the dashboard, and no one gets to say they didn't know. The digest is the building's weekly minutes, written by the data.

08 — Anonymous reporting & verified fixes

Report without your name. Close without doubt.

Some problems don't get reported because the reporter lives four doors from the problem. Any incident can be filed anonymously - staff can still follow up, but every public view shows “Anonymous resident.” The awkward stuff makes it onto the record instead of into the group chat.

And “resolved” isn't the end of the story. After management resolves an incident, residents - starting with the reporter - are asked to confirm: Confirm fixed moves it to verified; Still broken reopens it. Both are timestamped, both notify followers, both hit the audit log. A fix only counts when the people living with the problem say it does.

09 — Integrations & exports

Plays well with the rest of your stack

The record is most useful when it can leave the building. Email a report in and it becomes an incident. Pipe events out to webhooks (n8n-friendly, HMAC-signed). Export the history as CSV, or print a report page with uptime summaries and per-incident timelines - dated, attributed evidence fit for an AGM package or a Tribunals Ontario filing. Push notifications keep followers' phones in the loop.