A collaborative artwork may change its materials, display or participation format several times. A decision log helps the team understand those changes later. It should record the reason and responsibility, not simply produce a list of dates.

Keeping a Decision Log for a Collaborative Artwork

Distinguish a suggestion under discussion from a decision that people are expected to act on. Confusing the two can make a project appear settled when important agreement is still missing.

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.

Three useful steps

1. Record the question, the chosen option and the people responsible.
2. Note the reason and any condition that still applies.
3. Update the practical plan so the decision reaches those affected.

Preserve the difference between what was planned and what happened. Changes are often an important part of participatory practice, not an embarrassment to remove from the record. Explain a revised prompt, a shorter session or an altered display in proportion to its importance. This helps later readers understand the method instead of seeing only a smooth retrospective narrative.

Consider a small example

Imagine a window project that replaces a hanging element with a supported display after a venue review. Recording the reason helps a later team avoid quietly returning to the original arrangement without checking the same issue.

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.

Where the approach can go wrong

Do not treat the log as proof that everybody endorsed each choice. Record consultation and responsibility accurately rather than smoothing them into a claim of consensus.

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.

Consider the people and the context

Participation, recording and publication are related but distinct decisions. A person may join a workshop without agreeing to appear in publicity, or share a story under conditions that do not cover later reuse. Keep the relevant arrangements connected to the material and its proposed use. Where legal rights or data protection duties are involved, obtain suitable advice rather than treating a generic form as a complete solution.

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.

What to carry into the project

A useful log lets someone follow the project's development and identify which assumptions should be revisited if conditions change.

Related reading

Building a Timeline for a Participatory Art Case Study; Naming Files for a Small Art Project Archive; Choosing Documentation Methods for a Community Art Project.

Background and further reference

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