GUIDE · PROFESSIONAL FIRMS

Archiving digital case files: access and retention

After reading this guide you will know how to organise a firm's digital archive, who should be able to see what, how long to keep documents and how to verify that the system holds up in practice. The procedure is designed for a firm of any size.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. Why a digital archive needs to be designed

A digital archive that grows without rules soon becomes hard to use. Files end up in personal folders, the same case appears under different names, and after a few years nobody knows which version is the final one. The problem is not the technology but the absence of a shared structure. A well-designed archive makes searches faster, avoids duplicates and makes it possible to show at any moment what was done on a case.

Designing the archive means deciding three things in advance: how case files are organised, who can access them and how long they remain available. These decisions cost little at the start and a great deal when they have to be corrected years later, with files already in disorder and access inherited from people who no longer work at the firm. It is worth making them before the archive becomes large. Every delay adds files to sort out, and the work grows faster than goodwill can keep up.

2. What you need before you start

Before touching any folders you need a few things. The first is an archive owner, a person who sets the rules and enforces them, even when someone finds them inconvenient. The second is a list of the types of case the firm handles, with the typical documents for each. The third is a snapshot of what exists: where the files are today, how many systems hold them and who actually uses them, not who is supposed to.

You also need an agreement with the IT supplier on where the archive resides, which tools host it and how backups are made. Ask for the agreement to be written down and to state who intervenes in case of a problem. Ask also how long it takes to restore a case file, because the answer changes priorities. Without this step the rules remain on paper while reality follows other paths, often without anyone noticing.

3. The operational steps

The sequence matters. It is best to define the structure and naming rules first, then access, then retention and finally backups. Reversing the order leads to configuring tools before knowing what they must do, and then reconfiguring them twice. The following steps can be completed in a few meetings, provided each closes with a written decision and a name beside it.

Each step should produce a short document that staff can consult. You do not need a long manual: one page for the structure, one for access, one for retention and one for backups is enough. Keep the pages in the same place as the archive, so that anyone looking for a rule finds it where they work. Update the pages whenever a rule changes, and record the date of the change.

  1. Define the folder structure by client and by case, with a written naming convention.
  2. Establish who is responsible for each archive and who may open or close a case file.
  3. Set access groups according to role, not to individual people.
  4. Enable the change log and retention of earlier versions.
  5. Write the retention rules: how long each type of document remains available and when it is deleted.
  6. Configure backups separate from the main archive, with a copy that ordinary users cannot modify.
  7. Carry out a restore test of an entire case file and document the result.

4. Access and roles

Access is the element that most often degrades over time. When a collaborator changes role they receive new permissions but usually do not lose the old ones. The result is that different people see cases they should not see, without anyone noticing. To prevent this, link access to groups that correspond to specific functions, and give each group an owner who approves additions and revocations.

The practical principle is simple: each person sees what their work requires and nothing more. For the most sensitive case files, an additional access level with a recorded justification is advisable. Revocations must be carried out as soon as an assignment ends, not at the next periodic review, because it is precisely in the period between the end of an assignment and the review that forgotten access accumulates.

5. How long to keep documents

There is no single retention period that suits every firm. It depends on the type of act, the rules of the profession and the specific obligations relating to the client's sector. For this reason the retention rule should be written with an adviser or your professional body, and then applied consistently. An unwritten rule is applied differently by each person and will not hold up if challenged.

A good rule states, for each type of document, the minimum retention period, the point at which the case file is closed and the person responsible for the final decision on any deletion. Deletion must be documented, because a document that disappears without a trace causes more problems than one kept too long. If in doubt, it is better to keep and review the decision at the next review.

6. Common mistakes

The most frequent mistakes are always the same, and they recur in very different firms. It is worth checking each one, because each conceals a risk that only surfaces when a document is needed urgently. The list below covers the most common, to check against your archive before writing the new rules. They do not all need to be present: recognising just one in the current archive shows where to act.

  • Personal folders used as the main archive, which disappear when a collaborator leaves the firm.
  • Multiple versions of the same file under different names with no final version.
  • Inherited access that nobody has reviewed since a change of role.
  • Backups that carry the same permissions as the archive, and so are exposed to the same error.
  • No restore test, and therefore no certainty that the copy works.

7. How to check that it works

An archive is checked by sampling, regularly. Choose some closed cases and try to reconstruct them: the file must be complete, the versions recognisable and the access consistent with current roles. If a case cannot be reconstructed within a few minutes, the problem must be understood and corrected before it happens with an urgent document, when little time is available. Choose the cases at random, not only those you remember, because it is precisely the forgotten ones that give the most useful indications.

After the check, update the rules with what you have discovered and set the date of the next review. If the check reveals access that is no longer justified, correct it immediately and record the reason. Periodic checking is the part that holds everything else together, and its outcome should be kept like any other firm document. Anyone reading the outcome must be able to see quickly what was corrected and what remains to be done.

8. How to get started

This week choose one very common type of case and sketch its folder structure on a single page. Decide the file names, the mandatory documents and who can see them. It is a small but real test, and it immediately shows how many points will need deciding for all the other types of case. Carry out the test with someone who works on that type of case every day, not only with the owner.

Then ask the IT supplier for the list of current access to the chosen archive and the date of the last restore test. Compare them with the page you have written. The differences indicate the work for the coming meetings, and give you a concrete basis for deciding priorities and responsibilities. Share the result with staff, so that the next review is a team effort.

Frequently Asked Questions

Is one shared folder for the whole firm a good idea?

It depends on size and organisation. A single structure is simple to consult, but it makes it harder to limit access by case. Often a common structure for document types, with separate permissions by client, works best. In any case, you need a written rule on who creates folders and who closes them.

How do I stop file names becoming chaotic?

With a written convention that is short and the same for everyone. It can include the client, the document type, the date in the agreed format and a version number. The rule should also apply to files received from outside, as those create the most disorder. An example next to the rule helps far more than an abstract description.

When can a closed case file be deleted?

When the retention periods defined for that type of case have expired, and after a recorded decision by the person responsible. The period must be set with an adviser or your professional body. Before deletion, check that there are no ongoing disputes or related requests for documents.

Can the cloud provider read my case files?

It depends on the service, the contract and the encryption settings. Ask in writing who can access the data, in what circumstances and with what controls, and whether the encryption keys are managed by the firm or by the provider. The answers should be assessed together with a data protection adviser.

How often should the archive be reviewed?

With predictable regularity, for example at fixed intervals set by the owner. The review should cover access, a sample of closed cases and the outcome of the last restore test. It does not need to be long: what matters is that it always happens and produces a written note.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →