Legal Document Management: How In-House Teams Organize Group Documents

Key Takeaways

A legal document management system is the set of structure, rules and tooling that lets a legal department store, find, control and retire its documents, from corporate records to matter files. In a group with several entities and jurisdictions, the hard part is not storage. It is deciding which entity owns each record, who can open it and how long it stays. The next step is to inventory the records of one entity, with owner, jurisdiction, access roles and retention rule, before building any folder tree.

Consider a group headquartered in Europe with subsidiaries in several countries. An auditor, a regulator or a board member asks for the signed minutes of one subsidiary’s last board meeting. The draft sits in an email thread, a later version lives on a local drive, and the signed scan is with someone in the local office. A legal document management system exists to make that request routine rather than a search.

This article explains what such a system holds for an in-house legal team and how to organize it across entities. It covers folder logic, naming, versions, access by entity and retention, and ends with a practical first step for a group.

A legal document management system is the combination of structure, rules and tooling that lets a legal department store, find, control and retire its documents. It covers more than storage: each document sits under an owner, an entity, an access rule and a retention rule. For an in-house team, contracts, corporate records, policies, filings, advice and matter files each need the treatment their purpose requires.

These document types behave differently. Corporate records such as formation documents, board and shareholder minutes, registers and filings are tied to a legal entity and often to the law of the place where it was formed. Contracts are tied to a counterparty and a lifecycle, which a contract lifecycle management (CLM) tool or a contract repository is built to handle. Matter files follow the matter, including the advice, correspondence and decisions around it. One shared drive cannot serve all three without explicit rules.

In most groups, the actual system is a stack: Outlook for requests, Teams for conversation, SharePoint or shared drives for files, Excel for registers, Word for drafts and human memory for the rest. Each tool works on its own, but a collection of tools is not an operating model. Every subsidiary develops its own naming habits, its own folders and its own idea of which copy is final. The issue isn’t the quality of the team. It’s that the rules for each record live in people’s heads.

How do you organize group documents around each legal entity?

Start with the entity, then group its records by function. The entity list comes first because every later rule, from access to retention, depends on which entity holds a record and under which jurisdiction.

Entity first, then record function

Most shared drives end up with a folder called Misc. A structure that starts with the entity avoids it. Under each entity, group records by function, such as formation, governance actions, policies, filings and recurring corporate records. A function-first tree mixes affiliates together, so settle the entity list before creating any folder.

Recording legal name, jurisdiction and entity ID

Take an example: a group has two subsidiaries whose names differ by a single word, one formed in one country and one in another. Without a clear identifier, minutes and filings drift into the wrong folder within a year. Record every entity in a directory or metadata field with these items:

  • Its full legal name, written exactly as it appears in the formation documents.
  • Its jurisdiction, meaning the country or state where it was formed.
  • A stable entity ID, used in every folder and file name.

This directory becomes the reference for the rest of the system. When a new entity joins the group, it receives the same set of categories, the same roles and the same naming pattern, instead of a structure invented locally.

Folder structure, naming and versions: what a consistent system looks like

Folder levels and naming rules

Keep the tree to three or four levels: entity, then record category, then year or meeting date. Anything deeper is hard to browse, and people stop using it. Name each folder after what it holds, such as “Board minutes” or “Registers and filings”. Skip “Other” and “Miscellaneous”, because catch-all folders fill up fast and nobody remembers what belongs in them.

Naming pattern for entity records

Use the same order in every filename, so a plain alphabetical sort groups records by entity, then type, then date:

  • Start with the entity ID, then the record type, such as “board-minutes”.
  • Add the date or period as YYYY-MM-DD, so records sort in date order.
  • End with the status or version, such as “draft-2” or “record-copy”.

For example, ENT04_board-minutes_2025-03-12_record-copy tells any member of the team what the file is, which entity it belongs to and whether it is the approved copy.

Version labels and drafts

Label versions v1, v2, v3. Words like “new” or “update” tell nobody anything a year later. Mark drafts as drafts, and mark the approved or filed copy as the record copy with its final date. Each approved policy, signed-off set of minutes or filed document should have exactly one record copy.

Do three versions of the same board minutes exist in your group? Map one real record from creation to retention with the Alf team, entity by entity.

Talk to an expert

Who can open which entity’s records?

Access should follow the role a person holds and the entity they work for, not the convenience of an open drive. Give each role only the access its work needs, which is the least-privilege principle.

Permissions by entity and record category

Many teams open the whole legal drive to everyone because it is quicker. That is how a junior analyst ends up reading board minutes of an entity they never work on. Split access twice, by entity first and then by record category, so board minutes stay apart from routine filings. A local legal counsel then sees their own entity’s records, while group-level roles see across entities according to their responsibilities.

Roles that match the work

Give access to roles, not names. A corporate secretary does a defined job, and so does an entity administrator. When someone leaves, the role stays and the new holder takes it over, with no knowledge lost in the handover.

Classification matters too. Rules on the confidentiality of communications with in-house lawyers vary by country. In competition investigations by the European Commission, the Court of Justice held in Akzo Nobel v Commission (C-550/07 P, 2010) that professional secrecy does not cover communications with in-house lawyers. Knowing which documents are advice from in-house counsel and which come from outside counsel, and where each is stored, is therefore a design decision, not an afterthought.

Shareholders, auditors and regulators may also hold statutory rights to inspect some records, depending on the governing law. Name the holder of each record in the directory now, so a request can be routed on the day it arrives.

What to record for each document type

A short inventory sheet per entity is the foundation of the whole system. For each record category, capture:

  • The owner, as a role rather than a person.
  • The entity and its jurisdiction.
  • The roles that can open it.
  • The status and version that identify the record copy.
  • The retention rule and the starting point it runs from.

