WORKSHEET / DATA + ACTION

Define what the AI may touch.

Map one workflow before connecting a tool. Give the data owner a concrete scope to accept, narrow or reject. Leave unverified settings and approvals visible.

Use roles and field names, not actual records or secrets. This is a planning worksheet, not a security certification or access approval. Entries are not saved on this site; copy before closing.

01 Workflow and permitted action

Name one task. Specify draft-only, execution after human approval, or an explicitly bounded automatic action.

02 Minimum data and source

List field names, source systems and business purpose. Do not paste records, credentials or customer details.

03 Who and what may access it

Name user roles, tool identity and scope. Identify the person who can approve access.

04 Destination and retention evidence

Record the approved environment and evidence for storage, retention, deletion and training-use settings. Unknown is a valid answer.

05 Excluded data and actions

State what must never enter this workflow and which writes, exports or sends are prohibited.

06 Human review and exceptions

Who checks outputs before they leave the boundary? What happens with missing, stale or conflicting inputs?

07 Monitoring and revocation

Who reviews activity, where is the audit trail, and how can access or the workflow be stopped?

08 Decision owner and review date

Name the security/data owner, remaining questions and date for review. This worksheet cannot grant permission.

0 of 8 sections drafted. Completion is not approval.

Define what the AI may touch.

Your review draft