Write an RFP for outsourcing company-wide data literacy training

## Role and objective

You are a procurement and learning-and-development document specialist. Produce a complete, submission-ready RFP for outsourcing company-wide data literacy training, addressed to prospective training providers and usable by the procuring organization. Do not write a proposal, vendor response, training curriculum, or explanatory commentary outside the RFP. Use only facts supplied in the input; represent every missing procurement fact with the required status and slot convention.

The output form is a structured RFP containing the required item list, fillable instructions, tables for evaluation criteria and schedule, and confirmation states. Completion is achieved only when every required field is either supported by the input or explicitly marked `CONFIRMED`, `PROVISIONAL`, or `[FILL IN]`, with no invented project details.

## Scope and given facts

In scope:

- Outsourcing company-wide data literacy training.
- A procurement document that tells qualified providers what to submit.
- The required RFP items: overview, scope of work, documents to submit, evaluation criteria with weights, and schedule.
- Requirements for data-literacy training delivery, governance, measurement, and vendor responses only to the extent supported by supplied facts.

The only confirmed project fact is that the requested procurement concerns company-wide data literacy training. Do not infer the organization’s name, industry, workforce size, locations, learner groups, skill baseline, delivery format, technology environment, accessibility needs, budget, contract term, start date, deadline, legal authority, or desired outcomes.

Use these slots where information is absent:

- `[FILL IN: procuring organization, department, and contact details]` — completed by the issuing organization.
- `[FILL IN: learner population, locations, and baseline needs]` — completed by the business owner or training lead.
- `[FILL IN: learning outcomes, delivery requirements, budget, dates, and contract terms]` — completed by the procurement and program teams.
- `[VERIFY: governing procurement authority and applicable regime]` — completed after legal or procurement confirmation.

Do not fill the company-wide data literacy training brief with plausible assumptions.

## Working rules

Apply one status to every substantive item:

- `CONFIRMED` means the input explicitly establishes it.
- `PROVISIONAL` means it is a working requirement that the issuing organization must validate before release.
- `[FILL IN]` means the value is absent and must be supplied; add one short line identifying who or what supplies it.

If a requirement is necessary to make the RFP usable but is not in the input, mark it `PROVISIONAL` only when presenting it as a reviewable recommendation. Otherwise use `[FILL IN]`. Never convert a recommendation into a confirmed requirement.

Ask for the missing procurement facts that materially affect vendor responses: the procuring organization and contact, the learner and delivery profile, and the budget, timetable, evaluation weights, and governing authority. Keep each question tied to the company-wide data literacy training procurement.

Define the scope so vendors can respond to measurable requirements, but leave unconfirmed measures as slots. Separate mandatory requirements from desirable capabilities. If the organization has not specified whether delivery is instructor-led, virtual, self-paced, blended, or cohort-based, present the delivery model as `[FILL IN: required delivery model]`, not as a choice silently made by you.

Identify whether the Federal Acquisition Regulation governs. If it may apply, leave `[FILL IN: applicable FAR procurement vehicle—RFP, RFQ, or IFB]` and `[FILL IN: set-aside status—small business, 8(a), SDVOSB, HUBZone, or not set aside]`. For federal work, leave `[FILL IN: SAM.gov registration requirement/status]` and `[FILL IN: NAICS code]`. For state or local procurement, name `[VERIFY: governing state or local procurement authority]` without assuming FAR applies. Do not state what any named authority requires.

## Output structure

Produce only the RFP, using this item order:

1. **Overview** — State the procurement purpose, issuer, audience, procurement reference, response contact, and key dates. Instruct the issuer to fill every absent value and mark each item’s status.
2. **Scope of Work** — Describe the requested company-wide data literacy training service, including learner groups, objectives, curriculum boundaries, delivery, materials, technology, accessibility, implementation, support, reporting, and success measures. Every unspecified element must remain a status-labelled slot or provisional requirement.
3. **Documents to Submit** — List the vendor response components, such as organizational qualifications, relevant experience, proposed approach, work plan, staffing, references, pricing, assumptions, risks, conflicts, and required certifications. Do not invent certification requirements.
4. **Evaluation Criteria with Weights** — Provide a table with columns for criterion, description, weight, evidence requested, and status. Leave each unconfirmed weight as `[FILL IN: percentage weight]`; ensure the weights are not presented as final until confirmed.
5. **Schedule** — Provide a table with milestone, date, owner, and status. Leave dates as `[FILL IN: date]`. Include only milestones appropriate to the procurement once confirmed.
6. **Submission and Administrative Instructions** — Include the response method, format, question process, validity period, confidentiality treatment, amendments, and contact details as slots unless supplied.
7. **Required Confirmations** — Identify the governing authority and applicable procurement vehicle. Include the FAR questions, federal registration slots, state/local authority verification, and any legal review items without asserting applicability.

Use tables for evaluation criteria and schedule. Do not fill any project name, budget, date, institution name, criterion weighting, or statutory determination.

## Style rules

Use a hybrid style. Use itemized, table-based language for requirements, submission instructions, evaluation criteria, statuses, and schedule. Use concise narrative paragraphs for the overview, scope explanation, and transitions between sections. Maintain a formal, neutral procurement register. Avoid promotional clichés such as “best-in-class,” “world-class,” “seamless,” “revolutionary,” and “turnkey” unless a bidder is explicitly instructed to substantiate such language.

## 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 outsourcing company-wide data literacy training, not a vendor proposal or training plan.
2. Confirm that the five required item groups—overview, scope of work, documents to submit, weighted evaluation criteria, and schedule—are present.
3. Confirm that every substantive item has exactly one of `CONFIRMED`, `PROVISIONAL`, or `[FILL IN]`.
4. Check that no project name, budget, schedule date, institution, learner count, evaluation weight, or legal applicability was invented.
5. Check that every unfilled slot names the actual missing item and identifies who or what should complete it.
6. Confirm that evaluation criteria and schedule appear as tables rather than unstructured prose.
7. Confirm that FAR, RFP/RFQ/IFB, set-aside status, SAM.gov, NAICS, and state or local authority are treated as verification items, not assumed facts.
8. Confirm that the scope distinguishes mandatory requirements from desirable capabilities where both are included.
9. Check that the document does not drift into writing curriculum content, supplier marketing copy, or a completed procurement decision.
10. Confirm that any proposed requirement not supplied by the input is visibly marked `PROVISIONAL` or `[FILL IN]`.
11. Confirm that the tone is neutral and procurement-ready, with itemized sections and narrative transitions matching the hybrid style.
12. Confirm that the output contains only the RFP and no explanation of these instructions or the verification process.