Libraries · logistics & pm · procurement

Procurement & Vendors

RFPs, RFQs, statements of work, vendor evaluations, and award letters: the procurement documents that get the right vendor under contract without a dispute later.

PROMPTS 15 // OPEN SAMPLES 2 // FREE WITH ACCOUNT 13

Request for Proposal (RFP)

OPEN SAMPLE

Drafts a structured request for proposal that gives vendors the information they need to respond accurately. Use it when you are sourcing a service, solution, or complex supply requirement and need competitive proposals.

ORGANIZATION NAME ·WHAT IS BEING PROCURED ·NUMBER OF VENDORS ·APPLICABLE RULES OR POLICY ·REQUIREMENT DESCRIPTION ·BUDGET RANGE OR "not disclosed" ·TIMELINE ·EVALUATION CRITERIA ·SUBMISSION DEADLINE ·POC NAME AND CONTACT INFO
## Context
You are a procurement specialist helping me draft a Request for Proposal (RFP) for [ORGANIZATION NAME]. We are sourcing [WHAT IS BEING PROCURED]. This RFP will go to [NUMBER OF VENDORS] vendors. The procurement is governed by [APPLICABLE RULES OR POLICY, e.g., FAR, state procurement code, internal policy, or none specified]. Key background:

- Requirement description: [REQUIREMENT DESCRIPTION]
- Estimated budget range (if releasable): [BUDGET RANGE OR "not disclosed"]
- Period of performance or delivery timeline: [TIMELINE]
- Evaluation criteria and weights: [EVALUATION CRITERIA]
- Submission deadline: [SUBMISSION DEADLINE]
- Points of contact: [POC NAME AND CONTACT INFO]

## Task
Draft a complete RFP document with these sections:
1. Introduction and background
2. Scope of work and requirements
3. Proposal instructions (format, page limits, sections required)
4. Evaluation criteria and how scoring will work
5. Submission instructions and deadline
6. Terms, conditions, and any required certifications
7. Questions and clarification process

Use plain language throughout. Vendors of varying sizes will read this.

## Standards
- Do not invent requirements, dates, dollar figures, evaluation weights, or compliance rules the user did not provide.
- Write each requirement as a clear, testable statement. Avoid vague phrases like "world-class" or "best-in-class."
- Mark any section where the user left a variable blank with [NEEDS INPUT] so nothing is published incomplete.
- Keep the tone direct and professional. This is a legal procurement document: note that final legal and contractual review by appropriate authority is required before issuance.
- Do not invent vendor names, past contracts, or agency history.
- If a named input is missing or ambiguous, ask before drafting that section.
BEFORE YOU RUN IT
  • Clear written description of what you are buying: the requirement, deliverables, and any technical specifications
  • Evaluation criteria and their weights or priority order, confirmed from your acquisition plan or team decision
  • Submission deadline, period of performance, and any other dates from your procurement schedule
  • Applicable procurement rules or internal policy (FAR, state code, organizational policy) to include or reference
  • Budget range decision: whether to disclose it, and if so, the figure from your approved budget documents
  • Confidentiality: keep vendor-sensitive pricing targets and internal scoring deliberations out of the prompt
VERIFY BEFORE IT LEAVES YOUR HANDS
  • Confirm every date in the RFP against your procurement schedule before publishing: AI does not know your calendar
  • Check that evaluation weights add up to 100 percent using your own arithmetic, not the AI's output
  • Verify that no dollar figures, contract values, or past-award data appear in the draft unless you provided them
  • Read the scope section against your original requirement description to confirm nothing was dropped or invented
  • Check all compliance references (FAR clauses, state statutes, policy citations) against the actual documents before including them
  • Have your contracting officer, legal counsel, or designated authority review the final draft before issuance: this prompt is not legal or contractual advice
  • Confirm no [NEEDS INPUT] placeholders remain in the version you send to vendors
Sample output
Sample output. Generated by AI from sample inputs:

REQUEST FOR PROPOSAL
RFP No.: NW-2026-LOG-007
Northwind Distribution LLC

1. Introduction and Background
Northwind Distribution LLC (Northwind) is a regional third-party logistics provider headquartered in Columbus, Ohio. We are issuing this RFP to solicit proposals for a warehouse management system (WMS) to support our new Atlas fulfillment center opening in Q3 2026. This RFP is governed by Northwind's internal procurement policy.

2. Scope of Work and Requirements
The selected vendor must provide:
- A cloud-hosted WMS capable of managing up to 50,000 SKUs
- Real-time inventory visibility with barcode and RFID scanning support
- Integration with Northwind's existing ERP (Microsoft Dynamics 365)
- Role-based access for warehouse staff, supervisors, and finance
- Training for up to 40 users prior to go-live
- 99.5 percent uptime SLA with a documented incident response process

Delivery and go-live: no later than August 15, 2026.

