Solutions · Legal & advisory # Documents that belong with the matter they serve. For legal and advisory teams, DocuPrivé is designed to keep client documents inside the matter: requested from the right person with clear instructions, seen by the matter team for as long as the work needs, held if a dispute arises, and decided on at closing. Issuing a Request to one verified person for a defined period exists in our development build; the rest is designed and not yet built. Roles in this example a matter partner an assistant on the matter team the client's external adviser ## Who it is for Law firms, in-house legal teams and advisory practices that collect documents from clients and from the other professionals who act for them. The people who ask for documents, the people who work on them, and the person accountable for the matter when it closes. ## The recurring problem Matter documents arrive by email from several directions: the client, the client's other advisers, counterparties. Each copy lands in a different inbox, and it is rarely clear later who still holds what. At closing, the questions are always the same. What did we receive, and from whom? Who on the team could see it? How long must we keep it, and who decides when it goes? An example workflow ## How this work is designed to run, step by step. 2 of 10 steps exist in our development build; the others are designed, not yet built. This example shows how the stages fit together; the names and steps are generic. - 01 Request Assistant → external adviser **Ask for the identity and source-of-funds documents.** The assistant issues a Request from the matter's Room to the external adviser, with instructions and an exact date and time when access ends. Once issued, a Request's details are fixed. Issue, identity verification, current access and email notification are each recorded separately. In our development build - 02 Control External adviser **The adviser opens only that Request.** Recipient access starts with a verified receiving email address. The adviser sees who asked, what is needed and when access ends, and does not join the firm. In our development build, for Request details - 03 Receive External adviser → matter **Documents arrive against the Request.** Documents arrive in the context of the Request they answer, not a general inbox. Designed, not yet built - 04 Classify Matter team **Recognized for how they should be handled.** Material is recognized for what it is and how it should be handled. Designed, not yet built - 05 Use Matter partner, assistant **The matter team works with what the task needs.** People work with the documents a task needs, and no more. Designed, not yet built - 06 Retain Firm policy **Kept for the period the matter policy sets.** Material is kept for a period set by policy, not left by accident. Designed, not yet built - 07 Review Matter partner **Looked at again when the matter closes.** Before anything ends, the right people can look again. Designed, not yet built - 08 Hold Accountable person **Held if a dispute arises.** While a hold applies, material is not brought to an end, whatever stage it is in. Designed, not yet built - 09 Dispose Matter partner **Brought to a considered end.** When the time comes, material is brought to a considered end. Designed, not yet built - 10 Evidence Throughout **A record of each decision.** A proportionate record of what was decided, kept with privacy in mind, from the first Request to the end. Designed, not yet built In our development build ## What the other side sees today. When a Request is issued to someone outside the firm, this is their view: only that Request, who asked, what is needed and when access ends. What exists today - Issuing a Request from a Room to one named person, with instructions and an exact end to access. - Verified access to the Request details for that person, revoking access and resending the notification. - Receiving, classifying and keeping documents, holds, disposal and evidence are designed, not yet built. The recipient sees only this request: who asked, what is needed and when access ends. They do not join the requesting organisation. ## Related - [A file or a link? What changes when you share a copy instead of a pointer.](https://docuprive.com/resources/file-vs-external-link/) - [Request & Receive How a Request works today.](https://docuprive.com/platform/request-receive/) - [Accounting & audit An example yearly engagement.](https://docuprive.com/solutions/accounting-audit/) ## Follow the build as each stage arrives. [Get product updates](https://docuprive.com/updates/) [Contact](https://docuprive.com/contact/) [All use cases](https://docuprive.com/solutions/)