Read a complete illustrative engagement.
From supplied inputs to a board summary, evidence actions and a question reopened by a change.
Illustrative inputs, not a client.
The review question
What can the institution support on the supplied evidence before these two AI uses proceed?
The sponsor supplies generic procedure excerpts, a staff-use disclosure, an embedded-feature proposal and incomplete vendor disclosure. No real institution, vendor, person or confidential customer record is used.
Board summary
Two declared uses are documented. Staff drafting creates a version-control and input-boundary question. The embedded feature creates an unresolved data-reach and activation question. The file assigns evidence work to operations, risk/compliance, vendor management and IT.
A later-looking procedure is not necessarily the controlling procedure, and a vendor proposal does not establish which data the feature can access. Acting before those questions are resolved would leave the review rationale unsupported.
Illustrative recommendation
Retain the earlier controlled procedure as the baseline. Limit staff drafting to approved generic or redacted procedure material under human review once the input and version conditions are resolved. Keep the embedded feature disabled pending evidence of data reach, defaults and effective disablement.
Illustrative decision conditions
- The procedure owner confirms the controlling version and resolves the secondary-review conflict.
- Risk/compliance and operations review the permitted-input rule and redacted example; confidential material remains outside the public assistant.
- Vendor management supplies complete feature-specific handling answers, and IT provides authorized evidence of the relevant setting and control behavior.
- The authorized institution reviewer makes and records the actual decision separately; a source reference or completed checkbox is insufficient.
Conditional illustrative decision
Allow only the limited staff drafting workflow after its input and controlling-version conditions are evidenced and reviewed. Defer embedded-feature activation until the feature conditions are evidenced and the authorized institution reviewer records a separate decision.
Actual institution decision: ________________________
Institution reviewer: ________________________ Decision date: ________________________
A review prepares a file. It does not certify compliance, give a legal opinion or connect to a core.
Declared uses and evidence
| Use | Where it runs | Data it can touch | Owner | Evidence on hand | Question still open |
|---|---|---|---|---|---|
| Staff drafting of procedure explanations | A public assistant outside the institution | Reported procedure text; full inputs are not disclosed. Customer, member, account and confidential material must be excluded. | Operations procedure owner | Staff-use disclosure; earlier controlled procedure; later working copy; supplied approval record for the earlier version | Which version controls, and can the permitted input boundary be demonstrated? |
| Embedded AI summary feature in an existing platform | The vendor's service; downstream processing is not declared | Initial disclosure mentions event metadata; free-text reach, retention and downstream access are unresolved. | Vendor-management owner with IT review | Embedded-feature proposal and incomplete initial vendor disclosure | Is the feature enabled by default, what can it read, and does the institution's off setting stop the relevant processing? |
What the review covered
Agree the review boundary
Read the intake baseline and record the two declared uses and supplied materials.
The engagement is bounded to the supplied records and these two uses.
Boundary: No network discovery, system access or institution-wide census was performed.
Reconcile use disclosures
Compare staff-use disclosure with the embedded-feature proposal and vendor disclosure.
Staff inputs and vendor data reach remain incompletely declared.
Boundary: A disclosure does not establish actual behavior.
Reconcile procedure versions
Compare both supplied excerpts and their approval provenance.
Secondary-review instructions conflict; only the earlier version has supplied approval evidence.
Boundary: No full-procedure acceptance or supersession determination is made.
Prepare the reviewer file
Record observations, open questions, role assignments, recommendation and conditions.
The board summary explains why feature activation is deferred and staff drafting is limited.
Boundary: Preparation does not record a reviewer acceptance or an institutional decision.
Review a supplied change
Retain the baseline and compare a revised vendor disclosure to the initial disclosure.
Default activation and free-text data reach reopen the affected question.
Boundary: The revised disclosure is not a live configuration inspection.
Sources, versions and approval provenance
Intake and supplied-records list
Version: Intake baseline. Read in this illustration.
Sponsor scope acknowledgment is illustrated; no institutional authorization is recorded.
The list is the supplied starting point, not a complete technology census.
Staff-use disclosure
Version: Initial disclosure. Read in this illustration.
No authorization to send confidential material is supplied.
Self-report is incomplete and does not establish data exclusion or full usage coverage.
Earlier controlled procedure
Version: Revision 1. Excerpt compared in this illustration.
A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank.
This excerpt alone does not establish that the full procedure is complete, current or acceptable.
Later working procedure copy
Version: Revision 2 working copy. Excerpt compared in this illustration.
No approval record or supersession notice is supplied.
The higher revision number does not make this working copy the controlling version.
Embedded-feature proposal
Version: Proposal baseline. Read in this illustration.
No feature activation approval is supplied.
A proposal reference is evidence of a claim, not evidence of actual configuration or accepted controls.
Vendor feature disclosure
Version: Initial disclosure. Read in this illustration.
No institutional acceptance is supplied.
The disclosure leaves data reach and effective disablement unanswered.
Two conflicting procedure excerpts
Earlier controlled procedure - Revision 1
A second reviewer must approve an exception before staff act. If an instruction conflicts with the controlled procedure, pause and refer the question to the procedure owner.
A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank.
Later working procedure copy - Revision 2 working copy
Staff may act on a routine exception and notify the second reviewer afterward. The working copy does not say when an exception stops being routine.
No approval record or supersession notice is supplied.
Reviewer observation
The excerpts conflict on secondary review. No supersession evidence supports treating the later working copy as controlling. Input disclosure remains incomplete.
Retain the earlier controlled procedure as the review baseline; resolve conflict before using generated instructions operationally.
Source references show what was supplied. Inspection, acceptance and action completion require their own recorded evidence.
Open questions and assigned actions
Which procedure version controls?
The supplied excerpts conflict and the later working copy lacks approval and supersession evidence.
Evidence to return: Procedure owner's controlling-version confirmation, approval record and explicit treatment of the conflicting instruction.
Owner role: Operations procedure owner. Status: Open.
What text has staff sent, and what may they send?
The staff disclosure does not enumerate inputs or demonstrate exclusion of confidential material.
Evidence to return: A permitted-input rule, a redacted input example and a review of the disclosed usage boundary.
Owner role: Risk/compliance owner with operations. Status: Open.
What can the feature read, and is it effectively off?
Default behavior, fields, retention, downstream access and effective disablement are not established.
Evidence to return: Feature-specific handling terms, field list, retention answer and authorized configuration evidence.
Owner role: Vendor-management owner with IT. Status: Reopened by supplied change.
What evidence would permit a return to the reviewer?
The recommendation is conditional; no acceptance or institutional authorization is recorded.
Evidence to return: Completed role actions, reviewed supporting evidence and a separate recorded decision by the authorized institution reviewer.
Owner role: Risk/compliance owner. Status: Open.
Operations procedure owner
Confirm the controlling procedure and resolve the secondary-review conflict with an approval or correction record.
Due milestone: Before any generated procedure instruction is used operationally.
Evidence to return: Controlling-version confirmation and approved treatment of the conflicting instruction.
Assigned role; completion not asserted.
Risk/compliance owner with operations
Define permitted inputs, collect a redacted example, and review the staff-use disclosure before allowing the limited drafting workflow.
Due milestone: Before the limited staff drafting workflow begins.
Evidence to return: Permitted-input rule, redacted input example and documented review.
Assigned role; completion not asserted.
Vendor-management owner
Obtain feature-specific default, field-access, retention, downstream-processing and disablement answers; reconcile the revised disclosure.
Due milestone: Before feature activation is reconsidered.
Evidence to return: Written feature disclosure and handling terms with unresolved items identified.
Assigned role; completion not asserted.
IT owner
Inspect the authorized feature setting and document what the off control covers; use approved synthetic test material if a control test is authorized.
Due milestone: Before feature activation is reconsidered.
Evidence to return: Authorized setting record and any separately authorized control-test result.
Inspection and test are requested; neither is claimed completed.
Risk/compliance owner
Return the evidence and unresolved items to the authorized reviewer, then record any actual decision separately.
Due milestone: At the next reviewer decision milestone after the evidence actions.
Evidence to return: Reviewer observations and a separately completed institution decision record.
Reviewer acceptance and institution decision remain blank.
Retain the baseline. Reopen the affected question.
Keep the initial source register, excerpts, observations, open questions and recommendation together. The supplied follow-up does not overwrite them.
A supplied vendor change
A revised vendor feature disclosure is supplied after the baseline review.
Version: Revised disclosure. Read and compared in the follow-up illustration.
The revised disclosure says the feature is enabled unless the institution disables it and may read free-text service notes in addition to event metadata. No configuration capture or retention answer accompanies the revision.
Question reopened
What can the feature read, and is it effectively off?
The changed default and broader stated data reach require new configuration and handling evidence. The source change does not prove the live feature is active or that a disable control works.
Continue to defer feature activation and request the revised handling answers plus authorized setting evidence. The staff version-control question stays open on its existing evidence.
Actual institution decision: ________________________
Download the example
Send the review question.
Tell us the decision, deadline and accountable role. A person will reply within one business day.
Request a call