RFP vs RFQ vs ITT: Tender Document Types Explained

Open a procurement portal on any given morning and you will see the same three letters again and again: RFP, RFQ, ITT. They look interchangeable. They are not. Each one tells you something specific about what the buyer already knows, what they are still deciding, and how they intend to choose a winner.

Suppliers who treat every tender document the same way waste effort. They write a full solution narrative for a contract awarded on price alone, or submit a bare price sheet for a contract where the buyer wanted to see a methodology. Reading the document type correctly, before touching the response, changes what you write and how much time you spend writing it.

RFQ: the buyer already knows what they want

A Request for Quotation is used when the specification is fixed. The buyer knows exactly what they are purchasing, whether that is a defined quantity of a standard product, a piece of equipment matching an exact model number, or a service with clearly bounded scope. What they do not know is who can supply it cheapest and fastest.

An RFQ signals commodity buying. The buyer has usually already decided the specification is not up for debate. Your job is not to persuade them of an approach, it is to price accurately, confirm you meet the spec exactly as written, and demonstrate you can deliver on time.

What this means for your response: keep it short. Long justifications of methodology are wasted words in an RFQ response. Buyers evaluating quotations are often working from a lowest-compliant-price model, or a weighted scorecard where price carries most of the weight. Spend your effort on accuracy: correct units, correct delivery timelines, correct compliance with the stated specification. A quotation with an error in it loses regardless of price.

RFP: the buyer wants you to solve a problem

A Request for Proposal is used when the buyer knows the outcome they need but has not fully defined the solution. This is common for services, consulting, complex IT systems, construction design-and-build contracts, and anything where the "how" is genuinely open to different approaches.

An RFP signals that methodology matters. The buyer is not just comparing prices, they are comparing your understanding of the problem, your proposed approach, your team, your track record, and your price, usually weighted across several criteria at once. Two suppliers can propose completely different solutions to the same RFP and both be compliant.

What this means for your response: this is where narrative and evidence carry weight. Explain how you understand the requirement. Show a delivery approach, not just an outcome promise. Reference comparable work and be specific about how your team will be resourced against this contract. A generic proposal that could be sent to any buyer for any project reads as generic, and evaluators notice.

ITT: the formal competitive tender

Invitation to Tender is the term most common in the UK, Ireland, and other Commonwealth-influenced procurement systems. It is less about the shape of the requirement and more about the formality of the process: a structured, rules-bound competitive procedure, often used above certain value thresholds, with a fixed submission deadline, an evaluation methodology published in advance, and strict rules about what can and cannot be clarified once the process opens.

An ITT can sit closer to an RFQ (tightly specified, price-led) or closer to an RFP (quality-weighted, solution-based) depending on what is being procured. What makes it an ITT rather than either of those labels is the process wrapper: the compliance requirements, the standard forms, the scoring matrix, and the formal rules around communication with the buyer during the tender period.

What this means for your response: compliance is not optional, and there is usually no room to negotiate it after submission. Read the instructions to tenderers document in full before writing a single line of the response. Missing a mandatory form, exceeding a page limit, or submitting past the deadline typically disqualifies a bid regardless of quality. Formality is the point of an ITT, and buyers who use this label tend to enforce it strictly.

Other labels you will encounter

Markets vary, and buyers do not always use these three terms consistently. You will also see:

Reading buyer intent before you write anything

The label on the document is the fastest signal you have, but read past it. A document titled RFQ that asks for a method statement alongside a price table is behaving like a hybrid. A document titled RFP that gives you a fixed specification and a single price line to fill in is really an RFQ wearing an RFP label. The evaluation criteria section is the real source of truth: if price is weighted at 80 percent or more, treat it like an RFQ no matter what the cover page calls it. If quality, methodology, and experience carry the bulk of the weighting, write like you are answering an RFP. This matters most when working across several countries at once, where the same underlying process can appear under three different names depending on the buyer's local convention.

How TRINTA fits in

TRINTA reads what your company sells and matches it against public tenders published by official sources across Africa, Europe, the Middle East, and Latin America, surfacing the ones worth your attention daily, regardless of what the buyer chose to call the document.

Frequently asked questions

Share this article

Reference

Related articles