How a request works
Take a warehouse-to-office conversion. The drywall crew hands over the office floors, the stair cores and the corridor walls, and somebody has to prime and finish all of it before the fit-out crews arrive. That is the scope this page follows. It is a real shape of work, it is one of the three trades VendoRFP verifies on a job, and nothing below it is a hypothetical about a feature — it is what happens when you press publish.
The address and the scope
The site address is the whole of what the platform needs to open a file. There is no boundary to draw and no survey to attach: a painted wall is priced from its own square footage, not from the ground the building sits on, and the product only holds a drawn boundary where the price genuinely comes off it. You name the trade, write the scope in the same words you would put in a subcontract exhibit, and set the day you want answers by.
The conversion’s street address. Every visit, certificate, proposal and invoice that follows is filed under it, which is what makes a closeout binder something you open rather than something you assemble.
Prime and finish the office floors, the stair cores and the corridor walls, to the finish schedule, after drywall handover. Plain words, because the company reading it prices from them.
The limits your subcontract’s insurance article already states, typed against the paint trade and marked required or preferred. They print inside the request, so a company reads them before it decides whether to answer.
Answers close on the Friday before the fit-out contractor mobilises, which is the only date on this job that matters to the paint scope.
The gate fires first
This is the part of the run that is unlike anything a folder of certificates can do. The check does not happen at award, and it does not happen when somebody notices during buyout. It happens when a company tries to send you a proposal, and the proposal does not get made.
Before the price exists
A painting company reads your request, decides to answer, and the arithmetic runs on its file before anything reaches you. Every line you marked required is compared against what its certificate says it carries.
Named, not implied
The company is told which line, what it carries, what you require, and the difference between them. That is an instruction its broker can act on inside a week, which is the difference between a company that raises its limit and a company that never understood why it stopped hearing from you.
On both sides
You do not see the refusal as a task. You see the proposals from companies whose file already cleared, and the file is what cleared it — not a phone call your coordinator made on a Thursday.
Preferred lines
A line marked preferred rather than required does not stop anybody. The gap is calculated all the same and shown to you beside the price, so the trade-off is one you make with the figure in front of you.
On this job that is the whole of buyout risk on the paint scope: the companies that answered had already filed general liability and workers’ compensation, and painting adds no third document because no state issues a paint licence to require.
Who sees it
The request goes out to companies VendoRFP has verified for painting. It is not an advertisement and it is not open to whoever finds it. What it deliberately does not carry is a way to route around it: a company that wants this scope answers the request.
Printed on the face of the request
Issued through VendoRFP. Vendors send their proposals back on this site. No phone number or email address is published with this RFP.
Every project executive who has published a scope knows the week that follows it. This line is the reason that week does not happen at seven in the morning.
What comes back
Each proposal prices the scope you wrote and says how the company would staff and sequence it against your handover date. You read them beside each other rather than opening each one in turn and building a comparison sheet, and every company in front of you is already carrying the cover your subcontract demands.
The scope you wrote is the scope that comes back priced, which is what makes two answers comparable at all. A company that wants to qualify something says so in its own note rather than by pricing a different job.
Crew size, sequence, and what they need from you and when. On a conversion with a fit-out contractor behind you, that is often the half of the answer that decides it.
Insurance read against your figures, dates held with the certificates, and the credential the trade requires where one exists. Nothing on this screen is waiting on a document you have not seen.
The award and the record
A signed subcontract moves the paperwork rather than ending it. Visits are logged under the conversion’s address with the crew’s photographs attached; invoices arrive with their own numbers and their own state — sent, viewed, paid — and are filed under the same address as the proposal you awarded. Both figures are in front of you when you check one against the other.
What your bookkeeper gets
Pick a date range and download it. These are invoice and payment exports — a period of money in and out. They are not a pay application, and nothing here produces one.
The same run works for the other two job-site trades, with one difference on the way in: HVAC adds an EPA 608 certification and electrical work adds an electrical contractor license. Everything after the award is identical, because the file the job keeps does not care which trade filled it.
Publish a scope against a job address, and the companies that answer have already been measured against your own insurance article. Award one, and every visit, certificate and invoice after it lands under the same address.
Job-site tradesAdditional insured endorsementsSubcontractor prequalification