Generate professional Request for Proposal documents that attract qualified vendors and enable objective evaluation for procurement decisions
You are a procurement specialist with extensive experience in strategic sourcing and vendor management across Fortune 500 companies. You have issued hundreds of RFPs that successfully identified the right partners for complex projects ranging from technology implementations to professional services engagements. You understand that a well-crafted RFP does not just collect bids but attracts quality vendors, enables fair comparison, and protects both parties by setting clear expectations from the start. I need to create a Request for Proposal for [PROJECT_TYPE:select:IT/Software Implementation,Consulting Services,Marketing/Creative Services,Professional Services,Construction/Facilities,Staffing/HR Services,Financial Services,Legal Services,Research Services,Training/Development,Outsourcing Services,Custom Project]. My organization is [ORGANIZATION_NAME] in the [INDUSTRY:select:Technology,Healthcare,Financial Services,Manufacturing,Retail,Government,Education,Nonprofit,Energy,Real Estate,Professional Services,Media/Entertainment] sector. We have approximately [COMPANY_SIZE:select:Under 50,50-200,200-500,500-2000,2000-10000,10000+] employees. The internal stakeholder or project sponsor is [SPONSOR_NAME] with the title [SPONSOR_TITLE]. Here is the background on why we need this service and what triggered this procurement initiative: [PROJECT_BACKGROUND] The specific business objectives we want to achieve through this engagement are: [BUSINESS_OBJECTIVES] The scope of work and deliverables we expect from the selected vendor include: [SCOPE_AND_DELIVERABLES] Any specific technical requirements, certifications, or qualifications vendors must have: [MANDATORY_REQUIREMENTS?] Our target timeline is [PROJECT_TIMELINE:select:1-3 months,3-6 months,6-12 months,12-24 months,Ongoing engagement] with an anticipated project start date of [START_DATE]. The estimated budget range is [BUDGET_RANGE:select:Under $25K,$25K-$50K,$50K-$100K,$100K-$250K,$250K-$500K,$500K-$1M,$1M+,Not disclosed]. The deadline for vendor responses is [RESPONSE_DEADLINE] and our selection criteria priorities are [EVALUATION_PRIORITIES:select:Price-focused,Quality-focused,Experience-focused,Innovation-focused,Balanced approach]. Constraints or parameters vendors should know about include: [CONSTRAINTS?] Generate a complete Request for Proposal document with the following sections: Begin with a cover page including the RFP title, issuing organization, release date, response deadline, and primary contact information for inquiries. Section 1 covers the introduction and organizational overview. Provide context about who we are and why we are issuing this RFP. State the purpose clearly and explain what type of partner we seek. Include any relevant background that helps vendors understand our culture and operating environment without revealing confidential information. Section 2 presents the project background and objectives. Explain the business context driving this initiative. Articulate the problem we are solving or opportunity we are pursuing. Define success in concrete terms that vendors can propose against. Make clear what outcomes matter most to us. Section 3 defines the scope of work. Detail the required services, deliverables, and activities. Break down the engagement into logical phases or workstreams. Specify mandatory requirements versus nice-to-have capabilities. Include technical specifications, compliance requirements, or standards that apply. Section 4 outlines vendor qualifications. List required credentials, experience levels, and certifications. Specify the minimum years of relevant experience needed. Request information about company size, financial stability, and references. Define any mandatory requirements that disqualify vendors if not met. Section 5 contains proposal requirements. Detail exactly what vendors must include in their responses such as executive summary, approach and methodology, team composition and qualifications, project timeline and milestones, pricing structure, references and case studies, and any required attachments or certifications. Section 6 explains the evaluation criteria. State how proposals will be scored and weighted. Common criteria include understanding of requirements, proposed approach, team qualifications, relevant experience, price, and innovation. Be specific about weights if using a scoring matrix. Section 7 covers timeline and process. Provide the complete procurement schedule including RFP release date, deadline for questions, response to questions, proposal submission deadline, evaluation period, shortlist notification, vendor presentations if applicable, final selection, and contract negotiation. Section 8 presents terms and conditions. Include confidentiality expectations, proposal validity period, cost of preparation disclaimer, right to reject or cancel, insurance requirements, and any mandatory contract terms vendors should review. Section 9 provides submission instructions. Specify format requirements such as page limits or file types, delivery method and address, number of copies if physical, required signatures or authorizations, and deadline with time zone. Appendix sections should include the response template or format guide, any forms vendors must complete, technical specifications or standards documents if applicable, and sample contract terms for review. Write the RFP in a professional tone that is clear and direct without being bureaucratic. Use precise language that leaves no room for misinterpretation. The document should help quality vendors respond effectively while discouraging unqualified bidders from wasting everyone's time. Make every requirement serve a purpose and avoid boilerplate language that does not add value to the evaluation process. Format the RFP with clear section numbering and headings. Use tables for timelines and evaluation criteria. Include bullet points for lists of requirements. The length should be appropriate for the complexity of the project, typically 8-20 pages excluding appendices.
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA request for proposal is the document that determines whether you get competitive bids or vague pitches that waste everyone's time. Poorly structured RFPs cause 35 percent of evaluations to lack agreement among decision-makers, leading to delays, budget overruns, and vendor mismatches.
This prompt generates a complete RFP from sixteen inputs that cover your organization, project requirements, and evaluation framework. You start with [ORGANIZATION_NAME], [INDUSTRY], and [COMPANY_SIZE] to give vendors the context they need. Then [PROJECT_BACKGROUND] and [BUSINESS_OBJECTIVES] explain why this project matters, while [SCOPE_AND_DELIVERABLES] and [MANDATORY_REQUIREMENTS] define exactly what you need. Financial framing comes from [BUDGET_RANGE] and [PROJECT_TIMELINE], and the selection process is shaped by [EVALUATION_PRIORITIES] and [RESPONSE_DEADLINE].
The output follows standard procurement structure: introduction, scope of work, requirements, budget expectations, timeline, evaluation criteria, and submission instructions. Every section is written to attract qualified vendors and make proposal comparison straightforward. Build your RFP in Dock Editor and use it alongside a scope of work to lock down deliverables before soliciting bids. For structuring the project after vendor selection, see the project charter and statement of work.
Fill in [ORGANIZATION_NAME], [INDUSTRY], [COMPANY_SIZE], [SPONSOR_NAME], and [SPONSOR_TITLE]. These fields give vendors the background they need to assess fit and tailor their proposals to your organizational reality.
Enter [PROJECT_TYPE], [PROJECT_BACKGROUND], and [BUSINESS_OBJECTIVES]. Explain why this project exists, what problem it solves, and what success looks like. Clear objectives attract vendors who genuinely match your needs.
Provide [SCOPE_AND_DELIVERABLES] and [MANDATORY_REQUIREMENTS] with as much detail as possible. List concrete deliverables, technical requirements, compliance needs, and anything that is explicitly out of scope.
Enter [PROJECT_TIMELINE], [START_DATE], [BUDGET_RANGE], and [RESPONSE_DEADLINE]. Realistic timelines and transparent budget ranges produce better proposals and prevent wasted effort from both sides.
Complete [EVALUATION_PRIORITIES] and [CONSTRAINTS] to shape the scoring framework. The prompt generates a weighted evaluation section that vendors see upfront, making the selection process transparent and your comparison process efficient.
A CTO issues an RFP for a cloud migration project, specifying technical requirements, security compliance standards, integration needs, and a weighted evaluation that prioritizes data security at 30 percent and scalability at 25 percent.
A marketing director solicits proposals for a brand refresh by defining creative deliverables, campaign timelines, and evaluation criteria that weight portfolio quality and cultural fit above cost alone.
A facilities manager creates an RFP for office renovation, detailing square footage, material specifications, permit requirements, and a timeline aligned with lease terms so contractors can provide accurate bids.
A VP of operations requests proposals for a process improvement initiative, providing background on current pain points, mandatory methodology requirements, and evaluation priorities that emphasize relevant industry experience.
A complete RFP includes an introduction with company background, project goals using the SMART framework, a detailed scope of work, budget expectations, timeline with milestones, evaluation criteria with weightings, submission format requirements, and terms and conditions. The scope section is the most critical because it defines what vendors will actually deliver and price against.
An RFI gathers general information to narrow your vendor shortlist. An RFQ requests pricing for a clearly defined product or service where cost is the main differentiator. An RFP solicits detailed proposals when the solution itself is complex or uncertain and you need vendors to propose their approach. Most consulting projects need an RFP because the solution requires custom thinking, not just a price quote.
The biggest mistakes are vague scope definitions that let vendors make incorrect assumptions, missing budget information that produces wildly mismatched proposals, unrealistic response deadlines that yield rushed bids, and unclear evaluation criteria that prevent vendors from targeting what matters most. Using generic boilerplate instead of tailoring each section to your specific project also reduces the quality of responses you receive.
The [EVALUATION_PRIORITIES] input tells the prompt which scoring factors matter most for your selection. Common priorities include technical expertise, cost, security compliance, scalability, and cultural fit. The prompt uses these to generate a weighted scoring section that vendors can see upfront, which leads to better-targeted proposals and a more transparent decision process.
Include specific tasks, responsibilities, deliverables, project phases, and what is excluded from scope. The more precise this input, the more useful the generated RFP becomes. Vague scope is the leading cause of change orders and budget overruns after vendor selection. List concrete outputs like reports, software modules, or training sessions rather than abstract goals.
Yes. The [BUDGET_RANGE] input prevents you from receiving proposals that are wildly outside your financial scope. Transparency about budget signals seriousness to vendors and helps them propose realistic solutions. You do not need to share an exact number, but providing a range saves time for both sides and produces proposals you can actually compare.
The RFP draws its requirements from your business requirements document and feeds into the consulting contract once you select a vendor. After contract signing, the winning proposal's deliverables map directly to your project management plan. Keeping these documents connected prevents scope gaps between what you asked for and what gets delivered.
Discover more prompts that could help with your workflow.
Generate a professional service level agreement with performance metrics, uptime targets, response times, penalties, and escalation procedures
Generate a comprehensive project management plan with scope, timeline, resources, risks, and deliverables for any project type.
Generate a structured business case that analyzes costs, benefits, risks, and alternatives to win executive approval for your project or investment
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.