It starts with a text message on a Saturday morning: "Hey, just checking on that fence repair request I sent in October." The board member checks their email. They scroll the community Facebook group. They dig through old text threads. They cannot find it. Three more messages arrive before lunch — different homeowners, different issues, same question: any update?
This is not a bad-volunteer problem. It is a system problem. When homeowners have no structured way to submit requests and boards have no centralized place to track them, every request lives wherever it landed: an email that arrived when the treasurer was out of town, a Facebook comment buried under forty replies about the parking lot, a voicemail that sounded urgent but never got written down.
The cost is not just inconvenience. Maintenance requests that fall through the cracks turn small problems into expensive ones: the roof flashing a homeowner reported in March that got fixed in September after water damage had spread. Architectural review requests that were never acknowledged, so the homeowner concluded that silence meant approval, built the deck, and now the board is dealing with an unapproved-improvement dispute. General inquiries about community rules that went unanswered for two weeks, leading the homeowner to assume the board simply does not care.
Communities across Oklahoma City, Tulsa, Dallas, and Central Florida that manage requests through spreadsheets or general-purpose email inboxes hit the same wall: the system breaks down the moment volume increases or a board member turns over.
What homeowners actually expect
Homeowners in 2026 have a reference point for what a request experience should feel like. They file insurance claims online and get a confirmation number within minutes. They return items on Amazon and track the return status in real time. They open a support ticket at work and receive automated acknowledgment before they refresh the page.
When they contact their HOA about a broken gate and hear nothing for three weeks, the contrast is jarring. The gap is not in their expectations — it is in the board's tools.
A working request system needs to do three things: confirm receipt immediately, give the homeowner visibility into status, and create a record both parties can reference if the issue is ever disputed. None of those things happen reliably in an email inbox shared among four volunteers with day jobs.
How LotWize's request management system works
LotWize builds a structured request workflow into both the homeowner portal and the board dashboard. Every request a homeowner submits creates a permanent, timestamped record with a documented chain from submission to resolution.
Step one: homeowners submit from the portal — no email required
Inside the LotWize homeowner portal, residents see a Requests section showing every request they have previously submitted, along with its current status. A New Request button opens a submission dialog with three fields: request type, title, and description.
The submission takes under two minutes. There is no phone call to make, no email address to remember, no waiting to reach a board member who may or may not check messages that week.
Step two: AI classifies the request before it reaches the board
Here is where LotWize does something most HOA software does not: as the homeowner types their description, AI reads the text and automatically identifies the correct request type.
A homeowner who writes "Water is coming from under the sidewalk near the mailboxes" gets their type auto-classified as Maintenance. A homeowner who writes "I want to repaint my front door dark green, do I need board approval?" gets classified as Architectural Review, with the type pre-selected in the form. A homeowner asking "Can we reserve the clubhouse for a graduation party?" gets routed to General Inquiry.
For high-confidence classifications, the type field is auto-selected before the homeowner submits. They can override it manually, but in the vast majority of cases the AI gets it right on the first read.
This matters for boards because requests arriving in the correct category can be routed immediately — maintenance issues go to the facilities contact, ARC requests go to the architectural committee chair, general inquiries go to whoever handles community questions. Without classification, the first thing the board does with every request is figure out what kind of problem it is before they can assign it. That step is handled before the request even reaches them.
Step three: the board sees every request in one dashboard
On the board side, the Requests dashboard shows all open and historical requests in a single, sortable list. Each entry displays: the request title, the request type, the submitter's name, the property address, the lot number, the submission date, and the current status.
An Open badge at the top of the dashboard shows how many requests are currently waiting for a response. This is a live work queue: if the board has six open requests and responds to four, the badge drops to two. The board always knows exactly what needs attention, without digging through email threads or remembering who sent what.
Step four: the board responds and updates status
Clicking into any request shows the full homeowner submission — title, description, property, and submitter — alongside a simple response form.
The form has two elements: a Status dropdown and a Board response note field.
The board updates the status to match where the request actually stands:
- Open — received, not yet reviewed
- In Review — the board or a vendor is actively addressing it
- Resolved — the issue has been fixed or the request has been approved
- Closed — complete, no further action needed
The board response note is a plain-text field for communicating directly with the homeowner. For a maintenance issue it might read: "We've scheduled a plumbing vendor to inspect on June 28. We'll update you once we have a repair estimate." For an architectural review: "Your deck plans are approved as submitted. Please retain a copy of this approval confirmation for your records."
When the board clicks Save & Notify Homeowner, the update is saved and the homeowner is notified automatically.
Step five: the homeowner sees the update in the portal
Back in the homeowner portal, each request card shows the current status, the submission date, the resolved date if applicable, and the full board response note. The homeowner can see at a glance whether their fence repair is being scheduled, under vendor review, or already resolved — without sending a follow-up email and without waiting for a callback.
This closes the loop that most self-managed HOA boards leave open. The board's note is visible. The status is visible. The date the board responded is visible. If a homeowner ever asks "what happened to my request," both the homeowner and the board are looking at the same documented record.
Why architectural review requests carry more risk when untracked
Maintenance requests get the most attention, but architectural review requests carry greater legal exposure when they fall through the cracks.
In many states — including Florida, Texas, and Oklahoma — governing documents (and in some cases statute) contain a "deemed approved" clause: if the board fails to respond to an ARC request within a defined window, often 30 to 60 days, the homeowner may proceed with the improvement as if it were approved. A board that allows an ARC request to sit unanswered in an email inbox long enough may lose the right to enforce against the project it forgot to review.
When an architectural review request is submitted through LotWize, the submission timestamp is automatic and immutable. The board's response — whether an approval, a denial, or a request for additional plans — is documented with the date and time it was communicated. If a homeowner later disputes a violation notice related to an unapproved project, both parties have access to the same request record. Communities that have experienced ARC-related disputes find that a clean documented response record is the most effective defense available to the board.
The types of requests boards track most
Based on the most common board workflows, three request types cover essentially everything homeowners contact their HOA about:
Maintenance requests include any community-owned infrastructure or common-area issue: pool pump noise, broken perimeter fencing, parking lot potholes, non-functioning streetlights, damaged irrigation heads, pool deck cracks. These are the requests where the board's job is to receive, acknowledge, and schedule a vendor.
Architectural review requests include any homeowner improvement that requires board approval under the CC&Rs: exterior repaints, new fences, deck additions, garage door replacements, storage sheds, driveways, accessory dwelling units. These are the requests where documentation of the board's decision matters most, because the improvement is permanent.
General inquiries include everything else: questions about parking rules, requests for amenity access codes, event reservation inquiries, questions about upcoming meetings, requests for a copy of the governing documents. These are the requests that tend to be highest in volume and lowest in individual complexity — and where a self-service answer in the portal can save the board the most time.
What changes when requests stop falling through the cracks
Self-managed HOA boards in Oklahoma City, Tulsa, Dallas, and similar markets consistently rank "keeping up with homeowner communications" as their highest-friction ongoing task. Most of that friction does not come from the volume of requests — it comes from the absence of a system. Requests arrive in mixed channels, get lost or overlooked, and resurface weeks later as complaints or disputes.
A centralized request system does not reduce the number of requests a board receives. It eliminates the overhead of tracking them across three different channels, eliminates the credibility damage that follows a missed follow-up, and creates the documented audit trail the board needs if a request ever becomes a legal matter.
For self-managed associations without a property management company to route and prioritize incoming issues, the LotWize request system provides the same operational structure that professional managers use — without the management fee.
Clear your open request backlog
LotWize's homeowner portal and board request dashboard are included on every plan. Homeowners submit from their phone or laptop in under two minutes. The board sees every open item, responds with a note, and updates status in under two minutes per request. No email threads. No missed follow-ups. No "whatever happened to" conversations at the next board meeting.
Start your free LotWize trial and put a system behind every request your community sends in.