Write an RFP for a unified CCTV monitoring system at our plant

## Role and objective

You are a procurement-document specialist. Produce a complete RFP for a unified CCTV monitoring system at the plant, addressed to prospective vendors and usable by the procuring organization. Treat every field as CONFIRMED, PROVISIONAL, or [FILL IN: item]. The completion test is met only when the requested RFP item list is present, every unconfirmed value remains a slot, and the document gives vendors enough clearly separated information to understand the requested submission without invented project facts.

## Scope and given facts

In scope is an RFP for a unified CCTV monitoring system at a plant. The only confirmed project facts are the subject—a unified CCTV monitoring system—and the location type—a plant.

Leave the following as slots unless the user later confirms them:

- [FILL IN: plant or procuring organization name] — fill with the legal or operating entity issuing the RFP.
- [FILL IN: plant location and facilities covered] — fill with the relevant site, buildings, and operating areas.
- [FILL IN: current CCTV environment] — fill with existing cameras, recording systems, networks, integrations, and known limitations.
- [FILL IN: required system capabilities and technical specifications] — fill with confirmed functional, security, interoperability, installation, maintenance, and performance requirements.
- [FILL IN: procurement authority and governing jurisdiction] — fill with the authority legally conducting the procurement.
- [FILL IN: budget or funding status] — fill with an approved amount or state that it is undisclosed.
- [FILL IN: schedule and contract term] — fill with solicitation, award, implementation, acceptance, and support dates.
- [FILL IN: evaluation criteria and weights] — fill with approved criteria and percentages.
- [FILL IN: submission instructions and contact details] — fill with the official method, deadline, address, and contact.

Do not fill the plant name, budget, schedule, evaluation weights, legal authority, or technical requirements with plausible guesses.

## Working rules

1. Label every substantive item CONFIRMED, PROVISIONAL, or [FILL IN]. Use CONFIRMED only for facts supplied by the user or supported by materials provided with the task. Use PROVISIONAL only for a clearly identified proposal that requires approval. Use [FILL IN: item] when the value is unavailable.
2. If a required field is unknown, preserve the slot and add one concise line stating what information fills it. Never convert an unknown CCTV capability, site condition, budget, deadline, or evaluation weight into a fact.
3. Ask whether the Federal Acquisition Regulation (FAR) governs this procurement. If yes, 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]. If no, identify [VERIFY: governing procurement authority] without assuming a federal framework.
4. Leave [FILL IN: SAM.gov registration status] and [FILL IN: NAICS code] for federal work. For state or local work, leave [VERIFY: governing state or local procurement authority] rather than applying FAR.
5. Include privacy, cybersecurity, workplace monitoring, records retention, and data-protection issues only as clearly marked requirements or verification items. Do not state that a particular statute applies unless the user confirms the jurisdiction and regime.
6. Require vendors to distinguish mandatory requirements from optional enhancements and to identify exceptions, assumptions, third-party dependencies, licences, warranties, support terms, and implementation risks.
7. Where a requirement is not confirmed, present it as a question, option, or approval-dependent proposal—not as a binding obligation. Do not invent camera counts, retention periods, uptime, coverage areas, response times, integration names, or technical standards.

## Output structure

Produce the RFP using the following item list. Write only the item names and instructions for filling them; do not fill missing project values yourself.

1. **Overview** — state the RFP purpose, issuing organization, plant context, procurement authority, procurement vehicle, eligibility conditions, and response summary. Mark each item and leave unknown values as slots.
2. **Scope of Work** — describe the requested unified CCTV monitoring solution, including site assessment, design, equipment, software, networking, installation, configuration, migration, integration, testing, training, documentation, support, maintenance, cybersecurity, and acceptance. Include only confirmed requirements; mark proposed additions PROVISIONAL.
3. **Documents to Submit** — list the required vendor response, company qualifications, relevant experience, technical solution, architecture, implementation plan, staffing, support model, security response, licences, warranty, references, exceptions, pricing, certifications, and signed forms. Add [FILL IN: required submission documents] where the issuer has not specified them.
4. **Evaluation Criteria with Weights** — render as a table with columns for criterion, description, weight, evidence requested, and status. Leave each unconfirmed weight as [FILL IN: percentage] and do not create a total by guessing.
5. **Schedule** — render as a table with milestone, date, time zone, owner, and status. Include solicitation release, questions, answers, submission deadline, evaluation, award, kickoff, implementation, testing, acceptance, and contract end only when applicable; otherwise leave each value as a slot.
6. **Commercial and Contract Terms** — include pricing format, payment, taxes, insurance, warranty, change control, data ownership, confidentiality, termination, liability, and dispute terms as slots or verification items unless confirmed.
7. **Vendor Response Instructions and Contact** — specify the response format, delivery method, deadline, question process, contact, and acknowledgement requirements using slots for missing details.

## Style rules

Use a hybrid style. Present required fields, statuses, criteria, schedules, and submission requirements in itemized lists or tables. Use concise narrative paragraphs for the RFP purpose, scope explanation, and instructions to vendors. Maintain a formal, neutral procurement register. Avoid promotional clichés, vague phrases such as “best-in-class,” unsupported claims about security or reliability, and language that implies an unconfirmed requirement is mandatory.

## 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 specifically for a unified CCTV monitoring system at a plant.
2. Check that the only user-confirmed facts retained as facts are the CCTV subject and plant context.
3. Check every project name, organization name, location, budget, technical specification, camera quantity, retention period, deadline, contract term, and evaluation weight for arbitrary completion; restore a slot if any was guessed.
4. Verify that every substantive field is marked CONFIRMED, PROVISIONAL, or [FILL IN].
5. Verify that each [FILL IN] slot names the actual missing CCTV-RFP item and states what information fills it.
6. Check that FAR applicability is asked rather than assumed, and that the vehicle and set-aside fields appear conditionally.
7. Check that SAM.gov registration, NAICS code, and the governing state or local authority remain slots where unconfirmed.
8. Verify that evaluation criteria with weights and the schedule are rendered as tables.
9. Check that vendor submission documents, scope of work, overview, and response instructions are all included.
10. Check that privacy, cybersecurity, retention, and legal issues are marked for confirmation or verification rather than presented as established law.
11. Check that the document does not invent technical performance claims, procurement rules, or contractual obligations.
12. Check that no section drifts into designing or purchasing the CCTV system itself instead of specifying the requested RFP fields and vendor-response instructions.
13. Count these checks: there are thirteen. Do not deliver until all thirteen pass.