Jobs
Jobs by status
Add
New1
Assigned1
On site1
Complete2
Cancelled1
Field-service dispatch portal
A field-service dispatch portal is where a dispatcher assigns each customer job to a technician, the technician sees only their own jobs, and completes each one on site with photos and a checklist. Customers see their own jobs and where each one stands.
Pattern: RequestsDescribe it to Pory
“Customers report jobs that need doing, our dispatcher assigns a technician, and the technician works through a checklist and adds photos on site before marking the job complete.”
Viewing as
In plain English
What is a field-service dispatch portal?
A field-service dispatch portal is where a dispatcher assigns each customer job to a technician, the technician sees only their own jobs, and completes each one on site with photos and a checklist. Customers see their own jobs and where each one stands. 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 (customer, dispatcher and technician) that shows only what that role should see, and flat pricing with unlimited customers.
What it does
Dispatchers put each job in front of the right technician
Jobs were dispatched by phone call and text, and the whiteboard back at base was out of date by 9am. The dispatcher opens a new job, picks the technician, and it appears on that technician's list with the address and job type. The board shows what's still unassigned, so no one's hot water waits because a text went unread.
Assign to a personDone by: Dispatcher
Technicians start the day with only their own jobs in view
Technicians got a group text listing every job for the day and worked out for themselves which were theirs. Each technician signs in to a list of only the jobs assigned to them, with the address, the job type and the completion photos. Nobody turns up at a job that was given to someone else.
Role & row accessDone by: Technician
Technicians tick off each step and add photos before closing a job
Proof of work was a photo on the technician's own phone and a promise that the filters got cleaned. On site, the technician works through the job's checklist (isolate power, clean filters, test run) and uploads photos to the job before marking it complete. The office stops ringing customers to ask whether the work actually got done.
ChecklistsDone by: Technician
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 field service portals
All field service portalsInspection reports portalChecklist → photos → defects assignedEquipment maintenance logs portalSchedule & historySafety incident reporting portalReport → investigate → closeCleaning & janitorial portalJob checklists & photo proofLandscaping & pool service portalService visits & each client's historyRestaurant & franchise ops portalChecklists & incident logs
Your field-service dispatch portal, live today.
Describe it in a sentence and send the invite. Unlimited customers, flat price.