Sales & contracts template

Free request for proposal template

A request for proposal (RFP) is the document a buyer sends to vendors to describe a project and invite them to bid on it, with a deadline and the criteria you will use to pick a winner. This template gives you the full structure: scope, schedule, what each proposal must contain, how pricing is submitted, and how proposals will be scored. Download it free in Word or PDF and fill in the brackets.

Free to use. Legally binding under the ESIGN Act, UETA, and eIDAS.Updated November 2026 by Document eSign
REQUEST FORPROPOSAL (RFP)Ready to sign online.SignatureSigned and datedSIGN
or download a copy
Overview

What this template is

A request for proposal is a buyer's formal invitation to vendors to propose how they would deliver a project and what they would charge for it. You use one when the work is big enough, or uncertain enough, that you want several businesses to compete and you want their approaches side by side, not just their prices. A good RFP does four things. It describes what you need. It states the terms you expect the contract to carry. It tells vendors exactly what to put in their proposals. And it says how you will judge them. Those four items are also the minimum the US federal government puts in its own RFPs under FAR 15.203(a), which is a fair test for a private one too. The RFP is the buyer's side of the exchange. Each vendor answers it with a proposal, and the winning proposal becomes the starting point for a separate signed contract, usually a service agreement or a purchase agreement. This template is written for a business or nonprofit running its own selection. Public agencies follow their own procurement rules and should start from those.

Who uses it

An operations or IT manager replacing a software system, managed service, or outsourced functionA nonprofit choosing an auditor, fundraising platform, or website agency and wanting a documented, fair process for its boardA facilities team bidding out janitorial, security, or maintenance contractsA marketing lead selecting an agency for a campaign or annual retainerA procurement team that needs a repeatable format so every RFP it sends looks the sameA small business buying its first large service contract and wanting quotes that can actually be compared
What's inside
  • An RFP number, issue date, and a single named point of contact with a no-other-contact rule
  • A background section and a scope of work with deliverables and minimum requirements
  • A project timeline and a full schedule of events, from questions to expected award
  • A written questions-and-amendments process so every vendor gets the same answers
  • A required proposal structure: cover letter, approach, experience, staff, references, pricing, exceptions
  • Pricing instructions with a choice of model and a rule that unlisted costs are included
  • Submission instructions with a deadline, file format, labelling, and a late-proposal rule
  • Weighted evaluation criteria and a choice between best value and lowest acceptable price
  • No-obligation, proposal-validity, cost, confidentiality, and conflict-of-interest terms
  • An attachments list and a governing-law clause
HOW IT WORKS

From template to signed in three steps.

01

Start from the template

Open it in the editor with the fields already mapped, or download the DOCX to edit offline.

02

Add signers and send

Drop signature and date fields, then route each party in order or in parallel.

03

Get a sealed copy

Everyone signs, and you get a tamper-evident PDF plus an audit certificate.

Start signing free

Free forever. No credit card. Your recipients sign with no account.

The details

Everything to know before you send it.

1

How to fill it in

Work through it in order, but write the scope and the evaluation criteria before anything else. Everything else in the RFP hangs off those two sections, and they are the ones vendors read most closely.

  • Sections 1 and 2: name one contact person and write a short, honest background. Vendors price risk, so tell them what is being replaced and why.
  • Section 3: list the deliverables you will actually accept or reject, and separate true minimum requirements from preferences. Anything marked minimum is a pass-or-fail gate.
  • Sections 4 and 5: set real dates. Give vendors at least two to three weeks after answers go out to write a serious proposal; a tight deadline gets you recycled boilerplate.
  • Section 7: keep the page limit. It forces vendors to say what matters and makes your evaluators' job possible.
  • Section 8: pick one pricing model and make everyone use it. If each vendor prices differently, you cannot compare them.
  • Section 10: fill in the weights so they add up to 100, and choose best value or lowest acceptable price before you see any proposals.
  • Sections 13 to 16: set a validity period that covers your evaluation, negotiation, and internal approvals with a margin (we use 90 days for most service work), name your draft contract if you have one, and fill in the governing-law state.
2

Writing evaluation criteria that hold up

