Read a complete illustrative engagement.
See the board summary, the action list and a question that reopened after a change.
The example in ninety seconds
Illustrative inputs, not a client.
Keep the vendor feature off. Consider staff drafts once your team accepts the input limits and human checks.
The example resolves which procedure to use. It still lacks proof of what the vendor does with data, what it can read and how it stops.
Read the four-page buyer preview. Full printable supporting packet.




Current example edition: October 17, 2026. Final institution tiers and decisions remain blank.
Board recommendation
- Recommendation
- Keep the vendor feature off. Consider staff drafts once your team accepts the input limits and human checks.
- Rationale
- The example resolves which procedure to use. It still lacks proof of what the vendor does with data, what it can read and how it stops.
- Conditions
- Retain Revision 1 as the controlling procedure baseline.
- Return an accepted input rule and evidence of generated-answer review before operational use.
- Obtain feature-specific handling terms and authorized shutdown evidence before reconsidering activation.
- Tiers
- Staff procedure drafting
- Tier 2 provisional; unknown factors may raise the tier
- Embedded vendor feature
- Tier 3 provisional pending data and control review
- Institution decision
- Left blank
- Institution reviewer
- Left blank
- Decision date
- Left blank
Review scope
- Uses
- 2
- Records
- Only the listed uses and listed source versions
- Exclusions
- Institution-wide discovery
- Live systems and configurations
- Confidential customer records
- Legal opinion and compliance certification
- Timing
- Illustrative sequence, not a measured delivery duration
Six-column evidence file
| 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 statement. Earlier approved rule and later draft. The team returned the approval and confirmed which rule applies. | Can the input limits and generated-answer review be demonstrated? |
| Embedded AI summary feature in an existing platform | The vendor's service; downstream processing is not described | The first notice mentions event data. It leaves three questions open. Can the tool read notes? What does it keep? Who else can see it? | Vendor-management owner with IT review | Proposal for the feature. The first vendor notice is incomplete. | Is the feature on by default? What can it read? When you switch it off, does it stop processing the data in question? |
- Id
- use-staff
- Use
- Staff drafting of procedure explanations
- Where it runs
- A public assistant outside the institution
- Data it can touch
- Reported procedure text; full inputs are not disclosed. Customer, member, account and confidential material must be excluded.
- Owner
- Operations procedure owner
- Evidence on hand
- Staff use statement. Earlier approved rule and later draft. The team returned the approval and confirmed which rule applies.
- Question still open
- Can the input limits and generated-answer review be demonstrated?
- Source ids
- src-staff
- src-procedure-earlier
- src-procedure-later
- src-procedure-confirmation
- Reviewer observation
- The reply shows which version to use in the example. What staff can enter and how to keep that use safe remain open.
- Review disposition
- Retain the earlier controlled procedure as the review baseline; resolve conflict before using generated instructions operationally.
- Id
- use-vendor
- Use
- Embedded AI summary feature in an existing platform
- Where it runs
- The vendor's service; downstream processing is not described
- Data it can touch
- The first notice mentions event data. It leaves three questions open. Can the tool read notes? What does it keep? Who else can see it?
- Owner
- Vendor-management owner with IT review
- Evidence on hand
- Proposal for the feature. The first vendor notice is incomplete.
- Question still open
- Is the feature on by default? What can it read? When you switch it off, does it stop processing the data in question?
- Source ids
- src-vendor-proposal
- src-vendor-disclosure
- Reviewer observation
- The documents describe a feature but do not establish the live setting or effective off control.
- Review disposition
- Wait to enable the feature. Ask for records on its settings and data use.
Sources, versions and returned evidence
- Id
- src-intake
- Title
- Intake and received records list
- Version
- Intake baseline
- Calendar date
- Left blank
- Approval status
- The example shows a sponsor who saw the scope. It records no approval from the institution.
- Review state
- Read in this illustration
- Content
- The review covers two uses. Staff draft from procedure text, and a vendor feature is under review. No customer or account data is on file.
- Limitation
- The review starts with this list. It does not cover every tool.
- Id
- src-staff
- Title
- Staff-use disclosure
- Version
- Initial disclosure
- Calendar date
- Left blank
- Approval status
- The file has no approval to send private records.
- Review state
- Read in this illustration
- Content
- Staff say they use a public assistant to draft text about procedures. The tool runs outside the institution. Staff have yet to name the version or list all the text they entered.
- Limitation
- Self-report is incomplete and does not establish data exclusion or full usage coverage.
- Id
- src-procedure-earlier
- Title
- Earlier controlled procedure
- Version
- Revision 1
- Calendar date
- Left blank
- Approval status
- The record shows the team approved this version through its process for procedure changes. The name of the approver and the date are blank.
- Review state
- Excerpt compared in this illustration
- Content
- 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.
- Limitation
- This excerpt alone does not establish that the full procedure is complete, current or acceptable.
- Id
- src-procedure-later
- Title
- Later working procedure copy
- Version
- Revision 2 working copy
- Calendar date
- Left blank
- Approval status
- The file lacks an approval or a notice that the new version replaced the old one.
- Review state
- Excerpt compared in this illustration
- Content
- 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.
- Limitation
- A higher version number does not show that this draft is in force.
- Id
- src-vendor-proposal
- Title
- Embedded-feature proposal
- Version
- Proposal baseline
- Calendar date
- Left blank
- Approval status
- The file has no approval to turn on the feature.
- Review state
- Read in this illustration
- Content
- The existing platform may include an AI-assisted summary feature. The proposal describes summaries. It does not say whether the feature starts on by default. It leaves three more questions open. Which fields does it read? What does it keep? How can you turn it off?
- Limitation
- The proposal records a claim. It does not show the live settings or which controls the team accepts.
- Id
- src-vendor-disclosure
- Title
- Vendor feature disclosure
- Version
- Initial disclosure
- Calendar date
- Left blank
- Approval status
- The file has no decision to accept the use.
- Review state
- Read in this illustration
- Content
- The notice mentions service event data and an admin setting. It does not say if the tool can read notes or where else the data goes. It also leaves out how long data stays and what the off setting does.
- Limitation
- The notice leaves two questions open. What can the tool read? What stops it?
- Id
- src-change
- Title
- Changed vendor feature disclosure
- Version
- Revised disclosure
- Calendar date
- Left blank
- Approval status
- The file has no decision to accept the use or turn on the feature.
- Review state
- Read and compared in the follow-up illustration
- Content
- The new notice says the feature starts on unless the team turns it off. It may read service notes as well as event data. The vendor sent no copy of the settings and no answer on how long it keeps data.
- Limitation
- The update reopens two questions. What data can the feature reach? Is it on by default? The live setting is still unknown.
- Id
- src-procedure-confirmation
- Title
- Returned controlling-version confirmation
- Version
- Owner response 1
- Calendar date
- Left blank
- Approval status
- Synthetic role confirmation; actual-institution signer and date remain blank
- Review state
- Inspected and judged sufficient in this illustration for the version question only
- Content
- The owner confirms Revision 1 is in force. The owner pulls the Revision 2 draft for this use and keeps the second check. The reply points to the approval and explains which instruction to follow.
- Limitation
- This answer shows which version controls in the example. It does not approve assistant use or show which inputs are allowed.
Review coverage
- Id
- cov-scope
- Activity
- Agree the review boundary
- What was done
- Read the intake baseline and record the two listed uses and received materials.
- Finding
- The engagement is bounded to the received records and these two uses.
- Limit
- No network discovery, system access or institution-wide census was performed.
- Id
- cov-disclosures
- Activity
- Reconcile use disclosures
- What was done
- Compare staff-use disclosure with the embedded-feature proposal and vendor disclosure.
- Finding
- Staff inputs and vendor data reach remain only partly described.
- Limit
- A disclosure does not establish actual behavior.
- Id
- cov-versions
- Activity
- Reconcile procedure versions
- What was done
- Compare both received excerpts and their approval history.
- Finding
- Secondary-review instructions conflict; only the earlier version has approval evidence on file.
- Limit
- No full-procedure acceptance or supersession determination is made.
- Id
- cov-review
- Activity
- Prepare the reviewer file
- What was done
- Record observations, open questions, role assignments, recommendation and conditions.
- Finding
- The board brief explains why the feature stays off. It also shows what limits staff drafts.
- Limit
- This step prepares the file. The reviewer and the institution have yet to record a decision.
- Id
- cov-change
- Activity
- Review an update
- What was done
- Retain the baseline and compare a revised vendor disclosure to the initial disclosure.
- Finding
- Two changes reopen the question. The feature starts on by default, and it may read notes.
- Limit
- The new notice does not show anyone checked the live settings.
Proposed risk tiers and method
- Source
- https://www.csbs.org/node/584231
- Source checked
- October 11, 2026
- Method
- Check who could be hurt and who can review the work. Ask how much harm a failure could cause and what data the tool can reach. The highest known score usually sets the first tier. Keep that tier open to change if facts are missing.
- Boundary
- Tiers follow the optional CSBS worksheet. Your institution assigns the final tier.
- Factor assessments
- Use id
- use-staff
- Consumer impact
- Tier 2: drafts may affect operational instructions
- Human oversight
- Unknown: consistent qualified review not evidenced
- Harm potential
- Tier 2: a wrong instruction could cause operational harm
- Data sensitivity
- Unknown: historical inputs not verified
- Preliminary tier
- Tier 2 provisional; unknown factors may raise the tier
- Use id
- use-vendor
- Consumer impact
- Unknown: output use not accepted
- Human oversight
- Unknown: checkpoints not evidenced
- Harm potential
- Unknown: operating dependence not established
- Data sensitivity
- Potential Tier 3: free-text service notes may contain sensitive information
- Preliminary tier
- Tier 3 provisional pending data and control review
- Version
- CSBS worksheet preparation: example edition 2026-10-17
Tier reasons and uncertainty
- Use id
- use-staff
- Proposed tier
- Tier 2 provisional; unknown factors may raise the tier
- Reasons
- Drafts may become operational instructions.
- Inputs and controlling versions were initially unclear.
- Source ids
- src-staff
- src-procedure-earlier
- src-procedure-later
- src-procedure-confirmation
- Uncertainty
- The review has yet to confirm what staff entered or whether anyone enforced the input limits.
- Possible treatment
- Consider Tier 1 after you confirm input limits, document versions and human review.
- Reviewer role
- Institution risk reviewer
- Reviewer status
- Pending institution review
- Institution accepted tier
- Left blank
- Use id
- use-vendor
- Proposed tier
- Tier 3 provisional pending data and control review
- Reasons
- The revised disclosure expands stated reach to free-text service notes.
- Default activation, retention and effective shutdown require evidence.
- Service notes may contain sensitive information; actual contents and safeguards remain unknown.
- Source ids
- src-vendor-disclosure
- src-change
- Uncertainty
- No authorized setting inspection or shutdown test has been returned.
- Possible treatment
- Keep the feature off. Get answers about data use and approved proof of the controls.
- Reviewer role
- Institution risk reviewer with IT
- Reviewer status
- Pending institution review
- Institution accepted tier
- Left blank
Safe-use policy gaps
- Id
- gap-input-version
- Use id
- use-staff
- Source ids
- src-staff
- src-procedure-earlier
- src-procedure-later
- Finding
- Neither excerpt says what staff can enter in a public tool. Neither says how to check its text against the rule in force.
- Proposed treatment
- Use only approved general procedure text or text with private details removed. Leave out member, account and private records. Record the version in force. Have a second person check the work before staff use it.
- Action id
- action-staff
- Owner role
- Risk/compliance owner with operations
- Status
- Open; treatment proposed, not an approved policy
- Board condition
- Tier 1 staff drafting remains conditional on reviewed input boundaries and generated-answer review.
Evidence states and reviewer observations
- Id
- assessment-version
- Question id
- q-procedure
- Source ids
- src-procedure-earlier
- src-procedure-later
- src-procedure-confirmation
- Declaration received
- Yes
- Reference received
- Yes
- Source inspected
- Synthetic reviewer compared the returned response with both excerpts
- What the evidence supports
- Sufficient in this illustration for controlling version only
- Reviewer role
- Illustrative procedure-control reviewer
- Review date
- Left blank
- Institution decision recorded
- No
- Limitation
- No actual-institution approval, use authorization or verified signature
- Id
- assessment-inputs
- Question id
- q-staff-data
- Source ids
- src-staff
- Declaration received
- Yes
- Reference received
- Yes
- Source inspected
- Synthetic review of received disclosure
- What the evidence supports
- Insufficient: input examples and an accepted safe-use treatment are missing
- Reviewer role
- Illustrative risk reviewer
- Review date
- Left blank
- Institution decision recorded
- No
- Id
- assessment-vendor
- Question id
- q-vendor
- Source ids
- src-vendor-disclosure
- src-change
- Declaration received
- Yes
- Reference received
- Yes
- Source inspected
- Synthetic comparison of initial and revised disclosures
- What the evidence supports
- More proof needed. The settings, stop control, time kept and later data use remain open.
- Reviewer role
- Illustrative risk reviewer with IT
- Review date
- Left blank
- Institution decision recorded
- No
Questions still open
- Id
- q-procedure
- Question
- Which procedure version controls?
- Reason
- The excerpts disagree. The file does not show that anyone approved the later draft or that it replaced the old one.
- Needed evidence
- Procedure owner's controlling-version confirmation, approval record and explicit treatment of the conflicting instruction.
- Owner role
- Operations procedure owner
- Status
- Resolved in illustration for controlling version only
- Resolution source id
- src-procedure-confirmation
- Resolution reason
- The returned owner response identifies the controlling version, approval reference and treatment of the conflicting instruction.
- Id
- q-staff-data
- Question
- What text has staff sent, and what may they send?
- Reason
- Staff did not list the inputs. The file does not show that staff kept private data out.
- Needed evidence
- A rule for allowed inputs, a redacted input example and a review of the disclosed usage boundary.
- Owner role
- Risk/compliance owner with operations
- Status
- Open
- Id
- q-vendor
- Question
- What can the feature read, and is it effectively off?
- Reason
- It is unclear whether the feature starts on, which fields it reads or how long it keeps data. The file also leaves open who else can read it and whether the off switch works.
- Needed evidence
- Feature-specific handling terms, field list, retention answer and authorized configuration evidence.
- Owner role
- Vendor-management owner with IT
- Status
- Reopened after an update
- Id
- q-return
- Question
- What evidence would permit a return to the reviewer?
- Reason
- The advice has conditions. The file records no decision to accept or approve the use.
- Needed evidence
- Completed role actions, reviewed supporting evidence and a separate recorded decision by the authorized institution reviewer.
- Owner role
- Risk/compliance owner
- Status
- Open
Actions and required evidence
- Id
- action-procedure
- Owner role
- Operations procedure owner
- Action
- 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
- Calendar due date
- Left blank
- Evidence to return
- Controlling-version confirmation and approved treatment of the conflicting instruction
- Status
- Resolved in illustration after sufficient returned evidence
- Question ids
- q-procedure
- Closure source ids
- src-procedure-confirmation
- Closure scope
- Version confirmation only; assistant authorization remains separate
- Reviewer role
- Illustrative procedure-control reviewer
- Actual institution acceptance
- Left blank
- Id
- action-staff
- Owner role
- Risk/compliance owner with operations
- Action
- Set what staff can enter. Get an example with private details removed. Read the staff statement before you allow the limited drafting use.
- Due milestone
- Before staff start the limited drafting use
- Calendar due date
- Left blank
- Evidence to return
- Rule for allowed inputs, redacted input example and documented review
- Status
- Assigned role; completion not asserted
- Question ids
- q-staff-data
- Id
- action-vendor
- Owner role
- Vendor-management owner
- Action
- Get answers on whether it starts on, which fields it can read, what it keeps and who else gets the data. Ask how it stops. Check those answers against the new notice.
- Due milestone
- Before feature activation is reconsidered
- Calendar due date
- Left blank
- Evidence to return
- Written feature disclosure and handling terms with unresolved items identified
- Status
- Assigned role; completion not asserted
- Question ids
- q-vendor
- Id
- action-it
- Owner role
- IT owner
- Action
- 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
- Calendar due date
- Left blank
- Evidence to return
- Authorized setting record and any separately authorized control-test result
- Status
- Inspection and test are requested; neither is claimed completed
- Question ids
- q-vendor
- Id
- action-board
- Owner role
- Risk/compliance owner
- Action
- Send the records and open questions to the person who can review them. Keep the final decision in a separate record.
- Due milestone
- When the reviewer next meets to decide, after the work is done
- Calendar due date
- Left blank
- Evidence to return
- Reviewer observations and a separately completed institution decision record
- Status
- The reviewer and institution decision fields are blank.
- Question ids
- q-return
Trace findings to the recommendation
- Finding
- Version conflict
- Question id
- q-procedure
- Action ids
- action-procedure
- Assessment id
- assessment-version
- Board recommendation
- Retain Revision 1 as the controlling baseline in this example.
- Condition
- Closing this action alone does not authorize AI use.
- Finding
- Safe-use policy gap and unknown historical inputs
- Question id
- q-staff-data
- Action ids
- action-staff
- Assessment id
- assessment-inputs
- Board recommendation
- Defer operational use of generated instructions pending accepted input and review rules.
- Condition
- Institution records its own decision after evidence review.
- Finding
- Expanded vendor data reach and unresolved shutdown
- Question id
- q-vendor
- Action ids
- action-vendor
- action-it
- Assessment id
- assessment-vendor
- Board recommendation
- Keep embedded-feature activation deferred.
- Condition
- Revised handling terms and authorized control evidence must return to review.
Retained baseline
- Id
- baseline-review
- Label
- Retained review baseline
- Source ids
- src-intake
- src-staff
- src-procedure-earlier
- src-procedure-later
- src-vendor-proposal
- src-vendor-disclosure
- 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.
- Decision conditions
- The procedure owner confirms the controlling version and resolves the secondary-review conflict.
- Risk/compliance and operations review the rule for allowed inputs 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.
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
- Retention note
- Keep the first source list, excerpts, findings, open questions and advice together. Add the reply without replacing those records.
Later change and reconsideration
- Id
- change-vendor-disclosure
- Trigger
- The vendor sends a new feature notice after the first review.
- Source id
- src-change
- Changed claim
- The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.
- Affected question id
- q-vendor
- Reopened question
- What can the feature read, and is it effectively off?
- Reviewer observation
- The new default and wider data access call for fresh records on settings and data use. The new notice does not prove the feature is on or that the stop control works.
- Actions reopened
- action-vendor
- action-it
- Baseline disposition
- Keep the first record. Add the new version and note what changed. Save both sets of evidence.
- Recommendation after change
- Keep the feature off. Get new data answers and approved proof of the settings. The example has settled which version applies. It still leaves open what staff can enter and how to check their answers.
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
Follow-up history
- Stage
- Initial baseline
- Records
- Schema version
- 1.0
- Source register
- Id
- src-intake
- Title
- Intake and received records list
- Version
- Intake baseline
- Calendar date
- Left blank
- Approval status
- The example shows a sponsor who saw the scope. It records no approval from the institution.
- Review state
- Read in this illustration
- Content
- The review covers two uses. Staff draft from procedure text, and a vendor feature is under review. No customer or account data is on file.
- Limitation
- The review starts with this list. It does not cover every tool.
- Id
- src-staff
- Title
- Staff-use disclosure
- Version
- Initial disclosure
- Calendar date
- Left blank
- Approval status
- The file has no approval to send private records.
- Review state
- Read in this illustration
- Content
- Staff say they use a public assistant to draft text about procedures. The tool runs outside the institution. Staff have yet to name the version or list all the text they entered.
- Limitation
- Self-report is incomplete and does not establish data exclusion or full usage coverage.
- Id
- src-procedure-earlier
- Title
- Earlier controlled procedure
- Version
- Revision 1
- Calendar date
- Left blank
- Approval status
- The record shows the team approved this version through its process for procedure changes. The name of the approver and the date are blank.
- Review state
- Excerpt compared in this illustration
- Content
- 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.
- Limitation
- This excerpt alone does not establish that the full procedure is complete, current or acceptable.
- Id
- src-procedure-later
- Title
- Later working procedure copy
- Version
- Revision 2 working copy
- Calendar date
- Left blank
- Approval status
- The file lacks an approval or a notice that the new version replaced the old one.
- Review state
- Excerpt compared in this illustration
- Content
- 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.
- Limitation
- A higher version number does not show that this draft is in force.
- Id
- src-vendor-proposal
- Title
- Embedded-feature proposal
- Version
- Proposal baseline
- Calendar date
- Left blank
- Approval status
- The file has no approval to turn on the feature.
- Review state
- Read in this illustration
- Content
- The existing platform may include an AI-assisted summary feature. The proposal describes summaries. It does not say whether the feature starts on by default. It leaves three more questions open. Which fields does it read? What does it keep? How can you turn it off?
- Limitation
- The proposal records a claim. It does not show the live settings or which controls the team accepts.
- Id
- src-vendor-disclosure
- Title
- Vendor feature disclosure
- Version
- Initial disclosure
- Calendar date
- Left blank
- Approval status
- The file has no decision to accept the use.
- Review state
- Read in this illustration
- Content
- The notice mentions service event data and an admin setting. It does not say if the tool can read notes or where else the data goes. It also leaves out how long data stays and what the off setting does.
- Limitation
- The notice leaves two questions open. What can the tool read? What stops it?
- Id
- src-change
- Title
- Changed vendor feature disclosure
- Version
- Revised disclosure
- Calendar date
- Left blank
- Approval status
- The file has no decision to accept the use or turn on the feature.
- Review state
- Read and compared in the follow-up illustration
- Content
- The new notice says the feature starts on unless the team turns it off. It may read service notes as well as event data. The vendor sent no copy of the settings and no answer on how long it keeps data.
- Limitation
- The update reopens two questions. What data can the feature reach? Is it on by default? The live setting is still unknown.
- Coverage activities
- Id
- cov-scope
- Activity
- Agree the review boundary
- What was done
- Read the intake baseline and record the two listed uses and received materials.
- Finding
- The engagement is bounded to the received records and these two uses.
- Limit
- No network discovery, system access or institution-wide census was performed.
- Id
- cov-disclosures
- Activity
- Reconcile use disclosures
- What was done
- Compare staff-use disclosure with the embedded-feature proposal and vendor disclosure.
- Finding
- Staff inputs and vendor data reach remain only partly described.
- Limit
- A disclosure does not establish actual behavior.
- Id
- cov-versions
- Activity
- Reconcile procedure versions
- What was done
- Compare both received excerpts and their approval history.
- Finding
- Secondary-review instructions conflict; only the earlier version has approval evidence on file.
- Limit
- No full-procedure acceptance or supersession determination is made.
- Id
- cov-review
- Activity
- Prepare the reviewer file
- What was done
- Record observations, open questions, role assignments, recommendation and conditions.
- Finding
- The board brief explains why the feature stays off. It also shows what limits staff drafts.
- Limit
- This step prepares the file. The reviewer and the institution have yet to record a decision.
- Id
- cov-change
- Activity
- Review an update
- What was done
- Retain the baseline and compare a revised vendor disclosure to the initial disclosure.
- Finding
- Two changes reopen the question. The feature starts on by default, and it may read notes.
- Limit
- The new notice does not show anyone checked the live settings.
- Six column evidence rows
- Id
- use-staff
- Use
- Staff drafting of procedure explanations
- Where it runs
- A public assistant outside the institution
- Data it can touch
- Reported procedure text; full inputs are not disclosed. Customer, member, account and confidential material must be excluded.
- Owner
- Operations procedure owner
- Evidence on hand
- Staff use statement. Earlier approved rule and later draft. The file includes approval of the earlier rule.
- Question still open
- Which version controls, and can the input limits be demonstrated?
- Source ids
- src-staff
- src-procedure-earlier
- src-procedure-later
- Reviewer observation
- The excerpts conflict on secondary review. No supersession evidence supports treating the later working copy as controlling. Input disclosure remains incomplete.
- Review disposition
- Retain the earlier controlled procedure as the review baseline; resolve conflict before using generated instructions operationally.
- Id
- use-vendor
- Use
- Embedded AI summary feature in an existing platform
- Where it runs
- The vendor's service; downstream processing is not described
- Data it can touch
- The first notice mentions event data. It leaves three questions open. Can the tool read notes? What does it keep? Who else can see it?
- Owner
- Vendor-management owner with IT review
- Evidence on hand
- Proposal for the feature. The first vendor notice is incomplete.
- Question still open
- Is the feature on by default? What can it read? When you switch it off, does it stop processing the data in question?
- Source ids
- src-vendor-proposal
- src-vendor-disclosure
- Reviewer observation
- The documents describe a feature but do not establish the live setting or effective off control.
- Review disposition
- Wait to enable the feature. Ask for records on its settings and data use.
- Conflicting procedure excerpts
- Source id
- src-procedure-earlier
- Excerpt
- 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.
- Approval state
- The record shows the team approved this version through its process for procedure changes. The name of the approver and the date are blank.
- Source id
- src-procedure-later
- Excerpt
- 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.
- Approval state
- The file lacks an approval or a notice that the new version replaced the old one.
- Open questions
- Id
- q-procedure
- Question
- Which procedure version controls?
- Reason
- The excerpts disagree. The file does not show that anyone approved the later draft or that it replaced the old one.
- Needed evidence
- Procedure owner's controlling-version confirmation, approval record and explicit treatment of the conflicting instruction.
- Owner role
- Operations procedure owner
- Status
- Open
- Id
- q-staff-data
- Question
- What text has staff sent, and what may they send?
- Reason
- Staff did not list the inputs. The file does not show that staff kept private data out.
- Needed evidence
- A rule for allowed inputs, a redacted input example and a review of the disclosed usage boundary.
- Owner role
- Risk/compliance owner with operations
- Status
- Open
- Id
- q-vendor
- Question
- What can the feature read, and is it effectively off?
- Reason
- It is unclear whether the feature starts on, which fields it reads or how long it keeps data. The file also leaves open who else can read it and whether the off switch works.
- Needed evidence
- Feature-specific handling terms, field list, retention answer and authorized configuration evidence.
- Owner role
- Vendor-management owner with IT
- Status
- Reopened after an update
- Id
- q-return
- Question
- What evidence would permit a return to the reviewer?
- Reason
- The advice has conditions. The file records no decision to accept or approve the use.
- Needed evidence
- Completed role actions, reviewed supporting evidence and a separate recorded decision by the authorized institution reviewer.
- Owner role
- Risk/compliance owner
- Status
- Open
- Actions
- Id
- action-procedure
- Owner role
- Operations procedure owner
- Action
- 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
- Calendar due date
- Left blank
- Evidence to return
- Controlling-version confirmation and approved treatment of the conflicting instruction
- Status
- Assigned role; completion not asserted
- Question ids
- q-procedure
- Id
- action-staff
- Owner role
- Risk/compliance owner with operations
- Action
- Set what staff can enter. Get an example with private details removed. Read the staff statement before you allow the limited drafting use.
- Due milestone
- Before staff start the limited drafting use
- Calendar due date
- Left blank
- Evidence to return
- Rule for allowed inputs, redacted input example and documented review
- Status
- Assigned role; completion not asserted
- Question ids
- q-staff-data
- Id
- action-vendor
- Owner role
- Vendor-management owner
- Action
- Get answers on whether it starts on, which fields it can read, what it keeps and who else gets the data. Ask how it stops. Check those answers against the new notice.
- Due milestone
- Before feature activation is reconsidered
- Calendar due date
- Left blank
- Evidence to return
- Written feature disclosure and handling terms with unresolved items identified
- Status
- Assigned role; completion not asserted
- Question ids
- q-vendor
- Id
- action-it
- Owner role
- IT owner
- Action
- 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
- Calendar due date
- Left blank
- Evidence to return
- Authorized setting record and any separately authorized control-test result
- Status
- Inspection and test are requested; neither is claimed completed
- Question ids
- q-vendor
- Id
- action-board
- Owner role
- Risk/compliance owner
- Action
- Send the records and open questions to the person who can review them. Keep the final decision in a separate record.
- Due milestone
- When the reviewer next meets to decide, after the work is done
- Calendar due date
- Left blank
- Evidence to return
- Reviewer observations and a separately completed institution decision record
- Status
- The reviewer and institution decision fields are blank.
- Question ids
- q-return
- Retained baseline
- Id
- baseline-review
- Label
- Retained review baseline
- Source ids
- src-intake
- src-staff
- src-procedure-earlier
- src-procedure-later
- src-vendor-proposal
- src-vendor-disclosure
- 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.
- Decision conditions
- The procedure owner confirms the controlling version and resolves the secondary-review conflict.
- Risk/compliance and operations review the rule for allowed inputs 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.
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
- Retention note
- Keep the first source list, excerpts, findings, open questions and advice together. Add the reply without replacing those records.
- Change event
- Id
- change-vendor-disclosure
- Trigger
- The vendor sends a new feature notice after the first review.
- Source id
- src-change
- Changed claim
- The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.
- Affected question id
- q-vendor
- Reopened question
- What can the feature read, and is it effectively off?
- Reviewer observation
- The new default and wider data access call for fresh records on settings and data use. The new notice does not prove the feature is on or that the stop control works.
- Actions reopened
- action-vendor
- action-it
- Baseline disposition
- Keep the first record. Add the new version and note what changed. Save both sets of evidence.
- Recommendation after change
- Keep the feature off. Get new data answers and approved proof of the settings. At this point in the example, the records still do not show which version staff should use.
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
- Disclosure
- Supporting records for a synthetic illustration; no institutional acceptance or live inspection is asserted.
- Note
- Retained unchanged. Initial questions and actions remain visible as history.
- Stage
- Returned evidence
- Source id
- src-procedure-confirmation
- Question id
- q-procedure
- Action id
- action-procedure
- Result
- Version question resolved in the illustration; assistant use remains unapproved.
- Stage
- Later vendor change
- Event
- Id
- change-vendor-disclosure
- Trigger
- The vendor sends a new feature notice after the first review.
- Source id
- src-change
- Changed claim
- The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.
- Affected question id
- q-vendor
- Reopened question
- What can the feature read, and is it effectively off?
- Reviewer observation
- The new default and wider data access call for fresh records on settings and data use. The new notice does not prove the feature is on or that the stop control works.
- Actions reopened
- action-vendor
- action-it
- Baseline disposition
- Keep the first record. Add the new version and note what changed. Save both sets of evidence.
- Recommendation after change
- Keep the feature off. Get new data answers and approved proof of the settings. The example has settled which version applies. It still leaves open what staff can enter and how to check their answers.
- Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
- Result
- Vendor question and two related actions return to review. Prior record is retained; no approval carries forward.
Examiner-request mapping
- Request
- Inventory
- Where answer lives
- Listed-use summary and review boundary
- Limit
- Listed uses only
- Request
- Policies
- Where answer lives
- Source register and safe-use policy gap
- Limit
- Treatment proposed; institution accepts
- Request
- Governance
- Where answer lives
- Owned actions and the separate institution decision
- Limit
- Actual acceptance blank
- Request
- Risk assessment
- Where answer lives
- Tiering method and proposed tier reasons
- Limit
- Proposed CSBS-aligned tiers
- Request
- Vendor documents
- Where answer lives
- Source register and evidence assessments
- Limit
- Disclosure is not configuration inspection
- Request
- Monitoring
- Where answer lives
- Retained baseline and changes received history
- Limit
- Review updates you send. We do not monitor for changes.
- Request
- Risk tier worksheet
- Where answer lives
- Proposed risk tiers and reviewer status
- Limit
- Institution reviewer still required
Actual institution decision
- Decision
- Left blank
- Reviewer
- Left blank
- Owner
- Left blank
- Calendar date
- Left blank
Method review status
- Status
- Proposed illustration; qualified reviewer signoff not recorded
- Reviewer
- Left blank
- Date
- Left blank
- Selection note
- Use the existing supporting record four-factor method consistently. No new institutional or regulator acceptance is asserted.
Keep the matching current files
Download the blank six-column file.
Read the four-page buyer preview. Full printable supporting packet.
Executive summary CSV. Complete supporting records JSON.
Run the separate changed-source workpaper. Request a Vendor AI Decision Review.
Older downloads stay in place. The links above use the same edition. The example records no real reviewer signoff or institution decision.