A project timeline can help readers understand how an invitation became a series of activities and then a public work. It is most useful when it includes important changes, not just the milestones that appeared in the original proposal.

Building a Timeline for a Participatory Art Case Study

Separate dates that describe actual events from planned dates and later interpretation. The distinction matters when a project was extended, paused or rearranged.

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.

Put the method into practice

• Identify the main stages using reliable project records.
• Add changes that affected participation, making or display.
• Check that captions and linked material use the same sequence.

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.

An illustrative situation

For example, a case study might show that an initial drop-in session led to a revised drawing prompt before the final workshop. That makes the collaborative development clearer than a timeline containing only launch and opening.

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.

The mistake worth avoiding

Avoid inventing a precise date because it makes the layout look complete. Use a less specific description or mark uncertainty when the record does not support exactness.

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.

Make the wider arrangement work

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.

Keep the surviving record understandable beyond the original team's memory. A future reader needs the project's purpose, dates, context and relevant restrictions, as well as a selection of the material itself. Explain which parts are complete and which remain uncertain. This is especially important when a short-lived public activity is later encountered only through a website or archive.

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 helpful timeline explains the order and development of the work while leaving the record honest about gaps and revisions.

Related reading

Separating Working Files from Public Project Archives; Documenting Changes to a Temporary Installation; Preparing an Archive Handover for a Partner Organisation.

Background and further reference

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