Neutrality
Proposals are sealed, and we compete like anyone else
VendoRFP is run by a company that also serves communities as a pool vendor. This page says exactly who can open a proposal on this platform, and what happens on the RFPs where our own company competes.
Who sees what
Three readers, three views
What a community sees
The community that published an RFP reads every proposal sent to it — the vendor, the price and the proposal itself — and it chooses who it contracts with.
What a vendor sees
A vendor reads the RFP it opened and the proposal it sent, and only those. The row-level rule on the proposals table is keyed to the vendor on the proposal, so the same limit holds on every screen and in the live feed.
What VendoRFP staff see
Inside the product, a staff account reaches proposals through one screen, the admin RFP list, and that screen applies the recusal on the server before any row is sent to a browser.
Recusal
Our own company is a vendor like any other
On VendoRFP the company that runs the platform enrolls, is verified and sends proposals through the same door as every other vendor, with the same account type and the same rules.
Wherever that company has sent a proposal, every VendoRFP admin account linked to it is recused from that RFP: the admin screen keeps the proposal count and the 72-hour clock, and prints this sentence in place of the rows.
You are recused from this RFP: a vendor linked to your account has sent a proposal on it, so the proposals stay sealed to you. The community that published it reads every proposal; the count and the clock are unaffected.
How this is checked
A script opens two real vendor sessions on one RFP and reads as each of them, then reads as the community and as a recused admin. It runs against the live database, and the sentences on this page are pinned to it by a test that fails the build if either changes on its own.