What Is Document Archiving? File Plans, Terms, Disposal

Document archiving is what happens to a document after the work on it is finished. It stops being something people edit and becomes something the organisation keeps: as evidence, as a legal obligation, or because somebody will need it in seven years. A document archiving system is the software that holds those documents and, more importantly, the rules attached to them.

That second half is where most projects go wrong. Moving files to cheaper storage is easy. Knowing which of them may be deleted next March, and proving who deleted them, is the part that takes a system.

Archiving is not the same as document management

The two words get used interchangeably, and the distinction matters as soon as an auditor arrives.

• Document management deals with work in progress: who is writing, who approves, which version is current, where the comments live.
• Document archiving deals with what happens after that: long-term storage that stays readable and findable, with a term attached to every case.
• Records management is the rulebook over the archive: the file plan, the retention schedule, who may see what, and how disposal is documented.

A small organisation can run all three out of one system without naming them separately. A regulated one cannot, because each of the three answers a different question at an inspection.

What a document archiving system actually has to do

Hold a file plan

A file plan is the structure of cases: what belongs where, and under which rule. Without it, archiving is a folder with a better name. With it, a new document falls into the right case automatically rather than into somebody's personal structure.

Attach a retention term to every case

Not to a document, and not to a site or a folder: to the case. Contracts, personnel files and accounting records keep different terms, and the same project folder can hold all three. The system should refuse to delete a record before its term expires, which is a feature, not an inconvenience.

Destroy, and prove it

Deleting is not destroying. Disposal in an archive produces a report that says what was destroyed, under which rule, and who signed it. That report is itself a document with its own retention term. Destruction can run automatically when a term expires or be started by hand, and both should leave the same trace.

Log access

Who opened, changed, moved or destroyed a document, and when. The log is what you show at an audit instead of a promise. It is also what tells you, after an incident, whether anything actually happened.

Find things

An archive nobody can search is a warehouse. Full-text search across formats, search by case attributes, and search that still works on scanned paper are the difference between an archive and a pile.

Paper and electronic belong in one archive

Most organisations that start an archiving project have both, and treat them as two worlds: a system for files and a room for boxes. That split is what makes retention impossible to run, because half the cases are invisible to the rules.

The workable arrangement is one file plan over both. Paper cases are registered with the same attributes, their physical location is recorded, and scanning with recognition brings the content itself into search. Withdrawal and return of an original are tracked like any other action.

How to start without boiling the ocean

An archiving project does not start with software. It starts with an inventory: what is already kept, where it physically sits, and under which rule. Almost every inventory finds paper and electronic records living under different rules, and a file plan that exists on somebody's disk rather than in a system.

The first working result should be narrow and dull. One approved file plan, one group of cases moved under it, terms attached, the log switched on, and one disposal run taken through the full cycle including the report. That is enough to answer an auditor about that group, and enough to show the rest of the organisation what the target state looks like. Scope grows from there.

Where this sits in our products

If you are looking at the storage side, that is our document archiving software, built on the electronic document archive module. If the rules side is what hurts, the file plan and the retention schedules, that is records management software. If the documents live in Microsoft 365, the same rules apply through SharePoint archiving.

FAQ

What is the difference between document archiving and backup? A backup is a copy made so you can restore a system after a failure, and it is overwritten on a cycle. An archive is the authoritative copy kept for a defined term, with rules about who may read it and how it is destroyed. Backups answer "the server died". Archives answer "show me this contract from 2019 and prove nobody altered it".

How long should documents be kept? That is set by your regulator and your own policy, not by the software, and it differs by type of document and by country. What the software has to do is hold whatever terms you set, apply them per case, and make the expiry visible before it arrives rather than after.

Can documents be destroyed automatically when the term ends? Yes, and it should be a setting rather than a rule of nature. Automatic disposal on expiry suits high-volume routine cases; manual disposal with a human decision suits everything sensitive. Both should produce the same signed report.

Does a document archiving system replace the paper archive? Not on day one, and often not at all. Paper that must exist in original form stays in the room. What changes is that the room is described in the same file plan, with the same terms and the same search, instead of being a separate world.

Related reading. how to write a retention policy, the six stages of a document, version control rules.

See it on your own file plan. Talk to us and we will show the archive on your rules rather than on a sample database.