An archive handover is more than sending a folder link. The receiving organisation needs to understand the material, its structure, the relevant restrictions and the decisions it may need to make later. A small test of usability can reveal gaps before the project closes.

Preparing an Archive Handover for a Partner Organisation

Separate possession of files from responsibility for maintaining or publishing them. Confirm what the partner has agreed to take on rather than assuming that receiving a copy includes every future task.

Agree who will look after the record after the activity ends. A collection can become difficult to use when staff leave, access accounts change or the meaning of filenames is lost. A brief handover should explain the structure, the permitted uses, the unresolved issues and the person or organisation responsible for future decisions. Check that the recipient can actually open the material.

Put the method into practice

1. Write a short guide to the collection and its main identifiers.
2. Explain access arrangements, permitted uses and unresolved questions.
3. Ask the recipient to locate and open a sample of related files.

Use stable identifiers or clear filenames to connect related material. A photograph, recording, caption, permission record and final publication may all refer to the same contribution. The next person should not have to identify that connection from memory. Keep the structure understandable enough for a small team to maintain without turning routine documentation into a separate technical project.

An illustrative situation

For instance, the recipient could try finding an approved photograph, its caption and the corresponding permissions record. If this requires calling the departing artist, the handover needs clearer connections.

Documentation has several possible audiences. The artist may need process notes, a partner may need a practical handover, and a visitor may need a concise explanation of the work. These are not automatically the same document. Prepare an appropriate public version rather than exposing every internal comment, contact detail and unresolved discussion in the name of transparency.

The mistake worth avoiding

Do not transfer unnecessary personal information simply because it sits in the project folder. Follow the appropriate retention and transfer arrangements.

Keep the working record close to the activity it describes. A short note made after a session can preserve a change of plan, an unresolved question or a participant's suggested adjustment more accurately than a polished account written much later. Separate observation from interpretation, and mark anything that needs checking before it becomes part of the public story.

Make the wider arrangement work

Give people a realistic account of what can be changed or removed at different stages. An unpublished working file, a temporary display and material already distributed to others present different practical questions. Avoid sweeping promises that the team cannot honour. When a request arrives, pause further use where appropriate, check the agreement and involve the person responsible for deciding the next step.

Plan a realistic route for later questions about contributions, credits and archived material. A contact address is useful only while someone is responsible for monitoring it. When responsibility changes, update the public information and the handover record. Avoid promising indefinite personal availability if the project has no resources or agreement to provide it.

Turn a finding into a decision that somebody can act on. If the invitation was difficult to understand, specify which part needs rewriting and test the new version. If a resource was missing, identify who can address it before the next session. A report that records every issue without changing the plan is less useful than a short review that leads to a clear improvement.

Bring the activity to a clear finish

A good handover gives the next custodian both usable material and a realistic understanding of the responsibilities that accompany it.

Related reading

Writing a Public Summary of a Participatory Art Process; Writing Process Notes After an Art Workshop; Building a Timeline for a Participatory Art Case Study.

Background and further reference

Library of Congress: identifying, organising and preserving digital material.