COCasinoOpsAI
Surveillance • Controlled Intake

Review Request Intake Form

Convert a vague request into a bounded, authorized, evidence-aware surveillance assignment with clear questions, ownership, deadlines, privacy controls, and a defined deliverable.

Surveillance Review, Protection & Coverage Control SuiteCompare controls →
Authorize & scopeReview evidenceAssess coverageCorrect procedureAssure wording

Current workflow: Request Intake · Authorized intake. The suite supports restricted evidence handling and human review; it does not determine guilt, authorize surveillance expansion, or replace official source records and approvals.

How to use this tool

  1. Confirm requester, authority, purpose, priority, and deadline.
  2. Bound the event window, location, inclusions, exclusions, and privacy restrictions.
  3. List required source records and preservation responsibilities.
  4. Translate the request into answerable questions and a controlled deliverable.
New unsaved draft
Intake safeguard: A surveillance request should define a legitimate operational purpose, an authorized requester, a bounded time range, necessary source records, privacy restrictions, and a clear decision or deliverable. Do not use an intake form as a substitute for emergency response or evidence preservation.

Request identity and authority

Establish who is asking, why the review is legitimate, who authorized it, and how urgently it is needed.

1

Review scope

Bound the location, people or roles, event window, inclusions, exclusions, and known limitations before work begins.

2

Requested sources and preservation

List every expected source, current availability, preservation need, owner, and due point.

3
Source / evidence referenceTypeRelevant periodAvailabilityPreservation statusOwner / custodianDueRemove

Review questions and deliverables

Translate the request into answerable questions with clear priority, output, and status.

4
Review questionWhy it mattersPriorityExpected outputOwnerStatusRemove

Intake position

Live readiness indicators from the request.

Sources0Requested evidence inputs
Unavailable / at risk0Source or preservation attention
Questions0Defined review questions
High priority0High / critical questions
Intake completeness0%

Communication and handoff

Define the review owner, notification route, requester contact, and controlled delivery requirements.

5

Quality checks

Resolve warnings before accepting the request.

    Generated intake brief

    Review and copy only after checking authority and scope.

    Enter the review request and generate the intake brief.
    Good request versus weak request
    • Good: bounded event period, legitimate purpose, specific decision, authorized requester, named evidence, and controlled recipients.
    • Weak: “check everything,” no authority, vague suspicion, unnecessary personal data, or no requested output.
    • Emergency response, active safety threats, and immediate preservation should follow property procedures first.