VICTOROFF — TWELVE QUESTIONS BEFORE AN AI WORKFLOW PILOT
Version: 1.0.0
Date: 2026-09-24
Status: Review
Author: Victoroff

A practical meeting worksheet. Educational material, not a security certification,
audit opinion or evidence that a proposed service has been accepted.
Use a non-confidential description. Do not put customer records or credentials here.

YOUR BOUNDED QUESTION
Workflow category:
Outcome you want to explain:
Decision this review should support:
Snapshot time or period:

1. WHAT CAN CHANGE?
List the operations the system can attempt: read, recommend, draft, write, approve,
release or delete. Separate demonstrated behavior from proposed capabilities.
Notes:

2. WHO ACTS?
Identify the user, model, application, tool and execution identity. Do not assume
that the conversational assistant and the identity making a write are the same.
Notes:

3. WHAT ESTABLISHES AUTHORITY?
Name the applicable delegation or governing instrument, its version and conditions.
Tool access alone does not answer whether this particular action is authorized.
Notes:

4. WHICH RECORDS SUPPORT THE ANSWER?
Ask for source identifiers, timestamps and the relevant content. Mark provenance
as supplied or independently checked; do not assume a source label proves origin.
Notes:

5. WHAT IS MISSING?
List unknowns and contradictions. Absence from a snapshot does not establish that
an event never happened elsewhere or later.
Notes:

6. WHAT NEEDS HUMAN APPROVAL?
Identify the exact action and object being approved, the approver and conditions.
Ask what happens when a material fact changes after approval.
Notes:

7. WHERE IS THE EXECUTION RESULT?
Distinguish a proposed operation, a tool response and the system-owned final state.
Inspect the record of what actually happened rather than only the chat summary.
Notes:

8. WHAT MUST NOT HAPPEN?
Define negative acceptance cases using synthetic inputs: missing evidence,
expired approval, an out-of-scope action or an unavailable service.
Notes:

9. HOW WILL A SECOND REVIEWER CHECK THE FINDINGS?
Request a bounded report, cited findings, source register and explicit limitations.
Try following one conclusion to its supporting records without a spoken explanation.
Notes:

10. WHAT WOULD CLOSE EACH GAP?
Record a proposed action and the evidence that would establish completion.
Do not assign owners, deadlines or acceptance on another person's behalf.
Notes:

11. WHAT MUST BE AGREED BEFORE WORK BEGINS?
Confirm delivery owner, relevant expertise, capacity, scope, evidence handling,
commercial terms, timing and acceptance criteria. A demo is not delivery history.
Notes:

12. WHAT IS THE SMALLEST USEFUL NEXT STEP?
Choose one bounded investigation, prototype specification or scope discussion.
Separate it from future integrations, continuous monitoring and platform access.
Notes:

MEETING OUTPUT
Established findings:
Open questions:
Proposed owners to confirm:
Evidence needed next:
Acceptance criteria to agree:

NEXT STEP
Open the Victoroff journal and synthetic PAY-88219 example from the site where you
downloaded this worksheet. The demo uses fictional records and deterministic rules.
A proposed Snapshot engagement requires separate scope and availability confirmation.
No email address is required to use this worksheet.