My claims
Insurance claims portal
An insurance claims portal is where policyholders file a claim with photos and follow it to settlement, and adjusters approve or decline each claim with the reason on the record.
Pattern: RequestsDescribe it to Pory
“We're a regional insurer. Policyholders should file claims with photos of the damage, adjusters approve or decline each one, and the claimant can see where their claim is up to.”
Viewing as
In plain English
What is an insurance claims portal?
An insurance claims portal is where policyholders file a claim with photos and follow it to settlement, and adjusters approve or decline each claim with the reason on the record. 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 (policyholder and adjuster) that shows only what that role should see, and flat pricing with unlimited policyholders.
What it does
Policyholders file a claim with photos while the damage is fresh
Claims started with a phone call, a claim number read out twice and photos sent to an inbox nobody matched to the file. In Pory the policyholder uploads photos of the damage, picks the claim type, and gives the date and an estimated cost. The adjuster gets a complete claim on day one, not a callback list.
Forms to submit a recordDone by: Policyholder
Adjusters approve or decline with the reason written on the claim
Decisions went out in letters that took a week to arrive and explained very little. The adjuster opens the claim, looks at the photos and the estimate, and approves or declines it; a decline carries a note the policyholder can read. Fewer complaints start with "nobody told me why".
Approve / reject with a reasonDone by: Adjuster
Claimants see their claim move from submitted to settled
The claims line spent most of its day answering "where's my claim up to?" Each policyholder sees their own claims move from Submitted to Under assessment, Approved and Settled. The phone queue shortens, and the people still calling have a question worth an adjuster's time.
Status tracker for the submitterDone by: Policyholder
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
Your insurance claims portal, live today.
Describe it in a sentence and send the invite. Unlimited policyholders, flat price.