3. Proposal Instructions
Submit proposals in PDF format, maximum 30 pages, structured as follows:
- Section 1: Technical approach and system architecture
- Section 2: Implementation plan and timeline
- Section 3: Training and change management plan
- Section 4: Pricing (include one-time and recurring costs separately)
- Section 5: References (minimum three, similar scope)

4. Evaluation Criteria
Proposals will be scored on the following criteria:
- Technical capability and fit: 40 percent
- Implementation plan and timeline: 25 percent
- Pricing and total cost of ownership: 20 percent
- References and past performance: 15 percent

Northwind reserves the right to conduct demonstrations before final award.

5. Submission Instructions
Submit proposals by email to [email protected] no later than July 11, 2026 at 5:00 PM Eastern. Proposals received after this time will not be evaluated.

6. Terms and Conditions
Northwind is not obligated to award a contract as a result of this RFP. Costs incurred by vendors in preparing proposals are not reimbursable. Northwind reserves the right to cancel this RFP at any time.

7. Questions and Clarifications
Submit written questions to [email protected] by June 27, 2026. Answers will be distributed to all vendors by July 3, 2026. No oral questions will be binding.

Point of contact: Maria Chen, Procurement Manager, (614) 555-0182.
CUSTOMIZATION

For government contracting, replace the terms section with a reference to the applicable FAR parts and required clauses. For high-dollar or regulated procurements, add a mandatory pre-proposal conference section. Adjust page limits and section structure to match your organization's standard RFP template. If evaluation is conducted by a board, add a section explaining the board composition and protest rights.

Request for Quote (RFQ)

Drafts a focused request for quote for commodity goods or straightforward services where price and delivery are the primary decision factors. Use it when you need competitive pricing from multiple vendors fast.

FREE WITH ACCOUNT

Vendor Evaluation Matrix

Builds a scored evaluation matrix from the criteria and vendor responses you provide and flags where scores are close or unsupported. Use it during source selection to organize the comparison and document the rationale.

FREE WITH ACCOUNT

Statement of Work (SOW)

Drafts a statement of work that defines deliverables, standards, and responsibilities clearly enough for a vendor to price and perform the work. Use it before issuing a solicitation or attaching an SOW to a contract.

FREE WITH ACCOUNT

Bid Comparison Summary

Organizes bids or quotes into a side-by-side comparison table, recomputes totals independently, and flags discrepancies, missing items, and outliers. Use it after quote collection to prepare the award recommendation.

FREE WITH ACCOUNT

Contract Summary

Pulls the key facts from a contract into a plain-language summary that a project manager or operations lead can act on. Use it to onboard new team members, prepare for a kickoff meeting, or create a quick reference document.

FREE WITH ACCOUNT

Purchase Order Request

Drafts a purchase order request with all required fields populated from the information you provide. Use it to prepare a complete PO request for approval before submitting to finance or procurement.

FREE WITH ACCOUNT

Negotiation Prep Brief

Builds a structured negotiation preparation brief from the vendor data, contract terms, and objectives you provide. Use it before a vendor negotiation to organize your position, walk-in asks, and fallback options.

FREE WITH ACCOUNT

Vendor Award and Decline Letters

OPEN SAMPLE

Drafts the award letter to a selected vendor and the decline letters to the vendors who were not selected, after a competitive sourcing process closes. Use it as soon as the award decision is final and documented.

YOUR ROLE ·ORGANIZATION NAME ·GOODS OR SERVICES DESCRIPTION ·SOLICITATION NUMBER OR TITLE ·SELECTED VENDOR NAME ·DECLINED VENDOR LIST ·AWARD VALUE ·AWARD PERIOD ·DEBRIEF POLICY ·AWARD CONTACT NAME AND EMAIL
## Context
You are assisting a [YOUR ROLE (e.g., procurement manager, contracting officer, operations lead)] at [ORGANIZATION NAME] who has completed a competitive sourcing process for [GOODS OR SERVICES DESCRIPTION]. The solicitation reference is [SOLICITATION NUMBER OR TITLE]. The award decision has been made and is formally documented. Selected vendor: [SELECTED VENDOR NAME]. Vendors not selected: [DECLINED VENDOR LIST (names only)]. Award value: [AWARD VALUE]. Award period: [AWARD PERIOD (e.g., 12 months, June 1 2026 through May 31 2027)]. Debriefs: [DEBRIEF POLICY (e.g., debriefs available on written request within 5 days)].

## Task
Produce two documents:
1. Award letter to [SELECTED VENDOR NAME]. State the award, the value, the period, the next step (e.g., contract execution, kickoff scheduling), and a contact name for questions: [AWARD CONTACT NAME AND EMAIL].
2. A decline letter template that fits all unsuccessful vendors. State that a selection was made, that the vendor's proposal was considered, and whether debriefs are available. Do not rank, score, or compare vendors. Leave a placeholder for the vendor name.

