Home / Project Stories / The Project Was Closed. The Materials Were Still Needed.
Archival Case Study

The Project Was Closed. The Materials Were Still Needed.

A year after a design project ended, the client asked for original source materials. The team had to recover the right files and the context behind them.

Author: Michael Vance
Date: September 25, 2026
6 min read
Volume Ref: AR-2026-CS9

Project Organization Case Studies · Project Archives · Long-Term Organization · Ownership & Decision Context

Why the original materials mattered again

A design team delivered the approved work, closed the project, and moved on. Twelve months later, the client requested editable source files for a new campaign. The final presentation showed the outcome, but it could not replace the working assets that made revisions possible.

The request raised the central archive question: why had each material been kept, and did that reason still apply? The answer depended on the original brief, ownership after closeout, and the difference between exploratory files and approved versions.

Project materials reviewed after a client requested original design files
A project archive needs enough context to distinguish editable sources from final deliverables.

Original purpose

The working folder held drafts, linked assets, fonts, and editable layouts. The final export was sufficient for the original delivery, while the source files were kept in case the client needed a later adaptation. That reason had not been written down clearly.

Responsibility after closeout

The project manager had moved to another account and the designer who created the files was no longer responsible for the archive. The team identified a current owner for the request and recorded where the materials lived, who could authorize access, and whom to ask about usage rights.

Working files versus final versions

Several similarly named decks and image sets looked final. The team used approval messages and dated exports to identify the delivered version, then linked it to the editable source package. Drafts remained labeled as drafts, so a future reader would not mistake an exploration for an approved design.

What they chose to keep

The useful archive was more than a folder of files: it included the brief, the approved outcome, source materials, ownership notes, and a short explanation of why each group remained accessible. Temporary exports and duplicate copies could be reviewed separately.

A visual allocation mapper such as WizTree can help locate large or repeated folders during this review. It cannot explain the client's request or decide which material carries the right context; that judgment belongs to the team.

Peer Commentary

Archival Review Debriefs

Active Thread
No archival comments yet. Be the first to leave feedback for this project record.

Submit Archival Feedback

Contribute your analysis to this project record preservation log.

Observations are peer-cataloged before indexing.