An RFP and bid response portal is where vendors submit bids with their documents attached, each evaluator files their own score on every bid, and the procurement lead awards the contract with the reason on the record.
Pattern: RequestsDescribe it to Pory
“Our council puts out a handful of RFPs each year. Vendors submit bids with their documents, a panel of evaluators scores each bid, and procurement awards the contract.”
My bids
| Bid | Vendor contact | Bid documents | RFP | Status | |
|---|---|---|---|---|---|
| Brightline Civil – library roof | Hannah Schultz | 5 files | Library roof replacement | Under evaluation | |
| Brightline Civil – parks mowing | Hannah Schultz | 3 files | Parks mowing 2027 | Under evaluation |
Showing 1–2 of 2
In plain English
An RFP and bid response portal is where vendors submit bids with their documents attached, each evaluator files their own score on every bid, and the procurement lead awards the contract 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 (vendor, evaluator and procurement lead) that shows only what that role should see, and flat pricing with unlimited vendors.
What it does
Bids used to arrive as emails that bounced for being too large, followed by a file-sharing link and an apology. In Pory a vendor's bid holds its documents, from the pricing schedule and method statement to insurance certificates, all attached to the record. Each vendor sees only their own bids, and procurement stops hunting through inboxes on closing day.
Evaluation used to mean one scoring workbook passed around by email, with a different copy on every laptop. In Pory each evaluator opens a bid, reads the documents, and files a score out of 10, a recommendation and notes as their own record on that bid. Procurement opens the bid and sees each panellist's score listed separately, ready for moderation.
The reason a contract went to one bidder used to live in a panel meeting's minutes, filed somewhere. The procurement lead opens a bid, reads each evaluator's score and notes, and awards or rejects it, writing the reason on the record. When an unsuccessful vendor asks for a debrief, the answer is already written down.
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 vendors, flat price.
