Proposals & briefs · Oct 31, 2026 · 14 min read

RFP response template that sorts every requirement.

An RFP's requirement list is written before anybody has priced it, so this response answers each line in one of four plain ways, puts a figure beside every assumption it makes, and says how a change after the award gets priced and approved.

An RFP response should answer every requirement in the order the client listed it, state the price and what that price covers, give the schedule, and name the people who'll do the work. An agency can get all of those parts right and still lose money on a won RFP, because the requirement list was a wish list and the response said yes to all of it. The fix is to give each requirement one of four answers (included as written, included as we read it, optional at a printed price, or not included) and to price every reading you make. Below is a full response written that way for Juniper Ridge Library District, a three-branch public library asking for a new website, at $47,850, with a Word and PDF copy you can take away.

How should an RFP response answer the requirement list?

Line by line, in the client's own numbering, with a label on every line that says exactly how you're answering it. An evaluation committee scores a response against its own list, so a response that reorganizes the requirements into the agency's favorite structure makes the committee hunt, and a committee that has to hunt tends to mark the line as missing.

The label matters more than the prose under it. "Included as written" means you'll do exactly what the line says, at the price you've quoted. "Included as we read it" means you'll do it, but the line could be read more than one way and you've written down the reading you priced, with a number attached. "Optional" means it's outside the base price and you've printed what it costs, so the committee can add it without asking. "Not included" means you won't do it, and you say why in one sentence, which reads far better to a committee than silence.

The second label does most of the work. Requirements like "migrate all existing content" or "integrate with the catalog" sound like one task and can mean a week or a quarter, depending on what the person who wrote them had in mind. Writing your reading beside them turns a guess into a stated project assumption that the client can correct before signing, instead of after launch.

Where do the usual RFP response guides stop?

They stop at the moment of submission, which is useful for winning the bid and silent on the months that follow it. The three we read are written for proposal teams, and each one is good at the part it covers.

Responsive's collection of RFP examples, updated on October 30, 2026, groups samples by industry and closes on eight practices for writing a response, including one it calls saying no with style, which means explaining a gap and offering a way forward. It carries no dollar figures, and its own FAQ asks whether a response should include pricing tables without answering. The AutoRFP.ai pack, published April 28, 2026, offers seven templates and describes three of them in detail: a 50-point check before submission, sorted into five groups, an executive summary and a cover letter. Loopio's guide to automating responses, published October 16, 2026, runs through seven steps from importing the RFP to saving each answer in a library for the next one.

None of the three we read prices an assumption, lists what the base price leaves out, or says what happens when the client changes the scope after the contract is signed. For an agency those are the three places a won RFP turns into an unpaid month, so the response below covers what the guides cover and then gives its weight to sections 4 to 7 and section 11.

The RFP response
RESPONSE TO REQUEST FOR PROPOSAL
RFP: Website Redesign, RFP No. JRLD-2027-01, issued Monday, January 11, 2027
Issued by: Juniper Ridge Library District, a public library district with three branches ("the district")
Submitted by: [your agency], [address], [email] ("the agency")
Contact for this response: [name], [title], [phone], [email]
Submitted: Friday, February 5, 2027, before the 4:00 pm Pacific deadline
Addenda acknowledged: Addendum 1, published Friday, January 29, 2027

1. COVER LETTER
1.1 Thank you for the chance to answer this RFP. We build websites for public organizations whose staff, not developers, keep the site up to date, and that is the site this response describes.
1.2 Our price for the work described in sections 4 to 6 is $47,850, fixed, with a launch on Friday, July 30, 2027, the date in requirement R-12.
1.3 Every requirement is answered in section 4 in your numbering. Where a requirement could be read more than one way, we've written the reading we priced in section 5, so you can correct it before you award.

2. SUMMARY
2.1 A new website for the district's three branches with seven page templates, 60 migrated pages, a catalog search box, an events listing fed from your current calendar, and two training sessions for staff.
2.2 Tested against WCAG 2.2 level AA on every template before launch.
2.3 Two options are priced in section 7 and can be added at award or at any time in the 12 months after it, at the printed price.

