Client and matter architecture
A structure where the matter is an addressable thing with a client, a practice area, a responsible attorney and a status — not a folder path someone typed differently last Tuesday.
SharePoint consulting for legal practices
A SharePoint consultant for law firms who starts with the matter, not the homepage
Your documents are already in Microsoft 365. What is missing is the shape a practice needs: a structure organised by client and matter rather than by folder, permission boundaries that hold a conflicts wall, retention and legal hold that outlive the person who set them, and a precedent library people reuse instead of hunting through a colleague’s old file. We configure that inside the tenant you already pay for — no custom code, no second document system. One written fixed fee, typical delivery in 2–4 weeks, 30 days of hypercare included.
Representative dashboard — sample data
What we configure
The six things a practice needs SharePoint to do
Every one of these is configuration of tools already inside your Microsoft 365 licences — scoped in writing before anything is built.
Ethical walls that are enforced
Conflicts and confidentiality boundaries built as permission and Information Barrier segments, so the wall holds when someone searches, shares a link or adds a member — not only when they remember it exists.
Retention, hold and closing
Retention labels that start the clock when a matter closes, legal hold that freezes what it must, and a closed-matter state that is a configured status rather than a promise to tidy up later.
Precedent and template libraries
A curated bank of forms, clauses and engagement letters with owners, review dates and content types, so associates start from the approved version instead of last year’s deal.
Search that respects the wall
Metadata-driven search that finds every document on a matter across libraries, while returning nothing a user is not entitled to see — because the boundary is enforced at the platform, not the query.
Client and co-counsel access
Named external access scoped to a single matter, with sign-in under the guest’s own identity and an audit trail — instead of a zipped folder emailed to whoever was on the thread.
How it works
Three steps from a shared drive to a matter-centric practice
- 1
Map how matters open, run and close
A free consultation covers your matter numbering, who opens a matter today, which walls exist and why, what your retention schedule already says, and where precedents actually live. We reply with a written scope, one fixed fee and a delivery date.
- 2
Build one practice group and test the boundary
We configure the architecture, metadata, labels and permission model for a single group first, then try to break the wall from the wrong account before anybody trusts it with live client files.
- 3
Roll out group by group, then retire the drive
Content moves in agreed waves with matter metadata applied on the way in, site owners and assistants are trained on opening and closing matters, and we stay on for 30 days of included hypercare.
Why a matter has to be a thing, not a folder path
Almost every firm that calls us has the same setup: a drive letter, a folder per client, a folder per matter inside it, and roughly four spellings of the same client name. It works until you ask it a question. Which matters is this associate currently touching? Which files belong to a matter that closed in 2019 and should now be destroyed? Which precedent is the approved one? A folder path cannot answer any of those, because a path is a location, not a record.
The fix is to make the matter an object the platform understands. In SharePoint that means matter attributes — client, matter number, practice area, responsible attorney, open or closed status, jurisdiction where it matters — held as managed metadata rather than typed into a folder name. Microsoft’s documentation on managed metadata and the term store (opens in new tab) covers the mechanism; the legal engineering is deciding which of your attributes belong in a shared term set, which come from your practice management system, and which are per-library columns that nobody outside one group ever sees.
Once the matter is an object, everything downstream becomes possible in a way it simply is not with folders. Retention can be applied to the matter. A wall can be drawn around the matter. Search can be filtered by responsible attorney across every library at once. And a closed matter can be moved to a read-only state without anyone dragging anything anywhere.
How a firm’s vocabulary maps onto the platform
This is the translation table we scope against. Your build takes the rows that match how the practice runs — a two-partner shop and a forty-lawyer firm with three offices land in different places on several of them — but the vocabulary is the same conversation every time.
| What the firm calls it | What it becomes in SharePoint | Why the folder version cannot do it |
|---|---|---|
| Client | A site, or a term in a shared client term set applied to every matter | Four spellings of one client name means four answers to “show me everything for this client” |
| Matter | A site, a library, or a document set carrying matter number, practice area, responsible attorney and status | A folder has no status, so nothing can act on the matter closing except a human remembering to |
| Practice group | A hub joining that group’s sites, plus an Information Barrier segment where a wall is required | Nested folders inherit permissions downwards, which is the opposite of what a wall needs |
| Ethical wall | Segment-based Information Barrier policies plus a site-level permission boundary with no inheritance | A folder-level deny entry is invisible in search results and forgotten the moment someone shares a link |
| Precedent bank | A central library with content types, document templates, an owner and a review date per item | “Copy the last one” propagates whatever error was in the last one, permanently |
| Closed matter | A status change that applies a retention label and drops the library to read-only for most roles | Nothing about a folder changes when a matter closes, so the retention clock never starts |
| Litigation hold | A hold that preserves matter content even where a retention policy would otherwise delete it | Preservation depends on nobody emptying a recycle bin, which is not a preservation strategy |
| Client or co-counsel access | Guest access enabled on one matter site only, under the guest’s own signed-in identity | A zipped folder over email has no revocation, no expiry and no record of who opened it |
Ethical walls: what actually enforces one
This is the part most SharePoint pages aimed at legal skate over, so here is the specific answer. The feature that enforces a conflicts wall across Microsoft 365 is Microsoft Purview Information Barriers (opens in new tab). You define segments of users — a practice group, a deal team, the people cleared on one side of a dispute — and policies that block communication and collaboration between incompatible segments across Teams, SharePoint and OneDrive. Microsoft’s own documentation uses the legal case as one of its worked examples: a lawyer’s data obtained from one client cannot be accessed by a lawyer at the same firm who represents a different client.
In SharePoint specifically, segments are associated with a site and the site takes an Information Barriers mode. Microsoft’s guidance on Information Barriers with SharePoint (opens in new tab) sets out the four modes — Open, Owner Moderated, Implicit and Explicit — and the consequences of each. In Explicit mode, only users whose segment matches the site can access or share it, and the “Anyone with the link” and company-wide link options are switched off entirely. Up to 100 compatible segments can be associated with one site, and adding a segment to a site moves it to Explicit mode automatically.
Three honest caveats belong on this page, because finding them out afterwards is expensive. Information Barriers supports two-way blocks only — a policy where group A may reach group B but not the reverse is not supported, so if your wall is genuinely one-directional it has to be modelled another way. Policy changes take roughly 24 hours to propagate, so a wall raised for a matter that opens this morning is not an instant operation and the process has to allow for that. And Information Barriers carries its own licensing requirement that not every firm’s current plan meets. We check all three during scoping, because for a smaller firm a well-drawn permission boundary with no inheritance, unique groups per matter and external sharing locked down is often the right answer, and a segment model is over-engineering.
Retention, legal hold and the day a matter closes
Most firms have a written record-retention schedule and almost no way to enforce it. The documents that should have been destroyed seven years ago are still on the drive because destroying them requires somebody to identify them, and nothing in a folder tree marks a matter as closed. Making closure a configured event is what changes that: when the matter status flips, a retention label is applied, the retention period starts from the close date rather than from whenever a file was last touched, and the library drops to read-only for everyone who does not need write access to a closed file.
Microsoft’s documentation on retention policies and retention labels (opens in new tab) covers the distinction that matters here: a policy applies broadly to a location, while a label attaches to the content itself and travels with it. Firms generally need both — a baseline policy across matter sites, and labels for the categories your schedule treats differently. Microsoft also advises using retention policies and labels rather than eDiscovery holds for long-term preservation, with holds reserved for a specific investigation or case. Preserved content lands in the Preservation Hold library, which is why a user deleting a file does not defeat a hold.
A necessary line: this is configuration work, not legal advice. We do not decide your retention periods, interpret your bar’s rules or opine on what your engagement letters require. Your firm decides what the schedule says and which matters go on hold; we build the tenant so those decisions are actually enforced, and we document what was configured so your risk partner can review it. Anyone selling you a compliance guarantee for a SharePoint build is selling something they cannot deliver.
Do you actually need iManage or NetDocuments?
Firms ask this before they ask anything else, and the honest answer is that it depends on which problems you have. Purpose-built legal document management systems such as iManage and NetDocuments are mature products designed around exactly this workflow, and for firms whose bottleneck is legal-specific behaviour out of the box, the subscription buys real things. Where SharePoint wins is when the actual problem is that matters live in folders, the firm already pays for Microsoft 365, and adding a second document system means a second place to search, a second thing to license and a second thing to administer.
We do not resell either product and we have no commission either way, so treat the table below as the questions to take to a demo rather than a verdict. Ask the vendor to demonstrate each row on your own matters; anything a salesperson will not show live is a row you should discount. Note that we cannot quote third-party pricing here, and neither should anyone else without your seat count in front of them.
| Question to settle first | Configured SharePoint | Purpose-built legal DMS |
|---|---|---|
| Filing email into the matter | Possible from Outlook and Teams, but the smooth version usually needs a third-party add-in on top | A core design goal of the category — verify the exact behaviour in a live demo on your own mailbox |
| Ethical walls | Information Barrier segments plus permission boundaries; two-way blocks only, and licence-dependent | Typically built in as a first-class feature — ask specifically about one-directional walls |
| Opening a new matter | Automated provisioning we build with Power Automate against your matter numbering | Usually native, often integrated with practice management — confirm it matches your numbering scheme |
| Where it already lives | Inside the Microsoft 365 tenant you pay for; one search index, one identity, one admin surface | A separate system to license, administer, back up and search alongside Microsoft 365 |
| Retention and hold | Purview retention labels, policies and holds across mail, documents and Teams content together | Native records management — check whether it also covers email and chat, or only documents |
| Who administers it day to day | Whoever already administers your tenant, using skills that transfer to everything else you run | A product-specific skill set, in-house or through the vendor’s partner channel |
| Cost shape | A one-time configuration project; the platform is already inside your existing licences | Ongoing per-user subscription plus implementation — get it quoted at your real seat count |
| Leaving later | Content stays in your tenant in native formats throughout | Ask about export format and cost before you sign, not at renewal |
The pattern we see most often is that firms under roughly fifty people, already committed to Microsoft 365, get most of what they wanted from configuration — and firms whose partners will not give up Outlook-native filing end up buying the DMS regardless of what a spreadsheet says. Both are defensible. What is not defensible is buying either one before anybody has written down how a matter opens and closes.
What the engagement covers
Three shapes cover most requests from firms. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your matter volume, your wall requirements and your current licence position first.
| Engagement | What is configured | Typical timeline | Fee |
|---|---|---|---|
| Matter structure | Client and matter architecture, matter metadata and term sets, library and document-set design, search refiners, and site-owner documentation for one practice group | About 2 weeks | Fixed fee — scoped after your free consultation |
| Matter structure with walls and retention | The above plus the permission model, Information Barrier segments where licensing supports them, retention labels tied to matter close, hold procedure, and a precedent library with content types | 2–3 weeks | Fixed fee — scoped after your free consultation |
| Firm-wide rollout | Multi-group rollout, automated matter provisioning, migration of agreed content off the file server with matter metadata applied in flight, external access for clients and co-counsel, and admin runbooks | 3–4 weeks | Fixed fee — scoped after your free consultation |
For a sense of the market you are buying in, independent SharePoint consultancies publish their rates: SharePoint Maven, a solo consultancy run by a Microsoft MVP with a dedicated legal practice line, lists $350/hour hourly consulting and a $2,400–$4,200 fixed-fee document management engagement delivered in 3–4 weeks (opens in new tab), while general US Microsoft consultant rates commonly sit in the $100–$250 per hour band. We publish no price list, because the number depends entirely on the scope agreed after your consultation — but you should be able to place any quote you receive against those figures. The wider drivers behind a SharePoint fee are broken down on our SharePoint intranet cost page.
Who this fits
Small and mid-sized US firms — typically five to a hundred and fifty people — that already pay for Microsoft 365 and still keep client files on a server share or a tangle of OneDrive folders. The trigger is usually one of four things: a conflicts situation that made someone ask who can actually see what, a malpractice insurer or client audit asking about retention, a server refresh quote, or an incoming partner who used a real DMS at their last firm and will not go back to a drive letter. It is a poor fit for firms that have not decided how matters are numbered, because structure built on an undecided convention has to be rebuilt.
This page is the legal-shaped version of our wider SharePoint intranet and document management consulting, which covers intranets, governance and migration across any industry — same engineering standards, different vocabulary. Provider organizations running the same exercise on policy manuals, credentialing files and accreditation evidence get our SharePoint consulting for healthcare organizations instead, and contractors running it on drawing sets, RFIs, submittals and closeout packages get our SharePoint consultant for construction companies engagement. If the client files are still on a file server, the sequencing matters and our file server to SharePoint migration playbook explains why structure gets designed before anything moves. Where the firm exchanges documents with clients and opposing counsel through Citrix ShareFile, the portals, FileDrop links and per-matter folder templates need rebuilding before the content follows — that is the work our ShareFile to SharePoint migration services scope. Firms weighing Microsoft 365 Copilot should read how governance decides whether a Copilot rollout is safe first, since an assistant that summarises across everything a user can reach is a permission problem before it is an AI problem. And opening a matter — the intake request, conflict-check clearance, the engagement letter, provisioning the site and notifying the team — is a process rather than a checklist taped to a monitor, which is what our Power Automate consulting for law firms engagement automates alongside prebill and billing-narrative review; the generic version of that service is our approval and provisioning workflow consulting. We work with firms in all US states remotely from our Orange County, CA base.
Related services
What firms usually scope alongside this
SharePoint Consulting
The wider fixed-fee service: intranets, document management, migration and governance across any industry.
Microsoft Copilot Consulting
Copilot reaches everything a user can already open — which makes a governed matter structure the prerequisite, not the bonus.
Power Automate for Law Firms
The process half of a legal build: matter intake, conflict-check routing, engagement letters and prebill review running behind the structure.
Further reading
Guides for the decisions behind this build
Hand-written guides from our article library.
File server to SharePoint
The step-by-step playbook for moving client files off a server share without carrying the mess across.
Governance before Copilot
Why permissions and oversharing decide whether an AI rollout is safe in a confidentiality-bound practice.
How fixed fee works
Free consultation, written scope, one price, 2–4 week delivery, 30 days of hypercare.
FAQ
Questions firms ask before scoping
It depends on how much of the legal-specific behavior you need out of the box. If Outlook email filing, document numbering and profile-driven search are non-negotiable, a purpose-built legal DMS earns its subscription. If the real problem is that matters live in folders, SharePoint you already pay for can be configured to fix it.
Microsoft Purview Information Barriers is the feature that enforces them. You define segments, such as practice groups or deal teams, and policies that block collaboration between them across Teams, SharePoint and OneDrive. Segments are then associated with matter sites. Note that Information Barriers supports two-way blocks only, not one-way restrictions.
Usually not. A site per matter gives the cleanest permission boundary but creates a lot of sites to govern. Most firms we scope end up with a site per client or practice group, and a library or document set per matter carrying matter metadata. Volume and wall requirements decide which.
Closing is a configuration step, not a filing habit. A retention label is applied to the matter, the library goes read-only for most roles, and the retention clock starts from the close date. Your record-retention schedule decides the periods; we configure Purview to enforce what your firm has already decided.
Yes, when the matter is its own site or its own permission boundary. External sharing is set per site, so one matter site can allow named guests while the rest of the tenant stays closed. Guests sign in with their own identity, and every access is recorded in the audit log.
No custom code. Everything is configuration of SharePoint, Purview and the Microsoft 365 tools your firm already licenses, so nothing depends on us to keep running. The sites, the metadata, the labels and the documentation stay in your tenant, and you get 30 days of hypercare after handover.
Book a free consultation
Get more from the Microsoft tools you already pay for
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.