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 city 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
| Ridgecrest Civil, library roof | Library roof replacement | 5 files | 184000 | Shortlisted | |
| Ridgecrest Civil, parks mowing | Parks mowing 2027 | 3 files | 96500 | Under evaluation |
Showing 1–2 of 2
In plain English
Pory gives every vendor, evaluator and procurement lead a sign-in of their own. Each vendor sees only their own bids. It covers submission & evaluation. Bids, evaluations, documents, solicitations, key dates and team live in Pory's own database, so there's no spreadsheet to keep in sync.
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 work plan 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 panelist's score listed separately, ready for the consensus meeting.
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.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own bids.
Sees every bid in the portal.
Sees every bid in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
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
Upload and view files on the record they belong to, not in a folder named FINAL v2.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
A reviewer's score, a coach's feedback, a clinician's note, kept on the record it belongs to.
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.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
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 vendors.
