Problem pattern · Pattern only

Reuse client-work knowledge across an accounting firm

A design pattern for retaining, anonymizing, and reusing reports and client communications without treating confidential material as public data.

Operational context

A firm may understand the operational pain but still need help defining the safe experience: what is retained, what must be anonymized, who may retrieve it, and when a human must review an answer.

Target experience

Authorized staff can find prior knowledge by situation, see its provenance and access boundary, and draft a response without exposing another client's confidential information.

Questions to clarify

Confidentiality, legal duties, and data classification
Tenant, office, team, and role boundaries
Anonymization and human-review policy
Source provenance, retention, deletion, and incident response