Before it's a recall petition
Hear it from the homeowner,
not from the board meeting.
A broken pool latch, a dead streetlight, a gate stuck open since Friday. The homeowner who spots it has no fast way to reach the board, so it stews on Nextdoor instead. Put a code at the amenity and you hear the exact problem the day it broke, in time to fix it and text back.
No app for homeowners to download. It works over text.
Homeowner on Maple
Pool gate · photo attached
“Pool gate self-latch is broken, it just swings open. A toddler could walk right in. Please fix before the weekend.”
Latch replaced same day, photo on file. 3 neighbors who flagged it got a text back.
heard, fixed, and dated before the meeting
What you'll actually hear
The stuff that turns into a board-meeting blowup.
“The pool gate self-latch is broken, it just swings open. A toddler could walk right in.”
pool gate“Streetlight has been out at the Elm Court cul-de-sac for two weeks. It is pitch black walking the dog at night.”
Elm Court“The irrigation head by Building C runs at 3am and the sidewalk is iced over by morning. Someone is going to slip.”
Building C“Front entry gate arm has been stuck open since Friday. Anyone can drive right in.”
front entry gate“Mailroom inner door does not lock anymore. Packages are sitting out where anyone off the street can grab them.”
mailroom“Clubhouse stair handrail is loose, the bottom bracket pulled out of the wall. My mom uses that rail.”
clubhouseThe gap
Silence is what organizes the recall.
A homeowner who finds the broken latch has nowhere good to take it. They post on Nextdoor and a dozen neighbors pile on, they wait three weeks for the next board meeting, or they start asking who else is fed up. That is how a single open gate becomes a recall petition.
Give them a code at the gate and the board hears it the morning it broke. A vendor fixes it, everyone who flagged it gets a text with the date, and the complaint that could have organized a special election is a closed issue with a photo on file.
How it works
Three steps, broken latch to text back.
- 01 7:40a
A homeowner scans the code where it broke
A small placard at the pool, the gate, the mailroom, and the clubhouse. No app, no portal login, no waiting for the next board meeting. They type what is wrong, add a photo, and leave a number to hear back. Ten seconds, standing right at the broken latch.
- 02 7:41a
It lands in one inbox, dated and pinned
Every report from every amenity feeds one place, sorted, with the exact spot and a photo. Five neighbors flagging the same dead streetlight group into one issue. A broken pool latch or a loose handrail jumps to the top.
- 03 That day
A vendor handles it and the board texts back
Mark it resolved and everyone who flagged it gets one text with the date it was fixed. The homeowner who was about to post on Nextdoor hears that the gate is latching again, from the board, before the thread starts.
Heard and resolved, with the date
“The board ignores us” is the story that ends a board. The record ends the story.
Put a placard at the pool, the gate, the mailroom, and the clubhouse. A homeowner taps the one in front of them, so the board gets the exact amenity and a photo, not a vague gripe at open forum. Every report is stamped with the day it came in.
A bare log of known hazards is the notice a plaintiff's attorney wants after a fall. So the same record carries the fix and the date it was done, with the photo. You can show a homeowner, or a court, that the board heard it and closed it.
Hear it the day it broke, not at the next meeting.
Start free, put a code at the pool, gate, mailroom, and clubhouse, and let a homeowner report the exact hazard so the board fixes it and texts back, with the date on file.
Start free