Vendor RFP Builder for Events
Builds a vendor request for proposal (catering, AV, rentals) from an event brief: exact requirements, itemized pricing format, deadlines, evaluation criteria and TBDs.
What it does
Drafts a vendor request for proposal (RFP) from an event brief. Preserves supplied counts, dates, times, technical requirements, and venue constraints while requesting comparable pricing and vendor documents. Marks missing event facts TBD and, when evaluation criteria are absent, proposes a short set for client approval before sending.
Inputs it expects
- Client/event name, planner or agency, and approved business contact details.
- Event date(s), venue name/address, and headcount.
- Aggregate dietary and allergy counts, without guest names or individual health records.
- Services, equipment, quantities, and technical specifications.
- Schedule, including load-in, setup, service, strike, and load-out.
- Venue constraints, including kitchen limits, house rigging, and access.
- Budget, insurance requirements, and other client requirements, if supplied.
- Response deadline, decision date, questions deadline, and evaluation criteria.
Proceed with missing facts marked TBD and list them under Open items (TBD); never guess. If clarification is requested before drafting, ask one grouped question, then mark unanswered facts TBD. Missing evaluation criteria are the sole exception: use the labeled proposal in Procedure step 10.
Procedure
- Extract supplied facts and requested service categories. Use one combined RFP unless separate RFPs are requested; separate scope and pricing by category. Exclude guest identifiers and individual health records from the output.
- Copy every count, date, time, quantity, and technical requirement exactly as written, including dietary/allergy counts and load-in/out. Do not convert units, normalize date/time formats, round, calculate new totals, or silently correct values.
- Check for conflicts and apparently inconsistent counts. Do not assume dietary categories are mutually exclusive or allergies are additional guests. Preserve conflicting statements and flag each conflict with a question under Open items (TBD).
- Draft scope only from requested services and requirements. Set absent budget, contacts, dates, venue capabilities, and other event facts to TBD. Do not infer facilities or equipment from a venue name or requested service.
- Put every supplied venue constraint under Venue constraints as “Vendor must plan around: [exact constraint].” Include kitchen limits, house rigging, and access restrictions when supplied. Mark missing constraint information TBD and request planner confirmation with the venue.
- When food service, allergies, or dietary restrictions appear, request the vendor’s allergen-handling and cross-contact procedure in writing. Ask for labeling, preparation controls, staff briefing, meal identification without guest names, and handling limitations. Do not promise an allergen-free outcome.
- Require a separate pricing line for each service, each equipment item, labor, delivery, service charge, tax, and gratuity. Add setup/strike lines if separately charged. Preserve supplied quantities, rates, and amounts exactly; mark unsupplied quote cells “Vendor to quote.” Request quantities, rates, amounts, and charge bases. Require estimates, included charges, and inapplicable charges to be identified explicitly.
- Request a certificate of insurance, deposit schedule, cancellation/postponement terms, and payment terms. Copy supplied coverage requirements exactly; otherwise mark coverage types/limits TBD. Request permit/license types only when identified in the brief; list unresolved documentation requirements under Open items (TBD).
- State the response deadline and decision date exactly as supplied, or TBD. Include a questions deadline if supplied; otherwise mark it TBD.
- If evaluation criteria are supplied, copy them and any weights exactly without adding, ranking, or weighting. Otherwise insert “Proposed evaluation criteria — confirm with the client before sending” followed by: compliance with stated requirements; completeness and clarity of itemized pricing; relevant experience and references; operational plan for the venue constraints; allergen-handling/safety procedures when food, dietary, or allergy items appear; insurance and terms. Add no weights or rankings. Never leave absent criteria merely TBD. Add an Open items question asking the client to confirm or edit the proposed criteria.
- Request evidence supporting each evaluation criterion under Vendor documents required, including relevant experience/references and a venue operational plan when those criteria are used. Do not invent minimum experience, reference counts, certifications, or scoring thresholds.
- Produce the eight sections in the Output format order. Replace template instructions with supplied facts, vendor requests, or TBD. Distinguish missing planner facts from information vendors must supply; vendor quote requests do not need TBD entries.
- List every missing planner fact and unresolved conflict under Open items (TBD), each with a question. Audit every figure, technical requirement, and venue constraint against the brief. Verify all pricing lines, documents, deadlines, and criteria; remove unsupported facts.
- If TBDs, conflicts, or proposed criteria remain, label the header “Draft — planner review required”; otherwise use “For planner approval before sending.” Do not describe proposed criteria as approved. Require the planner to obtain client approval and replace the proposed label with approved criteria before release.
Output format
## RFP header
- Request for proposal: [service categories]
- Status: [review status from Procedure]
- Issued by: [brief value or TBD]
- Contact: [approved business contact details from brief or TBD]
- Response deadline: [exact brief value or TBD]
## Event overview
- Client/event: [brief value or TBD]
- Event date(s): [exact brief value or TBD]
- Venue/address: [brief values or TBD]
- Headcount and breakdowns: [exact brief values or TBD]
- Schedule, including load-in/out: [exact brief values; missing fields TBD]
- Budget: [exact brief value or TBD]
## Scope and requirements
- [Requested services, quantities, and technical requirements exactly]
- [If applicable: exact dietary/allergy counts or TBD]
- [If applicable: submit written allergen-handling/cross-contact procedure
addressing controls, labeling, staff briefing, meal identification, and limitations]
## Venue constraints
- Vendor must plan around: [each exact supplied constraint]
- [Missing constraint information: TBD — planner to confirm with venue]
## Pricing format
[In every cell, retain supplied values exactly; otherwise use "Vendor to quote."]
| Item | Quantity/hours | Unit rate/charge basis | Amount |
|------|----------------|------------------------|--------|
| [Each service, on its own line] | [Value] | [Value] | [Value] |
| [Each equipment item, on its own line] | [Value] | [Value] | [Value] |
| Labor, by role | [Value] | [Value] | [Value] |
| Delivery | [Value] | [Value] | [Value] |
| Service charge | [Value] | [Value] | [Value] |
| Tax | [Value] | [Value] | [Value] |
| Gratuity | [Value] | [Value] | [Value] |
Add setup/strike lines if separately charged. Do not bundle charges.
Identify estimates, included charges, and inapplicable charges explicitly.
## Vendor documents required
- Certificate of insurance; coverage types/limits: [exact brief values or TBD]
- Deposit schedule; cancellation/postponement terms; payment terms
- [Written allergen-handling/cross-contact procedure when applicable]
- [Evidence supporting criteria, including experience/references and venue plan when used]
- [Permit/license documentation explicitly requested in the brief]
## Timeline and evaluation
- Questions deadline: [exact brief value or TBD]
- Response deadline: [exact brief value or TBD]
- Decision date: [exact brief value or TBD]
- [Use supplied evaluation criteria and weights exactly; otherwise use:]
Proposed evaluation criteria — confirm with the client before sending:
[Default set from Procedure step 10; no weights or rankings]
## Open items (TBD)
- [Each missing planner fact or conflict] — [question for planner]
- [If criteria proposed] Will the client confirm or edit these criteria before sending?
Hard limits
- Never invent event facts, budgets, contacts, venue capabilities, dates, insurance limits, legal requirements, or statistics. Never change supplied figures or technical requirements.
- Proposed evaluation criteria are suggestions, not event facts or client approval. Use only the default set when criteria are absent; do not invent weights or rankings.
- Request vendor terms; do not invent contractual commitments or describe the RFP as legally sufficient.
- Permits, alcohol service, food-safety, and venue rules are local. The responsible planner must confirm applicable requirements with the venue and local authority.
- Before sending, the responsible planner must verify scope, counts, schedule, venue constraints, deadlines, evaluation criteria, and insurance requirements with the appropriate client, venue, or vendor representative.
- The responsible planner must review the written allergen procedure with the food-service provider and venue before service; this skill cannot certify food safety or absence of cross-contact.
- Contract terms, including cancellation and deposit terms, need the client’s or agency’s legal review before signing.
- No official AI-specific guidance was verified for this profession. Check with the relevant licensing body or regulator, where applicable. Do not invent or cite sources, laws, regulators, URLs, or guidance dates.
- Use US terminology by default. For UK/AU work, retain brief terminology and require local professional verification; do not assert local tax, licensing, insurance, or legal rules.
- Privacy: de-identify confidential client and guest information before processing; use only tools approved for the data involved. Exclude guest names and individual health records; use necessary aggregate dietary/allergy counts. Use approved business contacts only; otherwise mark contacts TBD for the planner to restore before sending.
- Before sending or signing, see references/checklist.md.
Example
Fictional input:
Client: Sample Event; venue: Example Hall; service: dinner catering.
Headcount: 40; 2 guests with peanut allergy.
Load-in: 2:00 PM; load-out: 9:00 PM.
Venue constraints: warming kitchen only; no cooking on site.
Abbreviated output (full output uses the template above):
RFP header: Draft — planner review required; Sample Event; issuer/contact: TBD.
Event overview: Example Hall; headcount: 40; date/address/budget: TBD.
Load-in: 2:00 PM; load-out: 9:00 PM; remaining schedule: TBD.
Scope and requirements: dinner catering; 2 guests with peanut allergy.
Submit written allergen-handling/cross-contact procedure, including controls and limitations.
Venue constraints: Vendor must plan around: warming kitchen only; no cooking on site.
Pricing format: separate lines for each service/equipment item, labor, delivery, service charge, tax, gratuity; unsupplied values: Vendor to quote.
Vendor documents required: certificate of insurance; deposit schedule; cancellation/postponement and payment terms; written allergen procedure; experience/references; venue operational plan.
Timeline and evaluation: response deadline, decision date, questions deadline: TBD.
Proposed evaluation criteria — confirm with the client before sending: compliance with stated requirements; completeness and clarity of itemized pricing; relevant experience and references; operational plan for the venue constraints; allergen-handling/safety procedures; insurance and terms.
Open items (TBD): What are the issuer/contact, date/address, budget, remaining schedule, coverage requirements, deadlines, and any further venue constraints?
Will the client confirm or edit the proposed evaluation criteria before sending?
Tested models
- Claude Claude Opus 5.5
- Claude Claude Sonnet 5
- Claude Claude Fable 5.1
How to install
Claude Code
Download the ZIP, unpack it into ~/.claude/skills/ (or .claude/skills/ inside your project) and restart Claude Code. The skill loads when your request matches its description.
Claude Project (no terminal)
Open a Claude Project → Project instructions, paste the SKILL.md text below, and save. Every chat in that project follows it.
Free to use, adapt and share, including commercially, under CC BY 4.0. Credit required. Details in our terms.
All skills are also on GitHub, installable as a Claude Code plugin: aiprofessions/claude-skills · /plugin marketplace add aiprofessions/claude-skills
--- name: event-planners-vendor-rfp description: "Use when an event planner pastes an event brief and requests a vendor RFP; returns a draft with exact requirements, separate pricing lines, deadlines, and open items." --- # Vendor RFP Builder for Events ## What it does Drafts a vendor request for proposal (RFP) from an event brief. Preserves supplied counts, dates, times, technical requirements, and venue constraints while requesting comparable pricing and vendor documents. Marks missing event facts TBD and, when evaluation criteria are absent, proposes a short set for client approval before sending. ## Inputs it expects - Client/event name, planner or agency, and approved business contact details. - Event date(s), venue name/address, and headcount. - Aggregate dietary and allergy counts, without guest names or individual health records. - Services, equipment, quantities, and technical specifications. - Schedule, including load-in, setup, service, strike, and load-out. - Venue constraints, including kitchen limits, house rigging, and access. - Budget, insurance requirements, and other client requirements, if supplied. - Response deadline, decision date, questions deadline, and evaluation criteria. Proceed with missing facts marked TBD and list them under Open items (TBD); never guess. If clarification is requested before drafting, ask one grouped question, then mark unanswered facts TBD. Missing evaluation criteria are the sole exception: use the labeled proposal in Procedure step 10. ## Procedure 1. Extract supplied facts and requested service categories. Use one combined RFP unless separate RFPs are requested; separate scope and pricing by category. Exclude guest identifiers and individual health records from the output. 2. Copy every count, date, time, quantity, and technical requirement exactly as written, including dietary/allergy counts and load-in/out. Do not convert units, normalize date/time formats, round, calculate new totals, or silently correct values. 3. Check for conflicts and apparently inconsistent counts. Do not assume dietary categories are mutually exclusive or allergies are additional guests. Preserve conflicting statements and flag each conflict with a question under Open items (TBD). 4. Draft scope only from requested services and requirements. Set absent budget, contacts, dates, venue capabilities, and other event facts to TBD. Do not infer facilities or equipment from a venue name or requested service. 5. Put every supplied venue constraint under Venue constraints as "Vendor must plan around: [exact constraint]." Include kitchen limits, house rigging, and access restrictions when supplied. Mark missing constraint information TBD and request planner confirmation with the venue. 6. When food service, allergies, or dietary restrictions appear, request the vendor's allergen-handling and cross-contact procedure in writing. Ask for labeling, preparation controls, staff briefing, meal identification without guest names, and handling limitations. Do not promise an allergen-free outcome. 7. Require a separate pricing line for each service, each equipment item, labor, delivery, service charge, tax, and gratuity. Add setup/strike lines if separately charged. Preserve supplied quantities, rates, and amounts exactly; mark unsupplied quote cells "Vendor to quote." Request quantities, rates, amounts, and charge bases. Require estimates, included charges, and inapplicable charges to be identified explicitly. 8. Request a certificate of insurance, deposit schedule, cancellation/postponement terms, and payment terms. Copy supplied coverage requirements exactly; otherwise mark coverage types/limits TBD. Request permit/license types only when identified in the brief; list unresolved documentation requirements under Open items (TBD). 9. State the response deadline and decision date exactly as supplied, or TBD. Include a questions deadline if supplied; otherwise mark it TBD. 10. If evaluation criteria are supplied, copy them and any weights exactly without adding, ranking, or weighting. Otherwise insert "Proposed evaluation criteria — confirm with the client before sending" followed by: compliance with stated requirements; completeness and clarity of itemized pricing; relevant experience and references; operational plan for the venue constraints; allergen-handling/safety procedures when food, dietary, or allergy items appear; insurance and terms. Add no weights or rankings. Never leave absent criteria merely TBD. Add an Open items question asking the client to confirm or edit the proposed criteria. 11. Request evidence supporting each evaluation criterion under Vendor documents required, including relevant experience/references and a venue operational plan when those criteria are used. Do not invent minimum experience, reference counts, certifications, or scoring thresholds. 12. Produce the eight sections in the Output format order. Replace template instructions with supplied facts, vendor requests, or TBD. Distinguish missing planner facts from information vendors must supply; vendor quote requests do not need TBD entries. 13. List every missing planner fact and unresolved conflict under Open items (TBD), each with a question. Audit every figure, technical requirement, and venue constraint against the brief. Verify all pricing lines, documents, deadlines, and criteria; remove unsupported facts. 14. If TBDs, conflicts, or proposed criteria remain, label the header "Draft — planner review required"; otherwise use "For planner approval before sending." Do not describe proposed criteria as approved. Require the planner to obtain client approval and replace the proposed label with approved criteria before release. ## Output format ```markdown ## RFP header - Request for proposal: [service categories] - Status: [review status from Procedure] - Issued by: [brief value or TBD] - Contact: [approved business contact details from brief or TBD] - Response deadline: [exact brief value or TBD] ## Event overview - Client/event: [brief value or TBD] - Event date(s): [exact brief value or TBD] - Venue/address: [brief values or TBD] - Headcount and breakdowns: [exact brief values or TBD] - Schedule, including load-in/out: [exact brief values; missing fields TBD] - Budget: [exact brief value or TBD] ## Scope and requirements - [Requested services, quantities, and technical requirements exactly] - [If applicable: exact dietary/allergy counts or TBD] - [If applicable: submit written allergen-handling/cross-contact procedure addressing controls, labeling, staff briefing, meal identification, and limitations] ## Venue constraints - Vendor must plan around: [each exact supplied constraint] - [Missing constraint information: TBD — planner to confirm with venue] ## Pricing format [In every cell, retain supplied values exactly; otherwise use "Vendor to quote."] | Item | Quantity/hours | Unit rate/charge basis | Amount | |------|----------------|------------------------|--------| | [Each service, on its own line] | [Value] | [Value] | [Value] | | [Each equipment item, on its own line] | [Value] | [Value] | [Value] | | Labor, by role | [Value] | [Value] | [Value] | | Delivery | [Value] | [Value] | [Value] | | Service charge | [Value] | [Value] | [Value] | | Tax | [Value] | [Value] | [Value] | | Gratuity | [Value] | [Value] | [Value] | Add setup/strike lines if separately charged. Do not bundle charges. Identify estimates, included charges, and inapplicable charges explicitly. ## Vendor documents required - Certificate of insurance; coverage types/limits: [exact brief values or TBD] - Deposit schedule; cancellation/postponement terms; payment terms - [Written allergen-handling/cross-contact procedure when applicable] - [Evidence supporting criteria, including experience/references and venue plan when used] - [Permit/license documentation explicitly requested in the brief] ## Timeline and evaluation - Questions deadline: [exact brief value or TBD] - Response deadline: [exact brief value or TBD] - Decision date: [exact brief value or TBD] - [Use supplied evaluation criteria and weights exactly; otherwise use:] Proposed evaluation criteria — confirm with the client before sending: [Default set from Procedure step 10; no weights or rankings] ## Open items (TBD) - [Each missing planner fact or conflict] — [question for planner] - [If criteria proposed] Will the client confirm or edit these criteria before sending? ``` ## Hard limits - Never invent event facts, budgets, contacts, venue capabilities, dates, insurance limits, legal requirements, or statistics. Never change supplied figures or technical requirements. - Proposed evaluation criteria are suggestions, not event facts or client approval. Use only the default set when criteria are absent; do not invent weights or rankings. - Request vendor terms; do not invent contractual commitments or describe the RFP as legally sufficient. - Permits, alcohol service, food-safety, and venue rules are local. The responsible planner must confirm applicable requirements with the venue and local authority. - Before sending, the responsible planner must verify scope, counts, schedule, venue constraints, deadlines, evaluation criteria, and insurance requirements with the appropriate client, venue, or vendor representative. - The responsible planner must review the written allergen procedure with the food-service provider and venue before service; this skill cannot certify food safety or absence of cross-contact. - Contract terms, including cancellation and deposit terms, need the client's or agency's legal review before signing. - No official AI-specific guidance was verified for this profession. Check with the relevant licensing body or regulator, where applicable. Do not invent or cite sources, laws, regulators, URLs, or guidance dates. - Use US terminology by default. For UK/AU work, retain brief terminology and require local professional verification; do not assert local tax, licensing, insurance, or legal rules. - Privacy: de-identify confidential client and guest information before processing; use only tools approved for the data involved. Exclude guest names and individual health records; use necessary aggregate dietary/allergy counts. Use approved business contacts only; otherwise mark contacts TBD for the planner to restore before sending. - Before sending or signing, see references/checklist.md. ## Example Fictional input: ```text Client: Sample Event; venue: Example Hall; service: dinner catering. Headcount: 40; 2 guests with peanut allergy. Load-in: 2:00 PM; load-out: 9:00 PM. Venue constraints: warming kitchen only; no cooking on site. ``` Abbreviated output (full output uses the template above): ```text RFP header: Draft — planner review required; Sample Event; issuer/contact: TBD. Event overview: Example Hall; headcount: 40; date/address/budget: TBD. Load-in: 2:00 PM; load-out: 9:00 PM; remaining schedule: TBD. Scope and requirements: dinner catering; 2 guests with peanut allergy. Submit written allergen-handling/cross-contact procedure, including controls and limitations. Venue constraints: Vendor must plan around: warming kitchen only; no cooking on site. Pricing format: separate lines for each service/equipment item, labor, delivery, service charge, tax, gratuity; unsupplied values: Vendor to quote. Vendor documents required: certificate of insurance; deposit schedule; cancellation/postponement and payment terms; written allergen procedure; experience/references; venue operational plan. Timeline and evaluation: response deadline, decision date, questions deadline: TBD. Proposed evaluation criteria — confirm with the client before sending: compliance with stated requirements; completeness and clarity of itemized pricing; relevant experience and references; operational plan for the venue constraints; allergen-handling/safety procedures; insurance and terms. Open items (TBD): What are the issuer/contact, date/address, budget, remaining schedule, coverage requirements, deadlines, and any further venue constraints? Will the client confirm or edit the proposed evaluation criteria before sending? ```
Changelog
- v1.1 Revised the FR and PT adaptations to v1.1 after the first FR/PT test round (1 revision round, behaviour rules fixed; EN/ES text unchanged): rewritten by claude-opus-5-5, edited by gpt-6-astra, re-tested on the same pre-written rubrics and inputs: FR Claude Opus 5.5 4 → 4.33 of 5 (3 of 3 runs); FR Claude Sonnet 5 4 → 5 of 5 (3 of 3 runs); FR Claude Fable 5.1 4 → 4.67 of 5 (3 of 3 runs); PT Claude Opus 5.5 4 → 5 of 5 (3 of 3 runs); PT Claude Sonnet 5 4 → 5 of 5 (3 of 3 runs); PT Claude Fable 5.1 4 → 4.33 of 5 (3 of 3 runs); judge gpt-6-astra.
- v1.1 Added FR (France) and PT (Brazil) adaptations to local practice (not a translation): written by claude-opus-5-5, edited by gpt-6-astra, tested on separate pre-written rubrics and inputs: FR Claude Opus 5.5 4 of 5 (3 of 3 runs); FR Claude Sonnet 5 4 of 5 (3 of 3 runs); FR Claude Fable 5.1 4 of 5 (3 of 3 runs); PT Claude Opus 5.5 4 of 5 (3 of 3 runs); PT Claude Sonnet 5 4 of 5 (3 of 3 runs); PT Claude Fable 5.1 4 of 5 (3 of 3 runs); judge gpt-6-astra.
- v1.1 Revised after the first test round (EN v1.1, ES v1.1): behaviour rules fixed, rewritten by claude-opus-5-5, edited by gpt-6-astra, re-tested on the same pre-written rubric and input. Test: EN Claude Opus 5.5 5 of 5 (3 of 3 runs); EN Claude Sonnet 5 4.33 of 5 (3 of 3 runs); ES Claude Opus 5.5 5 of 5 (3 of 3 runs); ES Claude Sonnet 5 5 of 5 (3 of 3 runs); judge gpt-6-astra. Added 2026-10-20: Claude Fable 5.1 on the same version, inputs and rubrics: EN 5 of 5 (3 of 3 runs); ES 5 of 5 (3 of 3 runs); judge gpt-6-astra.
- v1.0 First release. Written by claude-opus-5-5, edited by gpt-6-astra. First test round: EN Claude Opus 5.5 4 of 5 (3 of 3 runs); EN Claude Sonnet 5 3.7 of 5 (3 of 3 runs); ES Claude Opus 5.5 4 of 5 (3 of 3 runs); ES Claude Sonnet 5 3.3 of 5 (3 of 3 runs).
One tested AI workflow a week
Tested prompts and skills for your profession, with dates and limits. No sponsors, no popups.