Create an RFP to select a brand renewal agency

## Role and objective

<instructions>
You are an RFP author and procurement-document specialist. Produce a complete request for proposal to select a brand renewal agency for [FILL IN: issuing organization]. Write for prospective agencies and the organization’s evaluation team. The deliverable is a structured RFP with clearly labeled required fields, tables for evaluation criteria and schedule, and no invented procurement facts.

Before drafting, reason through the supplied facts, identify missing information, and decide which fields must remain [FILL IN] or [VERIFY]. Then provide the RFP only. Completion requires that every required RFP item is present, every unconfirmed value is visibly marked, and the document enables comparable agency responses without asserting unverified legal or commercial facts.
</instructions>

## Scope and given facts

<context>
Confirmed fact: the requested procurement concerns selecting a brand renewal agency.

In scope: defining the opportunity, brand-renewal scope, bidder response requirements, evaluation method, procurement schedule, and submission instructions. Include only information needed for agencies to understand the work and prepare responsive proposals.

Out of scope unless supplied: naming the issuing organization, describing its market or audience, setting a budget, fixing deliverable quantities, establishing a timetable, selecting an incumbent, naming competitors, asserting legal requirements, or assigning evaluation weights.

Use these slots wherever the source material does not confirm a value:
- [FILL IN: issuing organization and procurement contact] — fill with the authorized buyer’s name, title, email, and organization.
- [FILL IN: brand renewal objectives and scope] — fill with the approved business objectives, audiences, channels, deliverables, and exclusions.
- [FILL IN: submission deadline and evaluation schedule] — fill with the procurement-approved dates and milestones.
- [FILL IN: budget or pricing instructions] — fill with an approved budget range or explicit pricing-response instruction.
- [VERIFY: governing procurement authority] — fill with the authority confirmed by procurement counsel or the contracting office.
</context>

## Working rules

<instructions>
Classify every item as CONFIRMED, PROVISIONAL, or [FILL IN]. Use CONFIRMED only for the stated fact that the procurement selects a brand renewal agency. Use PROVISIONAL only for wording that proposes a structure without asserting a final procurement decision. Use [FILL IN] for missing organization-specific content. Add one concise line explaining what information fills each [FILL IN] slot.

Do not guess the issuing organization, project name, budget, timeline, deliverable volume, evaluation weighting, contact details, legal regime, or bidder eligibility. Do not convert a proposed criterion into an approved requirement. If a criterion or schedule is not supplied, present its row or field as a completion instruction with [FILL IN], not as a value.

Ask whether the Federal Acquisition Regulation (FAR) governs the procurement. If it does, leave the procurement vehicle as [FILL IN: FAR vehicle — RFP, RFQ, or IFB] and the set-aside status as [FILL IN: federal set-aside status — small business, 8(a), SDVOSB, HUBZone, or none]. For federal work, leave [FILL IN: SAM.gov registration status] and [FILL IN: NAICS code]. If the procurement is state or local, identify [VERIFY: governing state or local procurement authority] rather than assuming FAR applies. Name the authority only; do not state what it requires.

Require bidders to distinguish facts, assumptions, proposed methods, fees, exclusions, dependencies, and conflicts of interest. Where a requirement is optional, label it “Optional” and state the condition that makes it applicable. Do not invent agency names, case studies, performance results, or references.
</instructions>

## Output structure

<output_format>
Write the RFP using the following item list. Fill only supplied facts; give completion instructions for every other item.

1. **Overview** — State the procurement purpose and provide [FILL IN: project title], [FILL IN: issuing organization], [FILL IN: background], and [FILL IN: desired outcomes].
2. **Scope of Work** — Describe the required brand-renewal work. Include [FILL IN: research requirements], [FILL IN: strategic work], [FILL IN: identity or messaging work], [FILL IN: implementation support], [FILL IN: required deliverables], [FILL IN: exclusions], and [FILL IN: acceptance criteria].
3. **Documents to Submit** — List the proposal components and specify what bidders must provide in each: agency profile, relevant experience, proposed team, approach, work plan, assumptions, risks, references, conflicts, pricing, and exceptions. Mark any unsupported component [FILL IN: submission requirement].
4. **Evaluation Criteria** — Render as a table with columns for criterion, description, evidence requested, and weight. Leave every weight as [FILL IN: evaluation weight] unless supplied. Include [FILL IN: evaluation process and scoring method].
5. **Schedule** — Render as a table with milestone and date columns. Include release, question deadline, answers, submission deadline, evaluation, interviews or presentations, notice of intent, and contract start only if applicable; otherwise mark each as [FILL IN: applicable milestone and date].
6. **Submission Instructions** — Provide [FILL IN: submission method], [FILL IN: file format], [FILL IN: page limit], [FILL IN: contact], and [FILL IN: deadline].
7. **Commercial and Contractual Information** — Include [FILL IN: contract term], [FILL IN: payment terms], [FILL IN: intellectual-property terms], [FILL IN: confidentiality terms], and [FILL IN: cancellation or amendment terms].
8. **Questions and Clarifications** — State where and by when questions must be sent, using slots unless confirmed.
</output_format>

## Style rules

Use a hybrid style. Use concise itemized language for field labels, submission requirements, tables, criteria, dates, and status markers. Use short narrative paragraphs for the procurement purpose, scope context, bidder instructions, and clarification of response expectations. Maintain a professional, neutral, non-promotional register. Avoid procurement clichés such as “best-in-class,” “seamless,” “world-class,” and “turnkey” unless they appear in supplied source material. Do not make the RFP sound like an award decision.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is an RFP for selecting a brand renewal agency, not a brand strategy, agency recommendation, or marketing brief.
2. Confirm that the only factual procurement premise treated as CONFIRMED is the user-supplied selection purpose.
3. Check that the project name, issuing organization, contact, scope specifics, budget, schedule, and evaluation weights are not invented.
4. Check that each missing item uses the correct [FILL IN: item] or [VERIFY: item] label and includes a line explaining how it is completed.
5. Confirm that the overview, scope of work, documents to submit, evaluation criteria, schedule, submission instructions, and commercial information all appear.
6. Confirm that evaluation criteria and schedule are rendered as tables, with unconfirmed values left as slots.
7. Check that FAR applicability is posed as a question and that federal vehicle, set-aside status, SAM.gov registration, and NAICS code remain slots.
8. Check that state or local procurement is not treated as governed by FAR and that its authority is marked [VERIFY].
9. Check that no invented agency, case study, statistic, legal conclusion, deadline, budget, or contract term appears.
10. Check that the text stays within brand-renewal agency procurement scope and does not add unrelated services.
11. Confirm that the hybrid boundary is followed: tables and requirements are itemized, while context and instructions use short narrative paragraphs.
12. Confirm that the final response contains the reasoning steps first and then only the completed RFP, without commentary about these instructions.