An equipment maintenance log portal is where a maintenance team keeps each machine's service and repair history on the machine's own record and gets a reminder before its next service is due. The loader's last oil change lives on the loader, not in a greasy logbook in the cab.
Pattern: TrackingDescribe it to Pory
“We run about 60 machines across two yards: loaders, forklifts, compressors. We need each machine's service history in one place and a reminder when a service is coming due.”
Machines
| Machine | Type | Service due | Status | Yard | |
|---|---|---|---|---|---|
| CAT 950 loader #2 | Wheel loader | 2 Oct 2026 | Running | North yard | |
| Toyota forklift #7 | Forklift | 29 Sep 2026 | Service due | South yard | |
| Komatsu PC210 excavator | Excavator | 19 Oct 2026 | Running | North yard | |
| Atlas Copco compressor | Air compressor | 21 Sep 2026 | In workshop | South yard | |
| Cummins 150kVA generator | Generator | 12 Oct 2026 | Running | North yard | |
| Hyster forklift #3 | Forklift | 14 Sep 2026 | Out of service | South yard |
Showing 1–6 of 6
In plain English
An equipment maintenance log portal is where a maintenance team keeps each machine's service and repair history on the machine's own record and gets a reminder before its next service is due. The loader's last oil change lives on the loader, not in a greasy logbook in the cab. It follows the Tracking pattern: a person's or asset's history, built up over time. Pory generates it from a plain-English description, with a login for each role (maintenance manager and technician) that shows only what that role should see, and flat pricing with unlimited technicians.
What it does
Service history was a logbook in each cab and a spreadsheet the manager updated when they remembered. Technicians log each service, repair and part against the machine, with the date and the engine hours. Open the CAT 950 loader and its record is right there, so warranty claims and "when was this last done?" take seconds, not a hunt through the cab.
The only sign a service was due was a sticker on the dashboard, faded to blank by its second month. Each machine carries its next service due date, and as it gets close a reminder lands in the technician's inbox here and by email. No forklift runs three weeks past its service again because nobody could read the sticker.
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 technicians, flat price.