Most RFP disputes come from scoring, not from the scope. A losing vendor asks why they lost, and the only good answer is that you scored every proposal against criteria you published in advance. So publish them, weight them, and stick to them. The template offers the two methods federal buyers use, which translate well to private buying. Best value is what FAR 15.101-1 calls a tradeoff: you can pick a vendor that is not the cheapest if its approach or experience is worth the difference, and the RFP has to say how much price matters relative to everything else. Lowest price technically acceptable, described in FAR 15.101-2, works the other way: every proposal that meets the requirements passes, and the cheapest passing one wins. Use lowest price for commodity work where any competent vendor will do. Use best value for anything where a bad vendor costs you more than the price gap, which covers most software, professional services, and creative work. Our advice for best value: keep price at no more than about a third of the total score. Weight it much higher and you are running a price auction with extra paperwork.

3

A worked example: scoring three proposals

Say you run the template's five criteria with these weights: approach 35, experience 25, key staff 15, price 20, references 5. Four firms bid on a website rebuild. One is out before scoring starts because it lacks the $1,000,000 liability cover you listed as a minimum in Section 3. Evaluators rate each of the other three from 0 to 10 on the non-price criteria, and each rating is multiplied by the weight divided by 10. Price is scored by formula: the lowest price divided by each firm's price, times 20. Here is how it comes out.

  • Firm A, $84,000: price 20, approach 6/10 for 21.0, experience 6/10 for 15.0, staff 7/10 for 10.5, references 8/10 for 4.0. Total 70.5.
  • Firm B, $96,000: price 84,000 / 96,000 x 20 = 17.5, approach 9/10 for 31.5, experience 8/10 for 20.0, staff 8/10 for 12.0, references 9/10 for 4.5. Total 85.5.
  • Firm C, $120,000: price 84,000 / 120,000 x 20 = 14.0, approach 8/10 for 28.0, experience 9/10 for 22.5, staff 9/10 for 13.5, references 9/10 for 4.5. Total 82.5.
  • Under best value, Firm B wins. It is $12,000 more than Firm A but scored 15 points higher, most of it on approach and experience.
  • Under lowest price technically acceptable, Firm A wins, as long as its proposal met every minimum. Same proposals, different winner, which is why you pick the method before the bids come in.
  • Keep the score sheets. If Firm C asks why it lost despite the strongest team, the answer is on paper: it lost 3.5 points to Firm B on price and made back only half a point on everything else, because Firm B's approach scored higher.
4

RFP vs RFQ vs RFI

These three get mixed up, and sending the wrong one wastes everyone's time. A request for information (RFI) comes first, when you are still working out what you need. It asks vendors to describe what they offer, commits you to nothing, and usually carries no pricing. A request for quotation (RFQ) sits at the other end: you already know exactly what you want, down to the quantity and specification, and you just want prices. A request for proposal is the middle case. You know the outcome you need but want vendors to propose how to get there, so you judge them on approach, experience, and price together. If you could write the full specification yourself and the only open question is cost, send an RFQ. If you cannot yet write a scope of work, send an RFI. Everything else is an RFP.

5

What happens after you send it

The period between issuing the RFP and the deadline is where fairness is won or lost. Route every question through the one contact named in Section 1, answer in writing, and send the same answers to every vendor, without saying who asked. If you change anything, issue a numbered amendment to everyone. This mirrors federal practice, where FAR 15.206 requires the contracting officer to amend the solicitation when requirements change and to send amendments to every party that received it. Hold the deadline as written. The template makes your own receipt record the clock and lets you choose whether late proposals are refused outright, which is the safer default if you expect a close contest. Federal RFPs that leave out a time default to 4:30 p.m. local time under FAR 15.208(a), which is a reminder to always state a time and a time zone in Section 5. After the deadline, screen out anything that fails a minimum requirement, score the rest, shortlist two or three finalists for presentations, then negotiate with your first choice.

6

Is an RFP legally binding?

This template is written so that it is not. Section 12 says plainly that no contract is formed by issuing the RFP, by a vendor submitting a proposal, or by a notice that a vendor was selected. A contract exists only when both sides sign a written agreement. Section 13 adds that you can cancel the process, reject every proposal, or split the work, and that vendors pay their own costs of responding. Keep those clauses. Without them, a disappointed vendor has more room to argue that your RFP was an offer they accepted. Two things in the RFP do carry weight, though. Vendors are held to the proposal validity period you set, so their prices stay open long enough for you to decide. And anything you promise about the process, such as scoring against the published criteria, is something you should actually do. Once you pick a winner, the vendor's proposal feeds into a separate contract: a service agreement for ongoing work, a statement of work for a defined project, or a purchase agreement for goods.

