Map the information before moving it.
List the fields the workflow receives, derives, stores and sends onward. Include the website, CRM, email or messaging system, model provider, logs and staff tools. Record why each field is necessary for the task.
A process diagram should distinguish public business information from personal, confidential or sensitive information. Start with the minimum data the pilot needs, using representative test information where practical.
Define access and purpose.
Decide which people and services may access each information set, and which actions they may perform. A staff-facing knowledge assistant should not expose every internal document to every employee merely because it can search across files.
Document the purpose for collecting enquiry information and how people can raise a question about it. Legal obligations vary with the data, jurisdiction and service; this planning guide is not a substitute for the relevant professional review.
- Purpose and necessity for each field.
- Authorized users, services and actions.
- Appropriate separation of test and production data.
- An owner for access changes and enquiries.
Review the selected providers and account settings.
Confirm where processing occurs, which subprocessors are involved and what the applicable retention and training terms say. Check the actual service, account and contract rather than relying on a general statement about a technology category.
Include operational records such as transcripts, prompts, diagnostic logs and failed delivery payloads in the review. Deleting a CRM record alone may not address every copy created by the workflow.
Maintain the decisions after launch.
Agree retention, deletion, incident contact and access-review responsibilities before release. Revisit the information map when the provider, model, integration or task changes. Keep production settings consistent with the public policy and customer commitments.
The NIST Privacy Framework is a general resource for privacy risk management. Use it as a planning reference alongside the obligations and agreements that apply to your specific deployment, not as proof of certification or legal compliance.
General workflow guidance. Product availability, provider requirements and implementation scope are confirmed for each project.

