My requests
An HOA management portal is where homeowners send requests to the board, the board works through them in the open, and the community manager keeps each home's dues status and violations on record. Residents read the association's notices in the same place instead of on the mailroom corkboard.
Pattern: RequestsDescribe it to Pory
“Our 120-home HOA needs a place where residents submit requests to the board, the board works through them, and our community manager tracks dues status and violations for each home.”
My requests
In plain English
An HOA management portal is where homeowners send requests to the board, the board works through them in the open, and the community manager keeps each home's dues status and violations on record. Residents read the association's notices in the same place instead of on the mailroom corkboard. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (resident, board member and community manager) that shows only what that role should see, and flat pricing with unlimited homeowners.
What it does
Requests reached the board as emails to whoever was treasurer that year, letters in the clubhouse box and complaints at the pool. A homeowner picks the type (an architectural change, a repair, a parking problem), describes it, adds photos and their address. They can see where each request they've made stands, so nobody waits for the next meeting to find out.
Board members forwarded requests between personal inboxes and lost track of who was meant to reply. Every request is a card in its column (Submitted, Board review, Approved, Done, Declined) and a member drags it along as the board decides, with the reason written on the request. The monthly meeting starts from the board, not a stack of printouts.
Violation notes lived in the manager's notebook and a folder of phone photos, so a repeat bin offender looked like a first-timer. The manager files each violation on the home with the date, a photo and where it stands: open, notice sent, resolved or dismissed. Opening 14 Linden Ct shows its violations together, which settles most "since when?" arguments.
Dues status lived in the treasurer's spreadsheet, and the manager had to email them before answering a homeowner. Each home carries its dues status (current, due, overdue or on a plan) and the next dues date, kept up to date by the manager. Answering "am I up to date?" takes a search, not an email to the treasurer and a two-day wait.
Notices went up on the mailroom corkboard and in an email half the community filtered as spam. The board posts notices on a page every resident sees when they sign in: the annual meeting, pool closures, trash days, how to send an architectural request. Nobody has to stand in the mailroom reading thumbtacked paper to learn the pool is closed.
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited homeowners, flat price.