7

Public-sector RFPs are different

If you are a government agency, school district, or a public body spending public money, do not rely on a private template alone. Federal agencies follow Part 15 of the Federal Acquisition Regulation, and FAR 15.204-1 sets a uniform format in which instructions to offerors sit in Section L and evaluation factors in Section M. States, counties, and cities have their own procurement codes with their own thresholds, advertising rules, and protest procedures, and proposals you receive may become public records after award. This template can still help you organise content, but your procurement office's required forms and rules come first. On the vendor side, if you are responding to a public RFP, read Sections L and M (or their local equivalent) before anything else. They tell you exactly what will be scored.

8

Common mistakes to avoid

Nearly every RFP that goes badly fails in one of these ways.

  • A scope that describes the solution you already have in mind, so only one vendor can fit it. Describe the problem and the outcome.
  • No weights on the criteria, or weights decided after the proposals arrive. That invites a challenge and makes the decision hard to defend to your own management.
  • Letting sales reps call your team directly. One contact, in writing, every time.
  • Asking for so much that good vendors decline to bid. A 40-question requirements matrix for a five-figure project drives away the firms you most want.
  • Comparing prices built on different assumptions. Fix the pricing model and quantities in Section 8.
  • Forgetting a validity period, then losing your preferred vendor's price because the decision took four months.
9

Signing and sending it

Only the issuer signs an RFP. The signature shows that an authorized person approved the document and the process it describes, which matters when someone later asks who released it. You can sign it by hand or sign online and send it as a PDF, and an online signature on an RFP is valid under the ESIGN Act and UETA. Send the same file to every vendor on your list at the same time, and keep a record of who received it, because that list is who gets every answer and amendment.

Disclaimer

This template and the guidance on this page are provided for general information only and are not legal advice. Laws differ by country and state, so review the final document against your own situation and have a qualified lawyer check anything high-value or regulated before you sign.

FAQ

Questions, answered.

What is a request for proposal?

It is a document a buyer sends to vendors describing a project and inviting them to submit proposals by a deadline. It sets out the scope, the schedule, what each proposal must include, how to price it, and how the buyer will score the responses.

What should an RFP include?

At minimum: what you need, the terms you expect in the contract, what vendors must put in their proposals, and the criteria you will use to evaluate them, with their relative importance. Those are the four items FAR 15.203(a) requires in federal RFPs. A practical RFP also adds a contact person, a schedule of events, submission instructions, and pricing rules.

What is the difference between an RFP and an RFQ?

An RFQ asks for prices on something you have already specified exactly. An RFP asks vendors to propose how they would do the work as well as what it costs, and you judge them on approach and experience along with price. Use an RFQ when price is the only open question.

Who responds to an RFP, and with what?

Vendors respond with a proposal that follows the structure the RFP asks for: a cover letter, their approach, qualifications, key staff, references, and pricing. If you are the vendor writing that response, use a project proposal template, not this one.

How long should vendors get to respond to an RFP?

No single rule applies to private RFPs. For most service projects, three to four weeks from issue to deadline is workable, with written answers to questions going out at least two weeks before proposals are due. Complex technology or construction projects often need longer.

Does sending an RFP commit me to hiring someone?

Not under this template. It states that no contract forms until both sides sign a written agreement, and that you can cancel the RFP or reject every proposal. Keep those clauses in place.

Is the request for proposal template available in Word format?

Yes. Download the request for proposal as a Word (.docx) file and edit it in Microsoft Word, Google Docs, or Pages. You can also download a PDF or fill it in and sign online.

Can I download the request for proposal as a PDF?

Yes. A print-ready PDF is available alongside the Word version. Download either one free, or fill it in and sign online without downloading anything.

Live in under a minute

Ready to send your first envelope?

Create your free forever account, upload a document, and send it for signature in minutes. No credit card required.

30 free envelopes a month Legally binding · global Audit trail on every document