3. HOW TO READ SECTION 4
3.1 INCLUDED AS WRITTEN: we'll do exactly what the requirement says, inside the price in section 6.
3.2 INCLUDED AS WE READ IT: we'll do it inside the price, on the reading stated in the numbered assumption next to it.
3.3 OPTIONAL: outside the price in section 6, with its own price in section 7.
3.4 NOT INCLUDED: we won't do it under this response, for the reason given.

4. ANSWERS TO THE REQUIREMENTS
R-01 A site that adapts to phones, tablets and desktops. INCLUDED AS WRITTEN.
R-02 Conformance with WCAG 2.2 level AA. INCLUDED AS WRITTEN. Each of the seven templates is tested before launch and the results are handed over in writing.
R-03 A content system staff can edit without writing code. INCLUDED AS WRITTEN, on [content system].
R-04 Migrate all existing content. INCLUDED AS WE READ IT, see assumption A-1.
R-05 Integration with the library catalog. INCLUDED AS WE READ IT, see assumption A-2. A deeper integration is option O-2.
R-06 An events calendar for all three branches. INCLUDED AS WE READ IT, see assumption A-3.
R-07 A Spanish-language version of the site. OPTIONAL, see option O-1.
R-08 Training for staff who will edit the site. INCLUDED AS WRITTEN: two sessions of two hours each, recorded.
R-09 Hosting for five years. NOT INCLUDED. The district's current host can keep the site, and we'll move it there at launch inside the price.
R-10 Unlimited design revisions. INCLUDED AS WE READ IT, see assumption A-4.
R-11 New photography of all three branches. NOT INCLUDED. We don't take photographs, and we'll use the district's photo library or images it licenses.
R-12 Launch by Friday, July 30, 2027. INCLUDED AS WRITTEN, given assumption A-5.

5. ASSUMPTIONS
5.1 A-1 (R-04): we migrate the 60 current pages named in the content audit in section 9.2, rewriting nothing. The roughly 1,100 pages of past events are exported to a spreadsheet archive and are not migrated. Each further page migrated is $65.
5.2 A-2 (R-05): the site carries a catalog search box that sends the search to the district's existing catalog, which shows the results. Results shown inside the site are option O-2.
5.3 A-3 (R-06): events come from the district's current calendar system through its published feed, and the site lists them by branch. The calendar system itself isn't rebuilt or replaced.
5.4 A-4 (R-10): two rounds of revisions on the home page design and two on the other six templates as a set. A further round is $870.
5.5 A-5 (R-12): the district's approver named in section 11 answers each request for content or approval within five business days. A later answer moves the launch by the same number of business days.
5.6 If the district reads a requirement differently from the assumption beside it, tell us before award and we'll restate the price in writing.

6. PRICE
6.1 Discovery and content audit, 40 hours: $5,800.
6.2 Design of the home page and six templates, 92 hours: $13,340.
6.3 Build on [content system] and migration of 60 pages, 128 hours: $18,560.
6.4 Events listing from the calendar feed, 30 hours: $4,350.
6.5 Accessibility testing and fixes, 24 hours: $3,480.
6.6 Training, launch and the move to the district's host, 16 hours: $2,320.
6.7 Total, fixed, for the work in sections 4 and 5: $47,850, or 330 hours at $145 an hour.
6.8 Payment: $14,355 at award, $19,140 when the district approves the designs, $14,355 at launch, each due within 30 days of invoice.

7. OPTIONS
7.1 O-1 (R-07): Spanish versions of all seven templates with a language switch, 22 hours: $3,190. Translation of the text is done by the district's translator.
7.2 O-2 (R-05): catalog results shown inside the site instead of on the catalog's own pages, 40 hours: $5,800.
7.3 Either option can be added at award or within 12 months after it at the price printed here, and it adds to the schedule in section 9 the weeks we state in writing when it's ordered.

8. NOT INCLUDED
8.1 Hosting after launch (R-09), photography (R-11), writing or rewriting page text, translation, paid advertising, and changes to the catalog or calendar systems themselves.
8.2 Anything not answered as included in section 4 and not priced in section 7.

