Glossary · Request for quote (RFQ)

RFQ: asking several contractors to quote for a job

A request for quote (RFQ) asks contractors to price a defined scope: labour, materials, access times and compliance requirements. Operators use RFQs when they want prices compared for a defined job, or when policy requires competitive quotes.

OpsChase runs RFQs as a workflow: scope, deadline, requests, comparison, award, then onboarding before the first work order. Quotes sit on the same work order as the job, compared side by side, with compliance and proof on one record.

Why multi-site teams care about RFQs

Multi-site teams ask for quotes all the time: a new site, a one-off project, a trade you rarely need. An RFQ done well gets comparable prices quickly without letting standards slip. Done badly, it becomes a string of phone calls and an unchecked contractor on site.

What a good RFQ looks like

  • A clear scope: the site, the work, access times and what proof will be needed at the end.
  • Compliance requirements stated up front, so firms that can’t meet them don’t waste time quoting.
  • A deadline, and a short list of firms that can actually reach the site.
  • Quotes compared side by side on price, timing and fit.
  • An award followed by onboarding before any work starts.

Common RFQ mistakes

  • Sending an RFQ for every reactive job, which slows urgent work and wears out contractors.
  • A vague scope that produces quotes you can’t compare.
  • Asking firms that cover the capital but not the regional site.
  • Awarding the job and sending the work order the same day, before the checks are done.
  • Forgetting to add the winning firm to your regular list, so the next job starts from scratch.

How RFQs fit jobs tracked until the work is done

In OpsChase, you create an RFQ from a template, choose which vetted firms to ask, and track responses in one place. When nobody responds, deadlines and re-issue rules send a reminder, and assisted RFQ status records phone reminders without skipping checks. On award, onboarding collects licence, insurance, induction and site-access details, and assignment unlocks only after approval. From then on, the new firm’s jobs run with the same tracking and proof as everyone else’s.

Where to start

Pick the trades you ask quotes for most often, and write one RFQ template for each: the scope, the access rules, the proof you expect and the compliance requirements. When the next quote is needed, you send a ready-made request instead of starting from a blank email, and every firm quotes against the same brief.

Pair this with vendor onboarding and prequalification for the checks after award.

On OpsChase: one queue for your team and contractors, each job tracked until the work is done, then photos or sign-off. Book a demo — one site or many.

Is every job an RFQ?
No. Routine work goes to your own team or your contractors. RFQs are for jobs where you want prices compared, or where policy requires quotes.
Can one RFQ cover several sites?
Yes. Multi-site rollups support franchise and national buying.
What happens if nobody responds?
Deadlines and re-issue rules send a reminder, and assisted RFQ status supports phone reminders without skipping checks.
How many quotes should we ask for?
Follow your own procurement policy. For a routine job, a few firms that can actually reach the site are usually enough.
What is the difference between an RFQ and a tender?
A tender is usually a larger, formal process for ongoing contracts. An RFQ is quicker and suits a defined piece of work.
Should the lowest quote always win?
Not always. Price matters, but so do drive time to the site, availability in the window you need, and whether the firm can meet your compliance requirements. A cheap quote from a firm that cannot reach a regional site in time is not a saving.
OpsChaseOpsChase

Start with the part you need today and add the rest when you’re ready. One site or many.

Book a demo