## Standards
- Award letter: under 200 words. Professional and direct. State the award first, then the details.
- Decline letter: under 150 words. Respectful. No criticism of the proposal. No implied promises about future opportunities.
- Do not invent the award value, award period, solicitation number, or debrief policy. Use only what I provided above.
- Both letters must name the solicitation consistently using the exact title or number I gave you.
- Do not include contract terms, payment terms, or scope language. Those belong in the contract, not the award letter.
- If any required field above is missing or unclear, ask me before drafting.
BEFORE YOU RUN IT
  • Confirm the award decision is formally documented and approved before drafting. Letters sent before final sign-off create legal exposure.
  • Award value, period, and solicitation reference copied directly from the award document, not from memory
  • Debrief policy pulled from the solicitation terms or your organization's procurement policy
  • Contact name and email verified as current and correct
  • Confidentiality: keep evaluation scores, ranking details, and individual evaluator comments out of the prompt and out of the letters
VERIFY BEFORE IT LEAVES YOUR HANDS
  • Award value and period in the letter match the award document exactly. Recheck digit by digit.
  • Solicitation title or number is identical in both letters and matches the solicitation document
  • Decline letter contains no scores, ranks, or comparative statements about proposals
  • Debrief language matches the solicitation terms. The AI cannot know your policy.
  • Award letter names the correct next step for your process (contract execution, kickoff call, etc.)
  • No contract terms, payment terms, or scope language crept into either letter
  • Both letters cleared by legal or your contracting authority before release, if required by policy
Sample output
Sample output. Generated by AI from sample inputs:

AWARD LETTER

Subject: Award Notification: Solicitation 2026-LOG-041, Warehouse Management Software

Dear Ms. Reyes,

Northwind Distribution is pleased to inform Apex Systems that it has been selected for award under Solicitation 2026-LOG-041, Warehouse Management Software Implementation and Licensing.

Award value: $184,000
Award period: July 1, 2026 through June 30, 2027

Next step: Our contracts team will send the agreement for signature within five business days. Please direct any questions to Marcus Webb, Procurement Manager, at [email protected].

Thank you for your proposal and your interest in working with Northwind.

Sincerely,
Procurement Division
Northwind Distribution

---

DECLINE LETTER TEMPLATE

Subject: Notification of Selection: Solicitation 2026-LOG-041, Warehouse Management Software

Dear [VENDOR NAME],

Thank you for submitting a proposal under Solicitation 2026-LOG-041, Warehouse Management Software Implementation and Licensing. After careful review, Northwind Distribution has selected another vendor for this award.

We appreciate the time your team invested in responding. If you would like a debrief, please submit a written request to [email protected] within five business days of this notice.

We hope to see your firm in future solicitations.

Sincerely,
Procurement Division
Northwind Distribution
CUSTOMIZATION

If your organization prohibits debriefs or restricts their scope, adjust or remove that section and confirm with your legal team before sending. Government contracting contexts may require specific regulatory language (FAR, DFARS, state procurement codes) not included here. Have counsel review before release. For sole-source or non-competitive awards, the decline letter does not apply; use only the award letter and adjust the framing.

Procurement Requirements Doc

Builds a structured procurement requirements document that defines what is needed, the quantity, technical specifications, delivery requirements, and evaluation priorities before a solicitation goes out. Use it before drafting an RFP (request for proposal), RFQ (request for quotation), or purchase order.

FREE WITH ACCOUNT

Vendor Risk Summary

Produces a structured risk summary for a vendor relationship, covering financial stability, performance history, supply chain exposure, and compliance status. Use it before contract award, at annual reviews, or when a vendor shows early warning signs.

FREE WITH ACCOUNT

Contract Renewal Review

Produces a structured renewal review memo that weighs whether to renew, renegotiate, or replace a vendor contract before the option period or expiration date arrives. Use it 90 to 120 days before a contract end date.

FREE WITH ACCOUNT

All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.

Unlock free with an account →

Procurement Savings Tracker

Produces a structured savings summary that documents procurement savings by category and computes totals so they can be reported to leadership or included in a period-end procurement review. Recomputes all figures from the line-item data you provide.

FREE WITH ACCOUNT

Vendor Kickoff Agenda

Drafts a structured kickoff meeting agenda for the start of a new vendor engagement, covering roles, scope, communication protocols, key dates, and open items. Use it within the first week after contract execution.

FREE WITH ACCOUNT

RFP Evaluation Criteria

Builds the scoring criteria and weighting structure for evaluating vendor proposals, so evaluators apply consistent standards and award decisions can be documented and defended. Use it before an RFP (request for proposal) is issued.

FREE WITH ACCOUNT

All 135 prompts in this library are free with a VetsLearn account: every prompt, every checklist, synced to your account.

Unlock free with an account →
  • This library is not legal or financial advice. Contracts, statements of work, and budgets should be reviewed before you rely on them.
  • AI output is a first draft. Recompute every total. Every date, status, and metric must come from your own project records, not the AI.
  • A red, amber, or green status is your call, supported by the facts. Keep confidential customer, vendor, and personnel details out of the prompt.