9. SCHEDULE
9.1 Work starts Monday, March 15, 2027, if the award is made by Monday, March 1, 2027.
9.2 Discovery and the content audit, with the list of 60 pages to migrate, by Friday, April 2, 2027.
9.3 Designs approved by Friday, April 30, 2027.
9.4 Build and migration finished by Friday, June 25, 2027.
9.5 Testing, training and launch on Friday, July 30, 2027.

10. HOW LONG THIS PRICE HOLDS
10.1 The price in sections 6 and 7 holds for 120 days from the submission deadline, to Saturday, June 5, 2027, for an award made in that time with work starting within 30 days of the award.
10.2 After that, we re-price the same hours at our rate on the date of the award and send the new total in writing before any contract is signed.

11. CHANGES AFTER AWARD
11.1 The district names one approver at award, who accepts or declines every change in writing.
11.2 Anything outside sections 4 to 7 is a change. We send each one as a written change order with its price at $145 an hour, the hours behind it and what it does to the launch date.
11.3 Work on a change starts only after the approver accepts it in writing, and accepted changes are invoiced with the next payment in 6.8.
11.4 Options in section 7 are ordered the same way, at their printed prices.

12. TEAM AND REFERENCES
12.1 [Name, role and years of experience for each person who will work on the project.]
12.2 [Three public-sector or nonprofit references, with a contact and the site each one can point you to.]

