The short version
- RFP, tender, pitch, and proposal are often used interchangeably, but they describe different processes with different expectations attached.
- An RFP (request for proposal) is a formal document from a buyer asking suppliers to respond to specific requirements; a tender is broadly the same thing, used more commonly in construction, public sector, and UK procurement.
- A proposal is what you submit in response, but the word is also used loosely for unsolicited or semi-formal pitches that don’t follow a structured brief.
- Getting the terminology wrong rarely disqualifies you, but misunderstanding what type of document you’re responding to absolutely can.
- Whatever the buyer calls it, the same principle applies: read the brief carefully, answer every question they asked, and check your response before you submit.
If you’ve spent any time in sales, consulting, or business development, you’ve almost certainly used these words interchangeably. Someone sends you a document, you write a response, you call it a proposal, a bid, a tender, or a pitch depending on which industry you grew up in. Nobody corrects you. Everyone moves on.
The terminology is genuinely inconsistent. Different sectors use different words for broadly similar processes, and buyers themselves aren’t always precise. A procurement team might issue what they call an “RFP” that reads structurally like a tender. An agency might receive a “brief” that is functionally an RFP with a friendlier name on it.
But the differences do matter. Not because the labels are sacred, but because each format carries different expectations about how formal your response should be, how tightly you need to follow the structure, and how your submission will be evaluated. Getting that wrong doesn’t usually disqualify you. Misreading what the buyer actually wants, though, very much can.
This article untangles the terminology clearly, once and for all.
What is an RFP?
An RFP, or request for proposal, is a formal document issued by a buyer who knows what problem they want to solve but wants suppliers to propose how they’d solve it. The buyer sets out their requirements, evaluation criteria, and submission instructions. You respond to each one. Your response is assessed, usually scored, and compared against other submissions.
RFPs are common in technology, professional services, financial services, and increasingly in marketing. They tend to be structured and specific. The evaluation criteria are usually published, which means you know exactly how your response will be scored before you write a word of it.
That last point is worth pausing on. When a buyer tells you how they’re going to score your response, the correct thing to do is write directly to those criteria. Not around them, not near them. To them.
What is a tender?
A tender is, in most practical respects, an RFP with a different name. The distinction is partly cultural and partly sectoral. In construction, public sector procurement, infrastructure, and much of UK and European commercial purchasing, “tender” is the standard term. The process is the same: a buyer issues a document, suppliers respond, submissions are evaluated.
Where tenders do sometimes differ is in formality. Public sector tenders in particular tend to follow strict procedural rules, with defined submission windows, mandatory compliance requirements, and occasionally a two-stage process: a pre-qualification questionnaire (PQQ) first, then an invitation to tender (ITT) for shortlisted suppliers.
If you’re responding to a tender for the first time, the volume of compliance requirements can feel intimidating. It isn’t a sign that the buyer is difficult. It’s usually a sign that they’re subject to procurement regulations and have to document everything.
What is a proposal?
This is where the terminology gets genuinely slippery. Technically, a proposal is what you submit in response to any formal request, whether the buyer calls it an RFP, a tender, or something else entirely. But the word is also used for documents that don’t follow a formal brief at all.
A consultant might send a prospective client an unsolicited proposal after a meeting. An agency might be asked for a proposal without a formal brief in sight. In both cases, the writer has more freedom about what to include and how to structure it, but also less guidance about what the buyer actually wants to see.
The risk with informal proposals is assuming you know what matters to the buyer. You might. You might not. The absence of a formal brief doesn’t mean the buyer has no preferences. It usually means they haven’t written them down yet.
What about pitches, briefs, and everything else?
Creative and agency sectors tend to use different language again. A “pitch” usually involves a presentation, sometimes with a written document attached. A “brief” is what the client issues, and your response to it might be called a proposal, a pitch document, a credentials deck, or simply “the deck.”
None of this is wrong. It reflects how those sectors actually work. But it can create problems when an agency receives something more formal and treats it like a creative brief. The clue is usually in the document itself: if it has numbered requirements, weighted evaluation criteria, and a specified format for responses, it’s functioning as an RFP regardless of what the covering email calls it.
Why the format matters more than the name
The label matters less than understanding what type of evaluation process you’re entering. There are broadly two modes:
Structured evaluation: The buyer has defined criteria, published weightings, and a scoring process. Your job is to address every criterion with evidence. Creativity sits within that structure, not outside it. Missing a criterion, however strong the rest of your response, costs you points you cannot recover.
Relationship and judgement: The buyer is making a more subjective call. Fit, style, chemistry, and confidence all carry weight alongside the content of what you’ve written. Structure still matters, but there’s more room to show personality and differentiate.
Most formal RFPs and tenders fall into the first category. Most pitches and informal proposals lean towards the second. Some sit in both, which is where proposal writing gets genuinely interesting.
Pro tip: Read the evaluation criteria before you read anything else in the document. If there are published scoring weightings, those weightings tell you exactly where to invest your time.
When something isn’t clear, ask
Every formal procurement process includes a questions and clarifications window, and most buyers expect suppliers to use it. If a requirement is ambiguous, if you’re not sure what format an appendix should take, or if a section of the brief appears to contradict another, ask.
Asking questions is not a sign of weakness or confusion. Done well, it signals that you’ve read the document carefully and are taking the opportunity seriously. A precise, well-framed question shows more commercial intelligence than guessing and hoping.
Page limits are a good example. If the brief specifies a ten-page response, stick to ten pages. But if it isn’t explicit about what counts towards that limit, ask. Cover pages, appendices, CVs, and case study annexes are frequently excluded from the page count, and buyers rarely volunteer that information upfront. The difference between ten pages of core content and ten pages that include your cover and three appendices is significant. One question before the window closes can save you from either padding your response or cutting content you didn’t need to cut.
Keep clarification questions specific and professional. Don’t use them to probe the buyer’s preferences or try to get an unfair advantage. Most procurement processes publish all questions and answers to all bidders anyway, so anything you ask will be visible to your competitors.
The window closes. Ask before it does.