How long do you keep these records, and when do you delete them?

Retention is set by record type and by jurisdiction, not by one rule for every corporate document. The correct period depends on the governing law and, for some records, on the sector the entity operates in.

Retention categories by record type

Each rule needs a starting point, such as the creation date or a defined event, plus a retention period. Keeping everything for a long fixed period just in case is a habit to drop, because it keeps documents that no one can justify and makes it harder to find the ones that matter. Confirm each period with local counsel for the entity concerned, and record the result in the inventory.

Holds and avoiding automatic deletion

Before deleting anything, pause automatic deletion and check two things for each record: its retention rule and any preservation obligation, such as a legal hold. A legal hold is a duty to preserve documents relevant to a dispute, investigation or request, and its scope and triggers depend on the jurisdiction. A federal or public-sector retention schedule from another country is not a default for a private group, so build the schedule from the law that applies to each entity.

CheckRetention rulePreservation obligation
What it answersHow long a record is keptWhether a record must be kept longer
Who defines itThe legal department, with records owners and local counselCounsel, based on a dispute, investigation or request
Before any deletionConfirm the rule for that record type and jurisdictionConfirm that no hold applies to the record

Why do board minutes, policies and filings need controlled versions?

Because they are the records a group has to produce when someone questions a decision, and a draft produced by mistake is a problem. Minutes and filings look like paperwork you can file and forget, but they carry the evidence of who decided what and when.

Keep one record copy per approved policy, signed-off set of minutes or filed document, and mark drafts clearly. Tie each record to its entity, type, date, status and retention category, so the same question always has the same answer wherever it comes from in the group.

Test electronic exports as well. Some jurisdictions expect records kept electronically to be producible in readable form on request. Produce one export now, check that it is complete and legible, and fix the gaps before a request arrives.

Where to start: a practical next step for your group

Start with one entity, the one that produces the most minutes and filings. List its corporate records by category and, for each one, note the owner, the jurisdiction, the roles that can open it and the retention rule. It is dull work, but every later decision depends on it.

Ownership matters as much as structure. Someone has to define the common rules and keep them consistent across countries, which is the role described in what a legal operations manager does. The information governance and knowledge management domains of the CLOC Core 12 offer a useful frame for deciding which of these responsibilities sit at group level and which stay local.

The tool matters less than the order of the decisions: which entity owns each record, who can open it and how long it stays. Once those answers exist for one entity, extending the model to the next one is a copy of a pattern, not a new project.

How does Alf support legal document management across entities?

Alf is the operating infrastructure for global legal departments: it connects people, processes, knowledge and AI agents in one governed system. It is built around Organizational Legal Context, a shared operating context that lets humans and agents know who can do what, on which matter, in which entity, under which rule and with what level of autonomy. For document management, that context is the entity, the owner, the access rule and the status described above, held in one place instead of in separate tools.

Alf’s capabilities include centralization of dossiers and documents, configurable workflows and forms without code, approval workflows, a shared calendar with deadline alerts, a chronological history of each dossier and access rights by user, group or dossier. Teams can start a dossier from Outlook, generate documents from Alf templates built on Word, and sign electronically, including through DocuSign. The interface is multilingual, activity reports and dashboards give a group-level view, and an AI agent works from the context of the dossiers. Data is hosted in the European Union, encrypted at rest and in transit, with two-factor authentication and role-based access rights. You can explore the features and the security practices in more detail.

Alf is designed to let a group scale legal operations without scaling complexity: a new entity joins the existing model, group rules become workflows that respect local specifics, and validations and decisions are logged. The inventory of one entity’s records is still the first step, and the structure you define there is the one a system can then carry across the group.

Who in your group owns each entity’s records? Bring one real filing and walk through it with the Alf team.

Book a demo

Frequently asked questions

What is the difference between a legal document management system and a contract repository?

A contract repository focuses on contracts: finding the right agreement, its entity, its access rights and the context in which it was handled. A legal document management system is wider and also covers corporate records, policies, filings, advice and matter files, each with its own owner, access rules and retention rule.

The two overlap and often complement each other. A group can run a contract repository for agreements and apply the same entity, access and retention logic to every other document type, so the rules stay consistent.

Which records should a legal department keep for each entity?

For each entity, keep its formation and governing documents, shareholder and board records, policies, filings and any books or registers its jurisdiction requires. The exact list depends on the entity’s legal form and the law of the place where it was formed.

Start from the entity list and check requirements with local counsel for each jurisdiction. Record the result as a category list with an owner, so a new subsidiary can follow the same pattern.

Is there one retention period for corporate records across jurisdictions?

No. Retention periods are set by record type and by the jurisdiction that applies to each record, and the same type of record may follow different rules in different countries. A single period applied to every document either keeps too much or deletes too early.

Define each rule with a starting point, such as the creation date or a defined event, and a retention period confirmed with local counsel. Before any deletion, check whether a legal hold or another preservation obligation applies.

Should board minutes and draft policies be stored in the same folder?

Not by default. Minutes and policies belong to different functions, so each gets its own folder under the entity, with approved and draft versions clearly separated.

If a draft and the approved copy end up together, the status and version in each file name should make the record copy obvious.

Who should have access to a subsidiary’s legal records?

Give access to the roles that need a subsidiary’s records for their work, and no broader permissions than that work requires. Split access by entity first and by record category second, so board minutes stay apart from routine filings.

Remember that shareholders, auditors and regulators may hold statutory rights to inspect some records, depending on the governing law. Name the holder of each record in the directory, so a request can be routed without a search.