Law firms routinely ask clients for documents that would be uncomfortable to lose control of: passports, driving licences, proof of address, bank statements, corporate ownership records, trust documents, source-of-funds material, medical records, contracts, correspondence, and evidence for a matter.
Those files are not ordinary attachments. They identify people, reveal financial position, support professional judgments, and may sit inside regulated or confidential workflows. A firm may need them for client onboarding, conflict and risk review, AML-oriented processes, matter preparation, litigation support, conveyancing, private client work, or corporate transactions.
This article is operational guidance, not legal advice. It does not define when a firm must perform particular checks, what evidence is sufficient, or how long records must be retained. Those decisions depend on the firm’s obligations, jurisdiction, matter type, client risk profile, regulator expectations, and internal policies. The narrower point is this: once a firm decides it needs a client identity document, the method of collection and custody should match the sensitivity of the record.
Identity documents need matter context
Client identity documents should never be treated as isolated files. A passport submitted for onboarding is different from a passport submitted as evidence in a dispute. A bank statement used in source-of-funds review carries different handling expectations from a signed engagement letter. A corporate ownership chart may be relevant to client due diligence, transaction structuring, or conflict assessment depending on the matter.
That context matters because it explains why the document was requested, who needed to review it, what status it reached, and what should happen after the immediate task is complete. If the context lives only in an email thread, the firm may have to reconstruct the record later from inboxes, file notes, matter folders, and staff recollection.
A stronger approach starts with a defined request. The firm records which client or contact is being asked, which matter or onboarding workflow the request supports, what document is required, and what purpose the document serves. The client then receives a controlled route for submission rather than an instruction to attach sensitive files to a reply.
For a wider discussion of this operating model, see secure client document intake for law firms.
Why email is a poor custody layer
Email is useful for correspondence. It is weak for custody.
An identity document sent by email can sit in the client’s sent folder, the solicitor’s inbox, a shared mailbox, a mobile client, an archive, a local download folder, and every forwarded thread. The firm may save the document into a matter system or document management folder, but the earlier copies still exist across communication infrastructure.
Forwarding creates another problem. Legal work often requires escalation or review, so the issue is not that another colleague may need to inspect a document. The issue is that email forwarding expands access without creating a document-level custody record. The firm may know a message was forwarded. It may not have a clean record of who accessed the file, why they had access, whether a review decision was made, or whether the forwarded copy was later restricted or removed.
This is why email fails sensitive document collection. It can move the file, but it does not govern the request, submission, review, access history, retention, and lifecycle state around the file.
What governed collection should provide
Governed client identity document collection is the controlled request, receipt, access, audit, retention, and lifecycle management of sensitive client records.
The workflow should begin before the upload. A staff member should be able to define the request and connect it to the client, matter, onboarding process, or review purpose. The client should submit through a controlled path that makes the request feel legitimate and limited. The firm should receive the document into encrypted custody rather than into an ordinary mailbox.
After receipt, access should be scoped. Not every person who can view a matter folder needs to see every identity document. A compliance reviewer may need access to source-of-funds material. A fee earner may need to see whether a client due diligence step is complete. A broader team may only need status, not the underlying record.
Review state should also be explicit. A document may be received, incomplete, rejected, replaced, accepted, expired, retained, restricted, or removed from active use. If those states are tracked through informal notes and inbox labels, the firm has an operational gap. A governed workflow records the state as part of the document history.
This is the same category problem described in client document intake without email attachments: intake is not complete when the file arrives. That is when custody begins.
Audit trails should follow the document
For identity documents, an audit trail should be more than a mailbox search. It should connect each event to the document, requester, submitter, workflow, reviewer, access decision, and lifecycle state.
At minimum, the record should show when the request was issued, who was invited to submit, when the document was uploaded, which workflow received it, who accessed it, what review action occurred, and what retention or closure action followed. The audit trail should make the handling explainable without requiring staff to inspect multiple inboxes and folder histories.
This matters because client identity documents often support decisions that may later be questioned. A firm may need to show how a document entered the workflow, who reviewed it, whether a replacement was requested, or why access was restricted. Those answers should not depend on memory or scattered correspondence.
For a deeper treatment, see audit trails in document collection workflows.
Retention should be policy-led
Retention is one of the hardest parts of inbox-led identity document handling. A firm may have a policy for keeping client due diligence records, matter files, correspondence, or evidence. But if the same document exists across forwarded emails, local downloads, shared mailboxes, and unofficial folders, policy is harder to apply and harder to evidence.
Governed custody does not decide the firm’s retention obligations. It gives the firm a better operating surface for carrying out the retention decisions it has made. A workflow can distinguish between active review, matter use, restricted access, retained metadata, archived records, and deletion or removal where appropriate.
That distinction matters for privacy and governance. Keeping records longer than needed can increase exposure. Removing records without a clear process can create its own risk. A policy-led workflow gives compliance, legal, and operations teams a more consistent way to manage lifecycle decisions.
CVOR’s security and governance posture is built around this layered model: invite-only access, MFA, per-tenant authorization, application-layer encryption, immutable audit logging, retention support, and lifecycle controls.
Client experience is part of trust
Clients notice how a firm asks for sensitive information. A request to email a passport, bank statement, or proof of address may feel ordinary because people are used to it. It can also feel careless, especially when the client understands the sensitivity of what they are sending.
A controlled upload path sends a different signal. It tells the client that the firm has a defined process, that the document is being requested for a specific purpose, and that the file will not simply become another attachment in a thread. That does not remove the need for clear engagement terms, privacy notices, professional judgment, or appropriate client communication. It supports them with a stronger handling route.
For law firms, this is not only a technology issue. It is an operational credibility issue. The way a firm collects identity documents should be consistent with the care it claims to apply to client confidentiality, regulated work, and matter governance.
Practical evaluation questions
Firms reviewing their current process can start with direct questions.
Can staff see exactly what identity document was requested and why? Can the request be tied to the right client, matter, or onboarding process? Can the firm tell whether the document has been submitted, accepted, rejected, replaced, or expired? Can access be limited to the people who need the underlying file? Can the audit trail show request, submission, access, review, and lifecycle events? Can retention be applied without searching old emails and forwarded copies?
If the answer depends on inbox discipline, shared mailbox searches, staff memory, or manual spreadsheets, the firm is using informal tools as a custody system.
The better operating model
Law firms do not need more places to store documents. They need a governed way to request, receive, review, restrict, audit, retain, and retire sensitive client records.
That model should sit alongside matter management and professional workflows. It should not replace legal judgment, compliance ownership, or the firm’s own policies. It should provide a controlled document custody layer for the records those processes depend on.
CVOR’s platform is designed for governed document collection and custody. Law firms can issue controlled document requests, receive client submissions through a secure path, scope access, maintain audit trails, support retention policy, and reduce reliance on inbox-led handling for identity and matter documents.
CVOR governs document workflows for compliance-sensitive organizations.
Explore the platform →Frequently asked questions
What client identity documents do law firms commonly handle?
Law firms often handle passports, driving licences, proof of address, company ownership records, source-of-funds material, and matter documents as part of onboarding, client due diligence, or matter preparation.
Should law firms collect identity documents by email?
Email may be familiar, but it is weak as a custody layer because attachments can be forwarded, copied, downloaded, retained, and separated from the request, review status, and retention process.
What controls should a client identity document workflow include?
A governed workflow should define the request, verify the submitter path, restrict access, record audit events, support review status, connect documents to the matter, and apply retention policy.
Is this article legal advice for AML or SRA compliance?
No. This article is operational guidance for document handling. Law firms should apply their own professional, regulatory, AML, privacy, and retention obligations with advice from qualified specialists where needed.