Resident
Sees only their own service requests.
- Pages
- Home, My service requests, My photos and forms, Pickups and road work, Service notices
- Can start
- Report an issue, Upload a photo or form
Report an issue
Report → assign → fixed
Municipal service request portal for residents
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
How Pory sets it up
Pory gives every resident, dispatcher and crew lead a sign-in of their own. Each resident sees only their own service requests. It covers report → assign → fixed. Service requests, photos and evidence, pickups and road work and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Residents report a pothole in two minutes, no account needed
Reports used to come in by phone, email, the city'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
Who sees what in a municipal service requests portal
Every person signs in to their own view. This is what each role in the demo gets.
Dispatcher
Sees every service request in the portal.
- Pages
- Home, Service requests, Photos and evidence, Calendar
- Can start
- Ask for a photo or form
Crew lead
Sees the service requests assigned to them.
- Pages
- Home, Assigned to me, Field guide
What’s in the municipal service requests portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Service requests
- Issue (text)
- Category (choice: Pothole, Streetlight out, Graffiti, Illegal dumping, Missed trash pickup, Fallen tree)
- Reported by (link)
- Location (text)
- Photos (file)
- Details (long text)
- Status (choice: Reported, Assigned, In progress, Resolved, Declined)
- Crew lead (link)
- Reported (date)
Photos and evidence
- Item (text)
- Service request (link)
- Needed by (date)
- Status (choice: Requested, Uploaded, Checked)
- File (file)
- Resident (link)
Pickups and road work
- Event (text)
- Date (date)
- Kind (choice: Trash pickup, Crew visit, Road work)
- Resident (link)
Team
- Name (text)
- Role (text)
The parts behind this portal
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Collect
1 partPublic pages
An application page, a notice board, an open directory: pages and forms anyone can use without signing in, on your domain.
Decide
2 partsStatus tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Control
3 partsWho sees which records
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A resident signs in with a link sent to their email and lands on Home. They see Home, My service requests, My photos and forms, Pickups and road work and Service notices, and only the service requests that are theirs. From there they can use “Report an issue” and “Upload a photo or form”.
The public pages: Report an issue and Service notices. Anything about a particular person stays behind their sign-in.
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
Build your municipal service requests portal with Pory
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited residents.