What CondoPulse is
CondoPulse is a status page for your building. The same way statuspage.io shows whether a cloud service is up, CondoPulse shows whether your elevators, pool, gym, fire alarm system, parking garage door, and other building systems are working - and keeps a permanent, shared record of every problem from the moment it’s reported to the moment a resident confirms it’s actually fixed.
The point is simple: residents, the board, and management all look at one record. No more “I reported that weeks ago” with nothing to point at, and no more disputes about how long the elevator was really down. The numbers are computed from the incident history everyone can see.
What it tracks
Section titled “What it tracks”Your building is modelled as a small hierarchy:
- Property - the building or complex itself (e.g. Harborview Towers).
- Towers - e.g. Tower A and Tower B.
- Units - individual suites, like
A-1204(Tower A, floor 12, unit 04). - Assets - trackable systems and amenities: elevators, the pool, the gym, garden beds, the fire alarm system, the parking garage door, HVAC, laundry, common areas. An asset belongs to a tower, or to the whole property (the pool, for example).
Every asset has a live status:
| Status | Meaning |
|---|---|
| Operational (green) | Working normally |
| Degraded (amber) | Working, but not fully - e.g. one treadmill down in the gym |
| Down (red) | Out of service |
| Maintenance (blue) | Planned work in progress |
Incidents are the events behind those statuses. An incident is attached to either an asset (“Elevator A2 stuck on floor 7”) or a unit (“Leak under the kitchen sink in B-304”). Each incident has a severity (low / medium / high / critical), a status that moves through a defined lifecycle, a comment timeline, and optional photos.
The incident lifecycle
Section titled “The incident lifecycle”Every incident moves through the same stages:
open → acknowledged → in_progress → resolved → verified- Open - reported, not yet seen by staff.
- Acknowledged - staff have seen it. There are time targets for this step (4 hours for critical issues, up to a week for low-severity ones), and incidents that blow past their target get an SLA breached badge and an automatic severity bump.
- In progress - someone is working on it.
- Resolved - staff believe it’s fixed.
- Verified - a resident confirmed it’s really fixed. This is the part most systems skip: after staff mark something resolved, you get the last word with Confirm fixed or Still broken buttons. Still broken sends it straight back to in-progress. See Following & verified fixes.
Where you’ll use it
Section titled “Where you’ll use it”- The web app - the main status page lives at the site root (
/). It shows a summary banner (how many assets are operational, degraded, down, or in maintenance), every asset with its 90-day uptime bar and 30/90-day uptime percentages, any scheduled maintenance coming up, and recent incident history including how many fixes residents have verified. From there you can open any asset for detail, browse incidents, report a new one at/incidents/new, and find building contacts at/directory. - The mobile app - report issues with your phone camera, get push notifications on incidents you follow, and check status on the go. See The mobile app.
- The lobby kiosk - many buildings run a TV in the lobby showing the
full-screen kiosk view (
/kiosk): a dark, large-type display with the status summary, big uptime bars for every asset, a ticker of open incidents, and the upcoming maintenance strip. It refreshes itself every 60 seconds, so what you see walking past the front desk is live. - QR stickers - assets may have a printed QR sticker (“Scan to report an issue”). Scanning takes you straight to the report form with that asset pre-selected.
What you can do as a resident
Section titled “What you can do as a resident”- See everything public: asset statuses, uptime history, all incidents and their timelines, and the building contacts directory (property manager, superintendent, elevator vendor, after-hours emergency line).
- Report incidents - on web or mobile, with photos, and anonymously if you prefer (your name is hidden from other residents; staff can still see it - see Reporting an issue for the exact semantics).
- Comment on any incident’s timeline.
- Follow incidents and get notified on every status change.
- Verify fixes - confirm or dispute a resolution on any resolved incident.
What you can’t do: change incident statuses (other than the verify step), edit assets, or see other residents’ personal contact details. Those need a board, manager, or admin account - see Roles & permissions.
Why the uptime numbers can be trusted
Section titled “Why the uptime numbers can be trusted”Uptime isn’t typed in by anyone - it’s derived from the incident record. When a downtime incident on an asset is open, that interval counts against the asset’s uptime; when it’s resolved, the clock stops. Planned maintenance windows are excluded, so a scheduled elevator inspection doesn’t show up as an outage. The 90-day bar on each asset paints one thin slat per day - green, amber, red, or blue - so a month of elevator trouble is visible at a glance. Reading uptime bars explains every color and the math behind the percentages.
Because every change - every status transition, every merge, every escalation
- is recorded in an append-only audit log, the history can’t be quietly rewritten. That’s the record your board sees in its weekly digest, and the same record that can be exported as a print-ready report for an AGM.