13. EXCEPTIONS TO THE RFP'S TERMS
13.1 [List each term in the district's sample contract you can't accept, with the wording you propose instead, or write "None." Have a lawyer read the district's contract before you sign it.]

Signed for the agency: ____________________ Name: ____________________ Date: __________

Why does every assumption need a price beside it?

Because an assumption without a price only tells the client what you think, while one with a price tells them what it costs to think otherwise, and that second version is the one they can act on before they sign. Assumption A-1 is the clearest case in the response above, and it's also where the Juniper Ridge RFP could have cost the most.

Requirement R-04 asked for "all existing content" to be migrated. During the question period the agency asked how many pages that meant, and Addendum 1, published on January 29, answered that the current site held "approximately 1,400 pages" without saying what they were. Most of them turned out to be past event listings going back to 2016, the kind of page nobody visits and nobody would think to mention. At the $65 a page printed in A-1, migrating 1,100 of those would have been $71,500 of work, more than the entire project, and an agency that answered R-04 "included" without a reading would have owed it.

Written as an assumption with a price, the same line becomes a choice for the district: 60 pages inside the fee, an archive file for the rest, and $65 for any page it wants carried across. The same thinking applies to anything you're refusing, which is why section 8 spells out what's left out instead of relying on the absence of a yes, and our post on project exclusions covers how to word that list so it reads as helpful rather than defensive.

A-4 does the same job for "unlimited design revisions", which is a common RFP line and one no agency can honestly price. Two rounds on the home page and two on the template set, with a third at $870, is a reading the committee can score, and it's a lot easier to defend in a meeting than a quiet hope that the client won't use the word "unlimited" literally.

How long should the price in an RFP response hold?

Long enough to reach the award date the RFP itself sets, plus a margin for the delays public buyers often run into, and then it should end in writing. The Juniper Ridge response holds its price for 120 days from the submission deadline, which runs to June 5, 2027, three months past the March 1 award date the RFP gave.

The second half of section 10 matters as much as the first. A board that awards in August instead of March is buying the same hours at a later date, so 10.2 re-prices those hours at the rate on the day of the award and sends the new total before the contract is signed, which is the same idea our web design quote template uses for a start date that slips. Without it, a response submitted in February quietly fixes your rate for a project that might start in the autumn.

Section 10 also ties the hold to a start within 30 days of the award, because a client can award on time and then wait months for its own contract paperwork. The response doesn't need to sound suspicious about that, it only needs to say what happens to the price if it does.

What happens when the client changes the scope after the award?

It becomes a change order against the scope as you answered it, priced from the hourly rate the response printed and accepted in writing by one named person before the work starts. That's what section 11 says, and it only works because sections 4 to 8 make it possible to tell, line by line, what the original price covered.

At Juniper Ridge it came up in week six. On Monday, April 19, after a board meeting, the district asked for an online booking form for the meeting rooms at all three branches, with branch staff approving each booking by email. Nothing in R-01 to R-12 mentions rooms, so it fell under 11.2 without any argument about whether it was "really" part of the website. On Wednesday, April 21, the agency sent a change order for 26 hours at $145, which is $3,770, with the launch moving one week to Friday, August 6, and the district's approver accepted it on Friday, April 23. The project total went from $47,850 to $51,620, and the $3,770 was added to the launch invoice, which became $18,125.

The award is also the point where the response becomes the basis for the contract and its statement of work, and our post on how a statement of work differs from a proposal explains why the requirement list shouldn't be pasted into the scope without your readings beside it. For the changes themselves, a change request form works on paper, and Docket handles the same steps for web agencies, with the client's approver accepting each change from a link and the date kept with the project.

Should you answer an RFP you can't fully meet?

Usually yes, as long as the gaps are a few lines you can label honestly and not the core of the project. Juniper Ridge's RFP asked for five years of hosting and new photography, neither of which a web agency without a hosting business or a photographer should promise, and the response says so plainly with a reason for each, in R-09 and R-11.

A committee comparing six responses will forgive a clear "not included, here's what we'd do instead" much faster than a yes it later finds out was hollow. What should make you pass on an RFP is a gap in the work that carries the budget, a deadline you can't hit even with every assumption in your favor, or contract terms in the district's sample agreement you couldn't sign, which is why section 13 exists and why it's worth reading those terms before you spend a week on the response.

If the RFP comes from a client who has already told you what they want, without a formal process, you don't need this structure at all. A web design proposal or a general project proposal template fits that case better, because there's no committee scoring your answers against a numbered list.

Sixty pages was the number the whole response turned on

The line that decided whether Juniper Ridge was a good project is A-1: "we migrate the 60 current pages named in the content audit, rewriting nothing", with each further page at $65. Every other section of the response only works because that reading was written down before the award, since a requirement that says "all existing content" will otherwise be read on the day of the dispute by the side that wrote it.

So when you copy the template, keep the four labels and change everything else. Put your own rate in sections 6 and 11, your own readings in section 5, and a figure beside each one. Then read the RFP's requirement list one more time and ask, for each line, what the most expensive sensible reading would be. If that reading isn't the one you priced, it belongs in section 5.

Frequently asked questions

What is an RFP response template?

An RFP response template is a reusable document an agency fills in to answer a client's request for proposal, with a cover letter, an answer to every numbered requirement, the assumptions behind the price, the price itself, priced options, what's left out, the schedule, how long the price holds and how changes after the award are handled. The version on this page is filled in for a three-branch library's website at $47,850.

Is this RFP response template free to use?

Yes, with no sign-up and no email address. The whole response is printed on this page, and you can copy it or download it as a Word file or a PDF from the buttons under it. Replace the library, the requirements and the prices with the ones in your RFP, and keep the four answer labels from section 3, since they're what makes the rest of the response work.

How do you answer an RFP requirement that's unclear?

Ask about it in writing during the question period the RFP sets, and if the answer is still vague, answer the requirement as included on a stated reading and put a price beside the reading. In the response above, a request to migrate all existing content becomes 60 named pages inside the fee and $65 for each further page.

How long should the price in an RFP response stay valid?

Long enough to cover the award date the RFP gives, with a margin for delays, and no longer. The template holds its price for 120 days from the submission deadline, for an award with work starting within 30 days of it, and after that re-prices the same hours at the rate on the day of the award.

Can an agency change its price after winning an RFP?

Not for the work it answered, but it can price anything outside that work. Each request beyond the answered requirements goes to the client as a written change order with its hours, its price and its effect on the launch date, and work starts only after the client's named approver accepts it in writing.

What's the difference between an RFP response and a proposal?

An RFP response is a proposal written to the client's own format and numbering, because a committee will score it against the requirement list. An ordinary proposal follows whatever structure the agency prefers, since one person usually reads it and decides.