Resolve delivery and data questions in writing.
The public site describes how an inquiry is handled. Project commitments about access, confidentiality, delivery roles, security, compliance, continuity, and AI tooling belong in a reviewed written scope.
[02]
§ Before a commitment
Questions that shape the engagement.
- Confidentiality and access
- Before sensitive materials are exchanged, discuss the access boundary, confidentiality terms, named delivery roles, and any approval process that applies to the proposed work.
- Data and systems
- A discovery scope identifies the systems, data categories, retention expectations, and technical controls that must be evaluated. Do not assume that a public page establishes a data-processing commitment.
- Security and compliance
- Regulated, security-sensitive, or contractual requirements are assessed for the specific engagement. The written scope should record any required controls, evidence, insurance, continuity, or escalation terms.
- AI-assisted work
- If an engagement involves AI tools or client material, agree the permitted tools, data boundary, review method, and retention requirements before using them for that work.
[03]
§ Public inquiry data
Start with only what is needed.
Initial inquiries are for the workflow, systems, constraints, and decision context. Avoid secrets, health information, payment data, or other sensitive materials until a secure, agreed workflow is in place.
Read inquiry-data details →