Industry
Can the copilot see the matter it isn't supposed to see?
A firm's assistant searches client documents, drafts work product and plugs into email or the document management system. We review who can reach each matter, what leaves the firm, and who approves sending, sharing or changing a record. Separately, counsel can engage us to review technical claims and system materials for a dispute, a diligence question or post-incident work.
Included in the work
Matter permissions, document flows and action controls.
- Client/matter and staff-role access matrix, including firm-supplied ethical-wall rules
- Data-flow map covering retrieval, context, citations, exports, logs and caches
- Vendor terms and configuration questions with document dates and unresolved assumptions
- Findings register with reproduction conditions, technical impact and remediation owners
- Rollout decision memo with permitted use, unresolved risks and retest conditions
01
Start with one workflow the firm owns
Pick one pilot: an associate summarizing matter documents, a knowledge team searching approved precedents, or an assistant drafting an email for attorney review. Write down the intended user, client, matter, sources and allowed actions before anyone looks at the vendor.
- Translate the firm’s approved ethical-wall and matter-access rules into technical test inputs. Membership in the same firm does not by itself authorize access to every matter.
- Separate attorneys, paralegals, contractors, knowledge staff, IT administrators and connector service identities. Include role changes and departed staff.
- Use invented matters and redacted configuration for initial scoping. Agree on authorized systems, test accounts, data handling and stop conditions before accessing sensitive materials.
02
Follow a document beyond the search result
- Check source permissions at retrieval and before context assembly, including revoked access and cached candidates.
- Inspect citation titles, snippets and source links as well as answer text. Test direct export, shared conversations and generated files for the same matter boundary.
- Map answer caches, embeddings, conversation memory, diagnostic logs and backups. Record deletion and retention behavior separately for each store.
- Review document-management, email and storage connectors: delegated versus service access, token scope, administrators, external sharing and revocation.
03
Review the vendor and the action boundary
- Obtain the actual service agreement, data-use and training terms, retention settings, deletion process and subprocessor information for the selected product tier. Record where contractual terms and available configuration differ.
- Identify whether prompts, uploaded files, retrieved passages and outputs receive different treatment. Unanswered questions become rollout conditions.
- Require an accountable person to review citations and substantive output before use. Define which actions need approval, including sending, external sharing and changes to matter records.
- Bind technical approval to the intended action, recipient, content and current permissions. Include cancellation, changed drafts and failed or repeated requests in the test plan.
04
Where the professional guidance meets the technical review
ABA Formal Opinion 512 (July 29, 2024) covers competence, confidentiality, communication and supervision when lawyers use generative AI, and it supports asking concrete questions about what a tool can and can't do. The technical review supplies the system-specific answers. The firm's counsel decides what the professional obligations, client communication and consent require.
05
Counsel and expert support is a separate engagement
Counsel handling a dispute, a diligence question or a post-incident assessment may need an independent analysis of technical materials. That work has its own question, its own material request list, its own conflicts and scope review, and ends in a counsel-facing technical memo. It isn't the same job as approving the firm's internal AI pilot.
06
Prepare for the first discussion
- Send the proposed workflow, product and tier, decision deadline, system owner and a redacted architecture sketch. Keep client files and credentials out of the initial contact form.
- Provide a source inventory, role/matter matrix, connector scopes, applicable vendor documents and known access exceptions through the agreed review channel.
- Prioritize boundary failures before expanding the pilot. Each finding names an owner, acceptance test and review point; remediation implementation and retest scope are agreed separately.
Limits
Scope and limitations.
- This is a scoped engineering service. It isn't legal advice, it doesn't determine privilege, and it doesn't certify compliance or guarantee confidentiality.
- Reading documentation can't establish runtime isolation. Configurations we couldn't see, systems we couldn't reach and tests we didn't run are all recorded as limits.
Next step