Report an issue
Report → assign → fixed
Municipal service requests portal
A municipal service request portal is where residents report potholes, broken streetlights and other issues without an account, dispatchers assign each report to a crew and close it once it's fixed, and reporters see where their own requests stand.
Pattern: RequestsDescribe it to Pory
“Residents should be able to report potholes, broken streetlights and graffiti without signing up. Our dispatcher assigns each one to a crew and closes it once it's fixed.”
Viewing as
In plain English
What is a municipal service requests portal?
A municipal service request portal is where residents report potholes, broken streetlights and other issues without an account, dispatchers assign each report to a crew and close it once it's fixed, and reporters see where their own requests stand. 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, dispatcher and crew lead) that shows only what that role should see, and flat pricing with unlimited residents.
What it does
Residents report a pothole in two minutes, no account needed
Reports used to come in by phone, email, the council's social pages and the occasional letter, and someone typed them all into a log. In Pory a resident opens the public form, picks the category, says where it is, adds a photo and a line of detail, with no password to invent. Every report lands in one list instead of five channels.
Public pages & formsDone by: Resident
Dispatchers give each report a crew lead and close it once fixed
Jobs used to be read out over the radio and scribbled on a whiteboard that got wiped every Monday. The dispatcher sees every report on a board by status, names the crew lead it's for, and it lands on that crew's own list. Once the work is done it moves to Resolved, and the whiteboard can go back to being a whiteboard.
Assign to a personDone by: Dispatcher
Residents see their report go from Reported to Resolved
Residents used to report the same pothole three times because nothing told them anyone had seen it. A resident who signs in sees only the issues they've reported, and whether each one is reported, assigned, in progress or resolved. Duplicate reports drop, and so do the calls asking whether anyone's coming out.
Status tracker for the submitterDone by: Resident
The parts every portal is built from
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
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
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.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
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.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
More applications portals
All applications portalsGrant round portalApplications & reviewer scoringScholarship program portalApply → review → awardAccelerator & incubator portalStartup applications & cohortsConference CFP portalTalk submissions & program committeeResearch & IRB review portalProtocol submission & approvalPermit & license applications portalSubmit → review → issueRFP & bid responses portalSubmission & evaluationGrantee reporting portalMilestone reports & disbursements
Your municipal service requests portal, live today.
Describe it in a sentence and send the invite. Unlimited residents, flat price.