RFP Response (Vendor Proposal) Template for Word
Evaluators score RFP responses against a checklist, often with a stack of competing proposals on the desk. A response wins by making every requirement easy to find and every answer easy to score. This template is a finished six-page example responding to a fictional city’s utility billing RFP: a short cover letter, an executive summary tied to the buyer’s goals, a compliance matrix with one standard answer per requirement, and pricing that adds up.
- Pages:
- 6
- Works with:
- Word for Microsoft 365, Word 2016 or later, Word for Mac (Word for the web can fill in fields)
- Updated:
What you can do with it
- Cover block and cover letter with fill-in fields and date pickers for submission and validity
- Executive summary built around the buyer’s goals, then solution and technical architecture sections
- Implementation phases table and a compliance matrix with a dropdown per requirement
- Five-year pricing table with a pricing note callout, assumptions and exceptions, references and signature

What's inside
The document has 6 pages. Each part below is a heading in the file, so you can jump to it from the Navigation Pane (View > Navigation Pane).
| Part | What it covers | What you write |
|---|---|---|
| Cover block and letter | Who is responding to what, and the headline offer | Issuer, RFP number, vendor, dates, contact; letter with the key numbers |
| 2–3. Summary and understanding | Why you, in the buyer’s terms | Buyer’s goals and how you meet each; restated requirements |
| 4–6. Solution, architecture, plan | What you will deliver and how | Functional answer, hosting, security, integrations, phases |
| 7–8. Compliance and pricing | The scored parts | Answer per requirement; itemized five-year cost |
| 9–11. Assumptions, references, signature | Conditions and proof | Exceptions, client references, authorized signer |
Before you start
- Read the RFP’s submission instructions twice: required section order, page limits, file format and the deadline time zone.
- Build your requirement list from the RFP before you write anything; it becomes the compliance matrix.
- Get pricing approved internally before drafting the cover letter, which quotes the total.
Step-by-step guide
Fill in the cover block
Type the issuer, RFP number (it also appears in the header), your legal name and contact, and pick the submission and validity dates.
Write the cover letter last
Keep it to four short paragraphs: thanks, what you propose, that you meet the mandatory requirements, the total price and term. Pick the letter date.
Mirror the buyer’s structure
If the RFP prescribes section numbers, rename the Heading 1 sections to match. The numbering and contents update by themselves.
Answer every requirement
Add a row to the compliance matrix per requirement (Tab in the last cell), pick the compliance level from the dropdown and point to the section that answers it.
Price it so it adds up
Replace the pricing rows, check that quantity × unit price equals each total, and state the pricing basis in the callout.
Final checks and sign
Update the table of contents, delete the gray note, check page limits, have an authorized officer sign and save as PDF unless the RFP asks for Word.
Field and control map
Every content control and field in the document, in the order they appear. Gray-boxed fields in Word are the content controls.
| Name | Type | Where | Value in the sample |
|---|---|---|---|
| RFP number | Text | Header | RFP 2026-117 |
| Vendor short name | Text | Header | Tidewater Systems |
| RFP title | Text | Body | Utility Billing System and Customer Self-Service Portal |
| Issuer | Text | Body | City of Fairhaven, Public Utilities |
| RFP number | Text | Body | RFP 2026-117 |
| Vendor legal name | Text | Body | Tidewater Systems, Inc. |
| Submission date | Date picker | Body | November 20, 2026 |
| Vendor contact | Text | Body | Leah Montgomery, Proposal Manager |
| Valid until | Date picker | Body | May 20, 2027 |
| Letter date | Date picker | Body | November 20, 2026 |
| Recipient | Text | Body | Ms. Carla Jimenez, Procurement Officer |
| Recipient organization | Text | Body | City of Fairhaven |
| Letter signer | Text | Body | Daniel Ortiz |
| Signer title | Text | Body | Vice President, Public Sector |
| 5.1.3 compliance | Dropdown | Body | Fully meets (Fully meets / Meets with configuration / Partially meets / Does not meet) |
| 5.1.9 compliance | Dropdown | Body | Meets with configuration (Fully meets / Meets with configuration / Partially meets / Does not meet) |
| 5.2.4 compliance | Dropdown | Body | Fully meets (Fully meets / Meets with configuration / Partially meets / Does not meet) |
| 5.3.2 compliance | Dropdown | Body | Fully meets (Fully meets / Meets with configuration / Partially meets / Does not meet) |
| 5.4.7 compliance | Dropdown | Body | Partially meets (Fully meets / Meets with configuration / Partially meets / Does not meet) |
| Reference 1 contact | Text | Body | Finance Director, available on request |
| Reference 2 contact | Text | Body | Utility Billing Manager, available on request |
| Reference 3 contact | Text | Body | IT Director, available on request |
| Officer name | Text | Body | Daniel Ortiz, Vice President, Public Sector |
| Signed date | Date picker | Body | Click or tap to enter a date. |
| Submission date footer | Date picker | Footer | November 20, 2026 |
{ TOC \o "1-2" \h \z \u } | Field | Body | contents list |
{ PAGE } | Field | Footer | 1 |
{ NUMPAGES } | Field | Footer | 6 |
{ SEQ Table \* ARABIC } | Field | Body | 1, 2, 3, 4, 5 |
Every field, control and style, explained
The code in each card is read straight from the .docx file (the XML Word stores, or the field code you see with Alt+F9), so it is exactly what the template contains.
<w:lvl w:ilvl="0">
<w:start w:val="1"/>
<w:numFmt w:val="decimal"/>
<w:pStyle w:val="Heading1"/>
<w:lvlText w:val="%1."/>
<w:lvlJc w:val="left"/>
<w:pPr>
<w:ind w:left="440" w:hanging="440"/>
</w:pPr>
</w:lvl>
<w:lvl w:ilvl="1">
<w:start w:val="1"/>
<w:numFmt w:val="decimal"/>
<w:pStyle w:val="Heading2"/>
<w:lvlText w:val="%1.%2"/>
<w:lvlJc w:val="left"/>
<w:pPr>
<w:ind w:left="660" w:hanging="660"/>
</w:pPr>
</w:lvl>The section numbers (1., 2., 6.1 …) are not typed. A multilevel list is linked to the Heading 1 and Heading 2 styles, so any paragraph you set to Heading 1 gets the next number and the table of contents picks it up.
Piece by piece
<w:pStyle w:val="Heading1"/>- Links list level 1 to the Heading 1 style (level 2 to Heading 2).
<w:lvlText w:val="%1."/>- Level 1 shows its counter and a period: 1., 2., 3.
<w:lvlText w:val="%1.%2"/>- Level 2 shows the parent number, a period and its own counter: 6.1, 6.2.
<w:ind w:left="440" w:hanging="440"/>- Hanging indent so wrapped heading text lines up after the number.
In the sample: 1. Cover letter, 2. Executive summary, 3. Understanding of requirements … (16 headings)
How it is used: To add a section, type the heading, then pick Heading 1 (Ctrl+Alt+1) or Heading 2 (Ctrl+Alt+2) on the Home tab. Numbers after it update by themselves.
How to change it: Home > Multilevel List > Define New Multilevel List to change the format (for example "Section 1"). Keep "Link level to style" set to Heading 1 and Heading 2.
Learn this: How to Plan and Structure Long Documents in Word: Outline View and Multilevel Numbering →{ TOC \o "1-2" \h \z \u }A TOC field builds the contents list from the Heading 1 and Heading 2 paragraphs. The file ships with the entries and page numbers already filled in, so it looks right the moment you open it.
Piece by piece
\o "1-2"- Include heading levels 1 to 2.
\h- Make each entry a link to its heading (Ctrl+click in Word).
\z- Hide page numbers in Web Layout view.
\u- Use the paragraph outline level, so the styles decide what is listed.
In the sample: 16 entries. First: 1. Cover letter … page 1
How it is used: After you add or rename sections, right-click the contents list and choose Update Field > Update entire table.
How to change it: References > Table of Contents > Custom Table of Contents: set "Show levels" to 3 to list Heading 3 as well.
Learn this: How to Add a Table of Contents, Captions, and Cross-References in Word →Page { PAGE } of { NUMPAGES }The footer counts pages with two fields: PAGE is the current page and NUMPAGES is the total. Both recalculate when the document is printed, saved as PDF or scrolled in Print Layout.
Piece by piece
PAGE- The number of the page the field sits on.
NUMPAGES- The total number of pages in the document.
In the sample: Page 1 of 6 on the first page
How it is used: Nothing to do: add or delete pages and the numbers follow.
How to change it: Double-click the footer to edit the text around the fields. Insert > Page Number > Format Page Numbers sets the starting number.
Learn this: How to Set Up Pages in Word: Margins, Breaks, Headers, Footers, and Page Numbers →{ SEQ Table \* ARABIC }Each table caption uses a SEQ field that counts tables in order. Insert a new captioned table in the middle and every later caption renumbers.
Piece by piece
SEQ Table- A counter named "Table". Every SEQ Table field adds 1.
\* ARABIC- Show the counter as 1, 2, 3.
In the sample: 5 caption(s): Table 1 to Table 5
How it is used: Captions are what a "see Table 2" cross-reference points to (References > Cross-reference).
How to change it: References > Insert Caption adds a new one. If numbers look stale, press Ctrl+A then F9 to update all fields.
Learn this: How to Add a Table of Contents, Captions, and Cross-References in Word →<w:sdtPr>
<w:alias w:val="RFP title"/>
<w:tag w:val="rfp_title"/>
<w:text/>
</w:sdtPr>Names, numbers and other details people change every time are plain text content controls. Click one and type: the text replaces the sample, keeps the formatting, and the field still shows its name when selected.
Piece by piece
<w:alias w:val="…"/>- The title shown on the control’s tab when you click it.
<w:tag w:val="…"/>- A machine-readable name, useful for mail merge or code.
<w:text/>- Plain text: one line, one format, so pasted text cannot break the layout.
<w:showingPlcHdr/>- Present when the field shows gray placeholder text instead of a value.
In the sample: RFP title = Utility Billing System and Customer Self-Service Portal
How it is used: 15 in this template: RFP number, Vendor short name, RFP title, Issuer, Vendor legal name, Vendor contact, Recipient, Recipient organization, Letter signer, Signer title, Reference 1 contact, Reference 2 contact, Reference 3 contact, Officer name. Use Developer > Design Mode to see every control at once, or the Selection Pane to jump between them.
How to change it: Developer > Properties changes the title, tag and placeholder. To show the Developer tab: File > Options > Customize Ribbon > Developer.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:sdtPr>
<w:alias w:val="Submission date"/>
<w:tag w:val="submission_date"/>
<w:date w:fullDate="2026-11-20T00:00:00Z">
<w:dateFormat w:val="MMMM d, yyyy"/>
<w:lid w:val="en-US"/>
<w:storeMappedDataAs w:val="dateTime"/>
<w:calendar w:val="gregorian"/>
</w:date>
</w:sdtPr>Dates are date picker content controls: click the arrow to pick from a calendar, or type a date in any format and Word shows it as "November 2, 2026".
Piece by piece
w:fullDate- The stored date, independent of how it is shown.
<w:dateFormat w:val="MMMM d, yyyy"/>- Display format: full month name, day, four-digit year.
<w:lid w:val="en-US"/>- Language used for month names.
<w:storeMappedDataAs w:val="dateTime"/>- Stores a real date value if the control is mapped to data.
In the sample: Submission date = November 20, 2026
How it is used: 5 in this template: Submission date, Valid until, Letter date, Signed date, Submission date footer. Pick the date from the calendar so every date in the document has the same format.
How to change it: Developer > Properties > Display the date like this, for example d MMMM yyyy or yyyy-MM-dd.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:sdtPr>
<w:alias w:val="5.1.3 compliance"/>
<w:tag w:val="5_1_3_compliance"/>
<w:dropDownList>
<w:listItem w:displayText="Fully meets" w:value="Fully meets"/>
<w:listItem w:displayText="Meets with configuration" w:value="Meets with configuration"/>
<w:listItem w:displayText="Partially meets" w:value="Partially meets"/>
<w:listItem w:displayText="Does not meet" w:value="Does not meet"/>
</w:dropDownList>
</w:sdtPr>Fields with a fixed set of answers are dropdown list content controls, so everyone uses the same words (useful when you search or count documents later).
Piece by piece
<w:dropDownList>- A list the reader must pick from (no free typing).
<w:listItem w:displayText="…" w:value="…"/>- One choice: the text shown and the value stored.
In the sample: 5.1.3 compliance = Fully meets (Fully meets / Meets with configuration / Partially meets / Does not meet)
How it is used: 5 in this template: 5.1.3 compliance, 5.1.9 compliance, 5.2.4 compliance, 5.3.2 compliance, 5.4.7 compliance. Click the field and choose from the list.
How to change it: Developer > Properties > Add, Modify or Remove choices. Use a Combo Box instead if people need to type their own answer.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:style w:type="paragraph" w:styleId="Callout">
<w:name w:val="Callout"/>
<w:basedOn w:val="Normal"/>
<w:pPr>
<w:pBdr>
<w:left w:val="single" w:color="F2A93B" w:sz="24" w:space="8"/>
</w:pBdr>
<w:shd w:fill="EEF2F8" w:color="auto" w:val="clear"/>
<w:spacing w:after="160" w:before="120"/>
<w:ind w:left="180" w:right="180"/>
</w:pPr>
<w:rPr>
<w:sz w:val="21"/>
</w:rPr>
</w:style>Notes and warnings use a paragraph style named Callout: tinted background, amber bar on the left, indented on both sides. Because it is a style, every callout matches and you can restyle them all at once.
Piece by piece
<w:shd w:fill="EEF2F8"/>- Light blue-gray background.
<w:left w:val="single" w:sz="24" w:color="F2A93B"/>- Amber bar, 3 pt wide, on the left edge.
<w:ind w:left="180" w:right="180"/>- Indented 1/8 inch on each side.
In the sample: Used for the notes, tips and warnings in the body.
How it is used: Put the cursor in a paragraph and pick Callout in the Styles gallery.
How to change it: Right-click Callout in the Styles gallery > Modify > Format > Border or Shading. All callouts change together.
Learn this: How to Use Styles and the Navigation Pane in Word →<w:trPr>
<w:cantSplit/>
<w:tblHeader/>
</w:trPr>Header rows are marked to repeat at the top of each page when a table breaks, and rows are set not to split across pages, so a long table stays readable when printed.
Piece by piece
<w:tblHeader/>- Repeat this row at the top of each page.
<w:cantSplit/>- Keep each row on one page.
In the sample: 5 of 7 tables repeat their header row
How it is used: Add rows with Tab in the last cell; the header keeps repeating.
How to change it: Click in the header row > Table Layout > Repeat Header Rows. Short tables are also set to keep with the next paragraph so they do not split.
Learn this: How to Build and Format Tables That Read Well in Word →<w:style w:type="paragraph" w:styleId="Guidance">
<w:name w:val="Guidance"/>
<w:basedOn w:val="Normal"/>
<w:pPr>
<w:spacing w:after="100"/>
</w:pPr>
<w:rPr>
<w:i/>
<w:iCs/>
<w:color w:val="6B7280"/>
<w:sz w:val="19"/>
</w:rPr>
</w:style>Instructions for whoever fills in the template use a Guidance style (gray italics). Delete them before you send the document; with a style, Find and Replace can remove them all at once.
Piece by piece
<w:i/>- Italic.
<w:color w:val="6B7280"/>- Gray text.
In the sample: One note under the title block.
How it is used: Home > Replace > More > Format > Style > Guidance finds every note.
How to change it: Right-click Guidance in the Styles gallery > Modify.
Learn this: How to Use Styles and the Navigation Pane in Word →Tips and limits
- Use the buyer’s words. If the RFP says "customer self-service portal", do not call it "resident hub".
- Never leave "Partially meets" without saying how and when the gap closes.
- Keep marketing claims out of the compliance matrix; evaluators want a direct answer and a reference.
- The compliance dropdown has four standard answers so a reviewer can scan the column; edit the choices under Developer > Properties if the RFP defines its own scale.
- Public bodies may publish responses. Mark confidential pages as the RFP instructs.
Learn the skills behind this template
Was this guide helpful? Spot a mistake? Send feedback · admin@arumsoft.com