A project archive becomes useful when somebody who did not make the exhibition can answer a real question from it. They may need the final text, the identity of a pictured object, the permitted use of a photograph or the instructions for a retained display system. A large folder is not automatically an archive in that sense. It can contain thousands of files while still leaving the reader unable to tell which version reached the gallery.

The work begins with a final account of the exhibition as delivered. Preserve the connection between that account and the evidence, permissions, components and decisions behind it. The method below is intended for a small cultural team organising its own project record. Collection archives, personal information, financial records and legally significant documentation may have specific requirements that need the organisation's appropriate archival, privacy and professional guidance.

Define the questions the archive should answer

Begin with likely future users rather than a folder structure. An editor needs the final text and its source relationships. A technician needs installed equipment information and approved operating instructions. A loans coordinator needs traceable object movements and return records. A future curator may want to understand why a proposed section was omitted. These users share a project but do not need identical access to every file.

Write a short set of retrieval tasks: find the final label for an identified object, identify the approved photograph of a particular view, locate the instructions for a retained component, or explain the difference between an early proposal and the completed exhibition. Use those tasks later to test the archive. An arrangement that works only when its creator supplies the answer verbally is still dependent on personal memory.

Distinguish the organisational archive from a public exhibition record. Public documentation can explain the exhibition and show selected views without exposing loan contacts, personal correspondence or restricted rights information. Do not assume that preserving a file means publishing it, or that an online project page provides an adequate private operational record. Define those functions deliberately and connect them through appropriate references.

Create a concise account of what was delivered

Prepare an exhibition summary that identifies its title, relevant dates, venue, principal contributors, scope and the record's responsible organisation. Explain significant changes from the initial brief. A visitor reading the final panel may have encountered a different object selection or interpretive sequence from the one described in a funding proposal. The archive should make that relationship understandable without requiring a comparison of every draft.

Record the installed arrangement through verified final drawings or an appropriately described plan, selected photographs and the final text inventory. If a drawing remains partly inaccurate, label its limitations instead of giving it a definitive name. The goal is not to manufacture perfect documentation after the fact; it is to preserve an honest account of which information describes the actual result and where uncertainty remains.

Add a short guide to important identifiers. Explain how object numbers, panel references, media-station names and component codes relate. These conventions may have been obvious to the project team but become opaque later. A future staff member should not need to infer whether P-04 is a printed panel, a packing location or a photograph merely because several suppliers independently used the same abbreviation.

Separate final records from the history of revision

Keep a clearly identified final set for ordinary retrieval. Preserve significant earlier versions where they explain a consequential decision, contractual instruction or editorial development, following the organisation's requirements. Do not equate comprehensive preservation with giving every rough draft equal prominence. A person seeking the installed label should not have to choose between files named final, final revised and final revised correct.

Use meaningful filenames and a consistent version record. Include a stable identifier, a concise description and a status or date where appropriate. Avoid names that depend on somebody remembering the circumstances of an email. If the final file came from a supplier, connect it to the relevant approval or installed record rather than assuming its latest modification time establishes its authority.

Where a correction occurred after opening, preserve both the current public content and the necessary account of the change. A material factual correction may matter to future interpretation, while a routine spelling fix need not become a dramatic project narrative. The record should be proportionate and traceable. Do not erase the history needed to understand a significant change merely to make the final folder appear tidy.

Keep rights information attached to the relevant material

A photograph, interview extract, design file or reproduced work may have a defined use arrangement. Record the material's identifier, the relevant agreement or source, permitted uses, required credit where applicable and any known limitation. Use the organisation's appropriate rights process and seek advice on uncertainty. A file being present in the project folder does not establish that a future team can publish or modify it freely.

Make restrictions discoverable at the point of reuse. If the rights record is stored separately, use an unambiguous reference from the material's catalogue entry. Do not rely on a warning buried in an unrelated email thread. A future editor who can find the image but not its conditions is likely to misunderstand what the archive has supplied, particularly when an exhibition use differs from a later promotional or commercial use.

Keep personal participation agreements and private contact information under suitable access controls. A public credit preference can be recorded in the public-content workflow without exposing everything discussed during an interview. Retention and access periods should come from the organisation's actual responsibilities and agreements, not an invented universal duration. Review the arrangement when a new use is proposed rather than treating archive access as blanket permission.

Preserve the relationships between media, hardware and reusable parts

For installed media, distinguish the approved content master from the version used by the playback equipment. Record the relevant format, filename, content version, associated transcript or captions and the station where it appeared. A collection of audio files without speaker identities or a relationship to the final exhibition can be difficult to interpret even when every file opens successfully.

For retained physical components, connect the inventory to their current location, assembly information and known condition. Explain substitutions and modifications made during installation. A future team should know whether a panel was designed to be replaced, which fittings belong with a unit and what work still requires the original supplier or specialist. The archive should not encourage unqualified reconstruction from photographs alone.

