Design a law firm’s document management around the matter, the people authorised to work on it and the approved retention decision. Write those three rules separately, then test them together using sample files. A useful system lets staff find the right version while giving the firm a traceable basis for keeping or disposing of it.
Start with one matter type and the documents that actually pass through it. Ask who creates the first draft, who reviews it, who issues the final version and who closes the matter. Put responsibility beside each step. This produces a practical requirements brief before anyone starts configuring folders, labels or automation.
For a firm considering Microsoft 365, Microsoft Purview provides concrete retention and records-management examples. The documentation discussed here was checked on 24 October 2026. Use it to distinguish available product concepts from the firm’s own decisions about its matters. Put the applicable retention schedule and its authorising source into the brief before choosing a period in the software.
How should matter access and retention fit together?
Treat the access design as a named set of permissions that the firm approves. For each role, specify the intended ability to discover, read, edit, share and administer a matter. Write the expected result in ordinary language: “The reviewer can open Matter A’s draft; the unrelated team member cannot find it in search.” These are proposed acceptance criteria for your chosen environment, to be tested with separate accounts.
Retention answers a different operational question: what should happen to content over its lifecycle? Microsoft Purview supports retaining content for a specified period or forever. It also supports deleting content after a specified period. A third supported outcome retains content for a specified period and then deletes it. Microsoft’s retention overview describes these options; choosing between them requires an approved rule for the document category.
Avoid turning a matter’s closing date into an unexplained deletion instruction. Record the event that starts the period, the evidence of that event, the person who confirms it and the action due at the end. If the firm has not yet approved a category’s rule, give it a visible decision owner and review date in the project register. This lets the implementation proceed with a clearly identified unresolved decision.
Microsoft distinguishes container-level and item-level settings. Retention policies assign the same settings at site or mailbox level. Retention labels assign settings at item level, including documents and emails. Those distinctions are documented in the same overview. They help frame the design discussion when a matter contains several kinds of document with different approved handling rules.
Use the following proposed matrix during discovery. “Approved schedule” refers to the firm’s recorded decision, with its supporting authority, rather than a period supplied by this article.
| Matter component | Access decision to approve | Retention decision to record | Evidence to collect |
|---|---|---|---|
| Working draft | Named drafting and review roles | Category and approved schedule | Role test and saved version |
| Issued document | Named readers and change authority | Whether a record label is appropriate | Issued copy and label decision |
| Incoming correspondence | Matter team and filing responsibility | Applicable correspondence category | Filing sample and classification |
| Closed matter | Retrieval owner and access review | Start event and end action | Closure approval and event evidence |
| Exception | Named decision maker | Which instruction governs this item | Written instruction and review date |
Make the access review concrete. Include a person joining the matter, a person leaving it and an administrator handling a support request. Decide who can approve changes and where that approval will be recorded. For external sharing, specify the exact intended recipient and document rather than writing “client access” as an unrestricted requirement.
What do retention labels and records add?
Microsoft’s documentation says retention-label settings travel with content moved within the Microsoft 365 tenant. This makes movement an important test case when item-level classification is part of the design. Move a sample between the locations involved in the proposed workflow, then inspect its label and behaviour. Keep a copy of the expected result beside the observed result.
Labels can start a retention period from an event. A matter-closure workflow can therefore include a design question about whether a defined closure event should drive retention, subject to the actual configuration chosen. The proposed worksheet should identify who supplies the event and how corrections will be handled. Naming an event in a requirements document does not itself create a working event-based configuration.
Labels can support disposition review before permanent deletion. That capability is useful to investigate where the approved process requires a human decision at the end of a period. Define the reviewer, the material they need to see and what should happen if they defer. Keep this end-of-life process in the same brief as filing and retrieval, so closure does not become an abandoned administrative step.
Microsoft’s records-management overview adds further distinctions. A Purview file plan can bring an existing retention plan into Microsoft 365 or support building a new one. Use the firm’s approved categories as the starting input to that plan, with readable names that the people filing documents can recognise.
Declaring an item a record places restrictions on the actions allowed or blocked. Microsoft describes different behaviour for standard labels, records and regulatory records, with workload-specific qualifications. Choose a representative file and demonstrate the intended edit, rename, move and deletion behaviour before selecting a label approach for the wider matter collection.
Records management supports exporting information about disposed items. Consider where the firm wants that information stored, who may retrieve it and how it will be linked back to the approved disposal decision. The export is a product capability; the naming, ownership and reconciliation of the firm’s disposal register remain design decisions to settle during implementation.
An original matter-boundary exercise
Use a hypothetical test set with Matter A and Matter B, three test accounts and four harmless sample documents. The accounts represent a Matter A drafter, a Matter B reviewer and an administrator. The files represent a draft, an issued document, incoming correspondence and a closure note. Give every file an obvious test identifier and keep it separate from live matter material.
Create an expectation sheet before configuring anything. For each account and file, record whether search discovery, opening, editing and sharing should succeed. Add the intended label, the retention start basis and the person authorised to approve any change. The firm’s designated owner should resolve ambiguous entries before the demonstration starts.
Run the access cases first, then repeat the relevant cases after applying the proposed retention and record settings. Record observed behaviour, account used, timestamp and evidence location. If an issued sample remains editable when the approved design expects it to be protected, investigate the actual label, record state and workload behaviour against Microsoft’s documentation. Keep the unresolved case open with an owner.
Then simulate closure by following the agreed test procedure for the chosen configuration. Check how staff would retrieve the matter, identify the governing decision and route a disposal review. For long periods, demonstrate the configuration and review process using an isolated test arrangement rather than representing a future production outcome as already observed.
During handover, ask a staff member to locate an issued version and explain why it is retained. Ask the administrator to show the access approval and the rule that governs disposal. Those short demonstrations connect the system’s settings to the people who will maintain them.
Use the broader document management guide alongside business systems and your web development brief. To scope a matter-based implementation and its acceptance exercises, get started with the requirements.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.