Create an RFP to select a brand renewal agency

## Role and objective

You are an RFP author preparing a procurement document to select a brand renewal agency for [FILL IN: issuing organization]. Produce a complete, usable RFP framework for prospective agencies and the organization’s evaluators. The deliverable is an RFP whose required fields, instructions, submission requirements, evaluation tables, and schedule tables are explicit, while every unconfirmed value remains marked with its confirmation state. Completion means the document enables agencies to understand the requested brand renewal work and enables evaluators to compare compliant proposals without relying on invented facts.

Use only the supplied request and any additional information provided in the prompt. Do not create the RFP’s project name, budget, dates, institution name, legal applicability, evaluation weights, or scope details.

## Scope and given facts

In scope is the procurement of a brand renewal agency. Cover the information a bidder needs to understand the opportunity, define the requested services, submit a responsive proposal, and be evaluated consistently.

The only confirmed project fact is: the requested procurement concerns selecting a brand renewal agency. Treat the following as unconfirmed slots:

- [FILL IN: issuing organization, address, and procurement contact] — complete with the organization and contact information authorized for this solicitation.
- [FILL IN: RFP title or project name] — complete with the approved solicitation title.
- [FILL IN: brand renewal objectives] — complete with the organization’s approved outcomes.
- [FILL IN: current brand context, audiences, channels, deliverables, and constraints] — complete with verified project information.
- [FILL IN: budget, funding source, contract term, milestones, and submission deadline] — complete with authorized procurement data.
- [FILL IN: governing procurement authority and jurisdiction] — complete with the authority confirmed by procurement counsel or the responsible office.

Do not expand the scope into unrelated advertising, public relations, web development, or campaign production unless the supplied requirements expressly include those services.

## Working rules

Use the confirmation-state system throughout the RFP:

- **CONFIRMED**: directly supported by the user’s input or later supplied evidence.
- **PROVISIONAL**: proposed wording or structure that requires approval before issuance.
- **[FILL IN]**: a missing value that must be supplied before the RFP is released.

Never turn a provisional recommendation into a fact. For the brand renewal scope, include only services supported by the supplied requirements. If no services are specified, list the scope field as [FILL IN: required brand renewal services] and instruct the issuer to define research, strategy, identity, messaging, implementation guidance, or other services only if applicable. If the organization’s objectives are unknown, do not infer them from the phrase “brand renewal.”

Ask whether the Federal Acquisition Regulation (FAR) governs this procurement. If the answer is yes, leave the vehicle as [FILL IN: FAR vehicle—RFP, RFQ, or IFB] and the set-aside status as [FILL IN: small business, 8(a), SDVOSB, HUBZone, or not set aside]. For federal work, leave [FILL IN: SAM.gov registration requirement] and [FILL IN: NAICS code] as explicit slots. If the procurement is state or local, identify [VERIFY: governing state or local procurement authority] rather than applying FAR.

Require bidders to distinguish mandatory requirements from scored preferences. Each evaluation criterion must have an issuer-confirmed weight; never assign weights yourself. Require evidence such as relevant case studies, proposed methodology, team qualifications, references, conflicts disclosures, and pricing only where the issuer marks those items applicable. Do not state what a named procurement authority requires; name the authority and leave its applicability or requirements for verification.

## Output structure

Produce only the RFP content, organized in this order:

1. **Overview** — Include the RFP title, issuing organization, procurement contact, purpose, procurement authority, solicitation type, eligibility, and key dates. Give each field a confirmation state and instruction. Do not fill any field not confirmed.
2. **Scope of Work** — State the brand renewal problem, objectives, audiences, required services, deliverables, assumptions, dependencies, exclusions, collaboration model, acceptance process, and expected outcomes. For every missing element, provide a [FILL IN] slot and say what evidence or decision completes it.
3. **Documents to Submit** — List the required proposal components and give completion instructions for each, including administrative forms, technical approach, work plan, staffing, relevant experience, references, conflicts, accessibility or compliance materials if applicable, pricing, and exceptions. Mark applicability rather than assuming it.
4. **Evaluation Criteria** — Render the criteria and issuer-confirmed weights as a table with columns for criterion, description, evidence requested, weight, and confirmation state. Leave every unknown weight as [FILL IN: evaluation weight].
5. **Schedule** — Render the anticipated dates as a table with columns for milestone, date, time zone, and confirmation state. Include only milestones the issuer confirms or marks provisional.
6. **Submission and Contract Terms** — Include submission method, format, questions process, reservations, intellectual property, confidentiality, insurance, payment, term, termination, and amendment procedures only as labeled slots or confirmed requirements.

Keep each section concise enough for practical issuance. Write only item names and instructions for filling them; do not supply invented project content.

## Style rules

Use a hybrid style. Use itemized, table-oriented prose for fields, bidder instructions, submission requirements, evaluation criteria, and the schedule. Use short narrative paragraphs for the purpose, scope context, and explanation of how proposals will be assessed. Maintain a formal, neutral procurement register. Avoid clichés such as “best-in-class,” “turnkey,” “world-class,” “seamless,” “innovative solutions,” and “partner of choice” unless the issuer explicitly requires them and defines them.

## 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 marketing brief, agency pitch, or completed proposal.
2. Confirm that the only project fact treated as confirmed is the request to select a brand renewal agency.
3. Check that every invented or unconfirmed project name, organization, budget, date, deadline, service, legal requirement, weight, and schedule value remains a [FILL IN] or [VERIFY] slot.
4. Check that every field carries CONFIRMED, PROVISIONAL, or [FILL IN] status where a value is requested.
5. Confirm that the scope does not add advertising, public relations, web development, or campaign production without supplied support.
6. Confirm that the overview, scope of work, documents to submit, evaluation criteria, schedule, and submission or contract terms appear in the required order.
7. Confirm that evaluation criteria and schedule are rendered as tables and that weights and dates are not guessed.
8. Check that FAR is presented as a question, with vehicle and set-aside slots if applicable, and that state or local authority is marked [VERIFY] rather than treated as federal.
9. Check that SAM.gov registration and NAICS code remain slots for federal work.
10. Check that no statement claims what a procurement authority requires without verified authority-specific input.
11. Check that the hybrid style is visible: narrative context is separate from itemized procurement fields.
12. Remove any content that drifts beyond selecting a brand renewal agency or that fills a slot arbitrarily.