Coordinate ownership of the record. A fabrication drawing may belong to a supplier while a technical operating note is maintained by the venue. Record what has actually been supplied and what remains accessible only through another party. If the project expects future reuse, address the information needed for that use before the supplier relationship ends. An attractive promise of reusability is incomplete without an intelligible retained system.

Select photographs that explain the exhibition

Preserve more than publicity images. A useful installed record can include orientation views, relationships between sections, object-label positions, relevant interactive states and important production details. Choose images that answer the archive's retrieval questions. Hundreds of nearly identical photographs can make a record harder to navigate while still omitting the one junction needed to understand a retained assembly.

Describe what each selected image shows and when it was made. Distinguish an installation-stage view from an opening-day arrangement or a later modification. Do not use a photograph of an unfinished room as if it represented the public exhibition without context. Where people appear, handle identification, privacy and use according to the organisation's actual arrangements and the context in which the image was obtained.

Connect photographs to object or component identifiers where useful. A descriptive caption such as north wall, section two is more informative when it relates to a verified plan. Preserve original files and appropriate working versions under the organisation's digital-preservation approach. The article does not prescribe one universal file format or backup system, but a project should avoid relying on low-resolution copies embedded in an old presentation as its only visual record.

A hypothetical archive recovered from scattered folders

Imagine a small cultural centre finishing an exhibition whose files sit across an editor's computer, a fabricator's delivery folder and a volunteer's shared drive. The team initially copies everything into a single archive directory. A retrieval trial then asks another colleague to find the final wording beside one object. They locate three plausible text files and a photograph showing a fourth version, with no note explaining the difference.

The team creates a final text inventory linked to object and panel identifiers. It records the post-opening change that explains the photograph and labels the superseded drafts. The fabrication folder is connected to the retained-component inventory, while personal correspondence remains in an appropriately controlled record. Selected installed images receive descriptions and dates. The archive summary explains which drawings reflect later changes and which remain proposals.

A second retrieval trial asks for the conditions attached to an interview extract and the location of a reusable unit. Those tasks reveal missing links that the team can resolve while people still remember the project. This hypothetical example shows that usefulness comes from relationships and explanation, not simply from increasing the number of files kept after closing.

Write an index that explains where to begin

The archive index should orient a new user without requiring them to inspect every directory. Describe the principal record groups and their purposes in ordinary language. Identify the authoritative final account, the development history, the technical and retained-component information, and the route to restricted records. Include a contact role for questions rather than publishing an unrestricted list of everybody who once worked on the project.

Explain exceptions that would otherwise look like mistakes. Perhaps an object identifier changed after a loan was cancelled, one section was installed differently from the approved rendering, or a media file has separate language versions. A concise note can prevent hours of speculation. Link to the evidence where necessary, but do not reproduce an entire correspondence history in the index. It should help a person locate the right record and understand its status.

Test the index with the actual terminology used by future colleagues. A person searching for captions may not know that the project stored them under interpretation assets. Add helpful cross-references rather than expecting everyone to learn the original team's vocabulary. Keep the index itself versioned and under the same custody as the archive. An explanatory document left on somebody's desktop cannot support a collection of files stored elsewhere.

Assign a custodian and test the archive over time

Name the organisational role responsible for the archive after the temporary project ends. The role needs to know where the record is held, who can request access and how corrections or new use enquiries are handled. A personal account owned by someone leaving the organisation is not a durable access plan, even if the files themselves are well organised. Follow the institution's established information and digital-preservation arrangements.

Check that important files can be opened and understood using the intended systems, with appropriate technical support where needed. Preserve the context required for specialised formats and identify material that depends on unavailable software or an external provider. Do not silently convert complex records in a way that loses essential information merely to produce a folder of convenient previews. Any preservation action should follow competent advice and a documented method.

Repeat a few real retrieval tasks after handover. Ask someone outside the original team to identify final content, locate a rights reference and understand one retained component. Record what prevented them from completing the task and improve the index accordingly. An archive remains useful when it is treated as an information resource with accountable custody, rather than a ceremonial final upload that nobody checks until the next exhibition urgently needs it.

Questions specific to this guide

Should every draft be deleted once a final version exists?

No. Significant drafts may be needed to explain decisions or meet organisational and legal requirements. Separate the authoritative final set from retained development history and follow the applicable retention arrangements. Tidiness is not a reason to destroy a record that still serves a legitimate purpose.

Can the public exhibition website serve as the whole archive?

It can be one useful public record, but it usually does not contain all operational, rights, loan, technical and decision information. Those records may also require different access controls. Connect the public account to the appropriate organisational archive rather than publishing restricted information to make the website comprehensive.

What is the quickest useful archive test?

Ask someone unfamiliar with the project to find the final text for one object and explain the basis for reusing one image. If they cannot distinguish versions or locate the relevant rights information, improve those relationships before adding more material to the folder.

Further reading

Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.