Write the request around the deliverable you need, then tell every vendor how to answer it. This RFP template pairs a complete small-project request with a matching response outline. It keeps unanswered buying decisions visible before the request goes out.
Start with a buyer's request
This is an original fictional brief for Cedar Reading Club. It requests help preparing a two-page volunteer orientation handout. No actual organization, solicitation, vendor response, budget or award is represented.
Request for proposals: volunteer orientation handout rewrite
Status: Internal draft for review. Issue approval and submission instructions: TO CONFIRM.
Purpose: Prepare a plain-English orientation handout from the club's supplied source notes and terminology so new volunteers can find the information the club has chosen to include.
Requested work:
| ID | Requirement | What to explain in your response |
|---|---|---|
| R1 | Rewrite the supplied notes into a readable, two-page handout. | Your approach, proposed handout structure and exact deliverable format. Confirm the page-size and layout assumptions behind two pages. |
| R2 | Include one consolidated revision round. | What the round includes, what feedback you need together and how additional changes would be identified. |
| R3 | Use only the club's approved source notes and terminology for factual content. | How you will flag missing or conflicting information for the club to resolve. Do not propose invented volunteer procedures. |
Materials supplied by the club: Approved source notes and terminology. Readiness and delivery date: TO CONFIRM. The request does not include interviews or original research.
Outside this request: Translation, printing, web implementation and collection of volunteer information. Ask about a change in scope rather than silently adding one of these services.
Please organize your response under these headings:
- Approach and understanding of R1–R3.
- Deliverables and format assumptions.
- Draft and revision schedule, including dependencies on supplied notes and consolidated feedback.
- Fee, currency, pricing basis, assumptions and exclusions.
- One permitted comparable work sample, or a stated gap if you cannot supply one.
- Questions that need an answer before the work can be agreed.
Proposed comparison criteria: Completeness against the requested scope, approach, proposed schedule and fee. The buyer must confirm the criteria before issuing the request. This example assigns no weights, scores or winner.
Open buying decisions: Budget, actual contact, response deadline with time zone, submission channel, issue approval and award authority: TO CONFIRM.
This internal draft is ready to discuss, not ready to issue. A request for proposals does not itself accept an offer or place an order.
Turn the vague instruction into a scope check
“Make a better guide” leaves the output, inputs and revision work open. The revised request names a two-page handout, supplied notes and one consolidated revision round. A vendor can now say what they propose to deliver and which assumptions their schedule and fee depend on.
Choose R1, R2 or R3 in the example to follow that requirement into the response outline. For R1, a useful response would identify the actual deliverable and explain its format assumptions. “We create engaging content” does not answer the two-page handout request.
For R2, ask what counts as the included revision round. Feedback from three people arriving on separate days could mean something quite different from one consolidated set of comments. Set that expectation in the request so vendors can describe the same revision task.
For R3, keep factual decisions with the club. If a note does not explain who welcomes a new volunteer, the writer should flag the gap. Fluent wording cannot establish the club's actual procedure.
Give each response field a job
Use the aligned outline to check whether your instructions would produce comparable answers:
| Response field | What the buyer needs to learn |
|---|---|
| Approach | How the vendor would turn the supplied material into the requested handout. |
| Deliverables | What files and revision work the proposal actually includes. |
| Schedule | What happens after notes are available, what feedback is needed and which dates remain conditional. |
| Fee and assumptions | What the price covers, its currency and basis, and which changes would need a separate decision. |
| Work sample or gap | What relevant work the vendor can legitimately show. A missing sample stays missing. |
| Questions | Which uncertainties prevent a clear offer. |
George Washington University's procurement guidance connects evaluation criteria to the requester's objectives and explains why suppliers should know the priorities before responding. Decide which criteria fit your actual buying task; the university's internal procurement rules are not a universal process for a small organization.
Do not add a weighted score merely to make the request look formal. If you use weights in a real RFP, agree them, check the arithmetic and describe their use before release. This example's unweighted criteria are a discussion draft, not an approved evaluation method.
Resolve submission details before issuing it
The event that starts work is not the deadline for submitting a proposal. Keep the two separate. A draft schedule can depend on receiving approved notes, while the proposal deadline needs an actual date, time zone and permitted channel.
Confirm who may issue the request and who may make an award. Use your organization's procurement process and required documents. This template supplies the writing structure; it does not supply legal terms, purchasing authority or a compliant public tender.
Copy a prompt for the request and response outline
Create one complete HTML RFP review page for a buyer preparing
a small service-provider request.
Actual project purpose and audience: [PASTE]
Required deliverables, supplied inputs and exclusions: [PASTE]
Actual timing, dependencies and revision expectations: [PASTE]
Approved comparison criteria: [PASTE or TO CONFIRM]
Budget, contact, submission deadline/time zone/channel,
issue approval and award authority: [PASTE or TO CONFIRM]
Required official format and buying process: [PASTE]
Write the buyer's request first. Give requirements stable IDs.
Then provide a blank vendor-response outline that addresses
those requirements in the same order. Explain what answer each
field asks for. Do not invent vendor responses, prices, samples,
scores, accepted terms, authority or an award. Missing decisions
stay TO CONFIRM. Do not create legal or compliance clauses.
Include this separate original fictional teaching brief:
Cedar Reading Club requests a two-page volunteer orientation
handout rewritten from supplied approved notes and terminology.
R1: readable two-page handout; ask for structure, deliverable
format and page-size/layout assumptions.
R2: one consolidated revision round; ask for included work,
feedback needed together and handling additional changes.
R3: factual content only from approved notes/terminology;
ask how missing or conflicting facts will be raised with the club.
Inputs: approved notes and terminology; readiness/date TO CONFIRM.
Exclusions: original research, interviews, translation, printing,
web implementation and volunteer-data collection.
Response headings: approach; deliverables; dependency-based draft
and revision schedule; fee/currency/basis/assumptions/exclusions;
one permitted comparable sample or stated gap; open questions.
Proposed unweighted criteria: scope completeness, approach,
schedule and fee. Actual criteria approval TO CONFIRM.
Budget/contact/deadline/time zone/channel/issue approval/award
authority TO CONFIRM. No issued request or vendor response exists.
Show Buyer request and Vendor-response outline views. Selecting
R1/R2/R3 shows the exact request alongside its corresponding
response instruction. Compare vague "make a better guide" with
the complete scope. Keep unanswered submission details visible.
Provide separately blank preparation notes; preserve them across
views and ask before clearing. No submit/award/order controls.
Use at least 16px text, native labeled controls and visible focus.
At 360px stack the request/response records without page overflow.
Inline CSS/JavaScript only; no outside assets, network, storage,
saved-proposal or purchasing-workflow claims. Notes last only
in the current open page. Return the full HTML and open questions.
The maintained official request and authorized process prevail.
Check the generated outline by answering one requirement yourself. If you cannot tell what a vendor should put in that field, tighten the request before inviting responses.
Review the request beside the answers it asks for
An HTML reading copy lets a colleague inspect R1–R3 beside the response instructions. In your NOS workspace, clarify a static label such as “Revisions included” to “One consolidated revision round” when that wording matches the agreed request. Carry the correction into the maintained RFP and check any separately repeated instructions.
Have the authorized buyer resolve the remaining submission and approval details before issuing the actual request. Vendors should receive the same clear scope and response instructions you reviewed.