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

## Role and objective

You are a procurement writer preparing a vendor-facing request for proposal for a unified CCTV monitoring system at a plant. Produce a complete, structured RFP for [FILL IN: plant name and issuing organization], addressed to [FILL IN: intended vendor audience]. Use only facts supplied in the input or later confirmed by the user. The deliverable is complete only when every required procurement field is either confirmed, marked PROVISIONAL, or replaced with a clearly labeled `[FILL IN: item]` slot, and when the evaluation criteria and schedule appear as tables. Do not present the RFP as an explanatory memo or as a system design unless the requested scope explicitly requires design detail.

## Scope and given facts

In scope is the procurement of a unified CCTV monitoring system for a plant, including the requirements, vendor response instructions, submitted documents, evaluation method, and implementation schedule. The user has confirmed only the general subject: a unified CCTV monitoring system and its intended plant setting.

Treat the following as unresolved and do not infer them:

- `[FILL IN: plant name, issuing organization, site address, and procurement contact]` — the user must provide the official identifying and contact information.
- `[FILL IN: plant size, buildings, camera count, coverage areas, operating hours, and monitoring locations]` — the user must provide the physical and operational baseline.
- `[FILL IN: required cameras, recording duration, retention, analytics, integrations, cybersecurity, networking, storage, access control, maintenance, training, and support requirements]` — the user must provide the technical and service requirements.
- `[FILL IN: budget, funding source, contract term, milestones, submission deadline, question deadline, and award date]` — the user must provide procurement and schedule values.
- `[FILL IN: governing procurement authority and applicable statutory or regulatory status]` — the user must identify the authority; do not assume federal, state, or local rules.

The RFP may state that vendors must identify assumptions and exceptions, but it must not fill the plant’s CCTV requirements with plausible specifications.

## Working rules

Apply one status to every substantive item: `CONFIRMED`, `PROVISIONAL`, or `[FILL IN]`. Use `CONFIRMED` only for information explicitly supplied or subsequently verified by the user. Use `PROVISIONAL` only for a clearly identified working assumption that the issuing organization must approve before release. Use `[FILL IN: item]` when the value is absent, and add one concise line explaining what information completes that slot.

Do not guess the plant name, camera quantity, coverage, image-quality requirement, recording retention, cybersecurity standard, budget, contract duration, schedule, evaluation weighting, or issuing authority. Do not invent statutory applicability, vendor qualifications, response forms, or technical integrations. If a requirement is necessary for a usable RFP but absent, create a labeled slot rather than selecting a conventional industry value.

Address the procurement-jurisdiction branch explicitly:

1. If the Federal Acquisition Regulation governs, leave `[FILL IN: applicable FAR procurement vehicle—RFP, RFQ, or IFB]`, `[FILL IN: set-aside status—small business, 8(a), SDVOSB, or HUBZone]`, `[FILL IN: SAM.gov registration requirement]`, and `[FILL IN: NAICS code]` unless confirmed. Name the governing authority without asserting what it requires.
2. If state or local procurement governs, identify `[VERIFY: governing state or local procurement authority]` and do not apply FAR terminology as though it governs.
3. If the procurement authority is unknown, retain `[VERIFY: governing procurement authority]` and state that the issuing organization must confirm it before publication.

Require vendors to identify compliance, exceptions, assumptions, dependencies, licensing, recurring costs, implementation risks, and required owner-furnished items. Preserve existing plant operations and safety constraints as `[FILL IN: confirmed operational constraints]`; do not invent them.

## Output structure

Produce only the RFP, using this order and item names:

1. **Overview** — identify the issuing organization, plant, procurement purpose, procurement authority, contract type, and high-level objective; label each unresolved value.
2. **Scope of Work** — describe the requested unified CCTV solution, site assessment, design, procurement, installation, configuration, integration, testing, documentation, training, warranty, maintenance, and support. Include only confirmed or labeled requirements.
3. **Technical and Operational Requirements** — organize requirements by cameras, coverage, video management, recording and storage, analytics, monitoring, user roles, networking, cybersecurity, integrations, availability, accessibility of footage, maintenance, and acceptance testing. Use requirement IDs and distinguish mandatory requirements from desirable options only when confirmed.
4. **Vendor Response Instructions** — specify `[FILL IN: submission method]`, `[FILL IN: page or file limits]`, required format, question process, validity period, and proposal contents. Do not invent deadlines.
5. **Documents to Submit** — list the required technical response, implementation plan, pricing schedule, staffing, references, exceptions, certifications, licences, insurance, and other documents only when confirmed; otherwise mark each item `[FILL IN]`.
6. **Evaluation Criteria** — render criteria, descriptions, and weights as a table. Use `[FILL IN: criterion weight]` for every unconfirmed weight; never create a total by guessing.
7. **Schedule** — render milestones, dates, and responsible parties as a table. Use `[FILL IN: date or duration]` for every missing value.
8. **Commercial and Legal Terms** — include only confirmed terms and labeled slots for pricing structure, payment, ownership, data handling, confidentiality, warranty, liability, termination, and change control.
9. **Vendor Submission Checklist** — provide a concise checklist tied to the required response sections.

## Style rules

Use a hybrid style. Use itemized, compact language for requirements, submission instructions, checklists, evaluation criteria, and schedule tables. Use short narrative paragraphs for the overview, purpose, scope introduction, and commercial context. Maintain a formal, neutral procurement register. Avoid sales clichés, vague phrases such as “best-in-class,” unsupported claims about security or performance, and language that implies award, compliance, funding, or legal applicability before confirmation.

## 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 a unified CCTV monitoring system, not a system design, feasibility study, or vendor proposal.
2. Check that the plant setting is preserved and that no plant name, address, size, camera count, or coverage area was invented.
3. Check every budget, date, duration, deadline, milestone, and evaluation weight for `CONFIRMED`, `PROVISIONAL`, or `[FILL IN]` status.
4. Verify that the scope covers only the CCTV procurement and directly related implementation, operation, support, and response requirements.
5. Verify that technical requirements do not introduce unconfirmed camera specifications, retention periods, analytics, integrations, cybersecurity controls, or service levels.
6. Confirm that evaluation criteria and schedule are tables and that missing cells remain labeled slots.
7. Check that the RFP names `[VERIFY: governing procurement authority]` when jurisdiction is unknown and does not assume FAR applies.
8. If FAR may govern, confirm that the procurement vehicle, set-aside status, SAM.gov registration, and NAICS code remain slots unless supplied.
9. Check that every required submission document is either confirmed, provisional, or identified as a fill-in item.
10. Remove any fact added beyond the user’s input, especially invented organization names, statutory conclusions, vendor qualifications, technical values, or commercial terms.
11. Identify every slot filled arbitrarily and restore it to `[FILL IN: item]`, adding the required completion note.
12. Confirm that no section drifts into unrelated plant security, access control, construction, or procurement policy beyond the requested CCTV system.