Why archive at all
Active folders get crowded with finished work. Every completed project that stays alongside current ones makes the current ones slightly harder to see. At the same time, deleting old projects feels risky, because questions come back: What did we quote that client? Why did we choose that approach? Where is the signed version?
Project archiving is the middle path. You move finished work out of the active area, keep what has lasting value, and make sure it can still be found. Done well, the archive is quiet most of the time and useful on the occasions you need it.
Decide when a project is finished
Archiving too early causes friction, since you end up pulling things back. Archiving too late defeats the purpose. A reasonable trigger is a clear event: the final deliverable is accepted, the last invoice is settled, or the work is formally closed. If a project is simply dormant, you can mark it as paused rather than archive it.
Write the closing date down. It makes the archive easier to sort later and gives you a natural point to do the cleanup while the project is still fresh in your mind.
Sort what is inside
Before moving a project, look at what it contains. Files usually fall into a few groups:
- Final outputs. The delivered documents, approved designs, published versions. These almost always stay.
- Agreements and records. Contracts, approvals, invoices and correspondence that confirm what was agreed. Some may need to be kept for a period set by law or company policy, which varies by location and type of document, so check the rules that apply to you rather than assuming.
- Source material. Raw files needed to reproduce or edit the output later. Keep these if you might reuse or revise the work.
- Working drafts and duplicates. Intermediate versions, exports and scratch files. These are the usual candidates for deletion, though the final draft’s history may be preserved by version history in the tool you used.
- Personal data. Customer details and similar information. Retaining it longer than needed can create obligations, so handling customer data responsibly applies at the archive stage too.
Pruning the last two groups often shrinks an archive considerably, and what remains is easier to understand.
Write a one-page summary
The most valuable file in an archived project is often one you create at closing: a short summary note. It does not need to be elaborate. A few lines usually cover:
- What the project was and who was involved
- Start and end dates
- What was delivered
- What went well, what did not, and anything you would do differently
- Where the important files are
Months later, this note answers most questions without anyone opening a single other file. It also preserves context that a pile of documents cannot: the reasons behind decisions. Store it at the top of the archived folder with an obvious name so it is the first thing anyone sees.
Keep a consistent archive structure
Put archived projects in one place, separate from active work. A few options work well:
- A top-level archive folder with a subfolder for each year of completion, then one folder per project
- An archive organized by client, if clients are how you usually search
Whichever you choose, name the project folders using the same pattern across the archive, as described in the material on file naming, for example with the closing year and a short project name. Consistent names make the archive sortable and searchable. Avoid creating a unique structure inside each project; copying the same internal layout, such as a folder for deliverables and one for records, makes old projects predictable to navigate.
Make the archive findable
An archive that cannot be searched is a graveyard. A few habits keep it useful:
- Use distinctive words in folder and summary names, including the client name spelled the same way every time.
- Keep the summary note in plain text or a common document format that search tools can read.
- Make sure your archive location is covered by the search tool you actually use.
If you want the archive to be easy to scan by eye, a simple index file listing projects with one line each can be worth the small upkeep.
Protect the archive
Archived work is easy to forget, which makes it easy to lose. Check that the archive is included in your backups, since cloud sync is not a real backup and will faithfully copy an accidental deletion. Backup basics explain the distinction. Also consider who can still open the files: sharing permissions on old project folders often stay broader than needed, and tightening them at closing is a sensible step. When team members leave, access offboarding should cover archives as well as active spaces.
Occasionally open an archived file to confirm it still works. File formats and tools change over time, and the discovery that an old file cannot be opened is better made on a calm afternoon than during an urgent request.
Move, do not scatter
When you archive, move the whole project to its new location rather than copying pieces. Copies left behind create the same duplicate problem that archiving is meant to solve. If other people use the project folder, tell them where it went, or leave a short note file at the old location pointing to the new one.
Review the archive itself
An archive is not necessarily forever. Once or twice a year, or when storage becomes a concern, skim for material that has passed any required retention period and has no remaining value. Deleting deliberately, with a record of what you removed and why, is a healthier habit than letting an archive grow without limits. If you are unsure whether something may still be needed for legal or tax reasons, ask someone qualified before removing it.