How to Document a Performance-Based Digital Art Piece
Documenting a performance-based digital art piece requires more than filming an event from the back of the room. The record must communicate the work’s timing, atmosphere, audience relationships, software behaviour, physical setting and the choices made by the artist. A strong archive helps people understand what happened live, even when they encounter the project months or years later.
This matters especially for experimental work shown in artist-run spaces, galleries, festivals and online showcases. A project presented during Vivid Sydney, in a Melbourne laneway gallery or at a regional arts venue may have several lives: a live event, a portfolio case study, an educational resource and a record for future curators. Plan for each use before the performance begins.
Define The Live Work
Start by describing what must be experienced in person. Is the central element a performer’s movement, audience participation, projected imagery, live sound, changing data or a combination of these? Write a short treatment that explains the sequence of actions, the role of technology and what changes from one performance to the next.
Record the conditions around the work as carefully as the work itself. Note the venue, date, duration, lighting state, equipment, software version, internet connection and number of participants. If the project responds to weather, biometric information or audience behaviour, explain the input and its effect in plain language. A future viewer should be able to distinguish the artistic intention from an accidental technical fault.
Build A Capture Plan
Use several forms of documentation rather than relying on one camera. A wide shot establishes the room and audience, a closer angle captures gestures and interfaces, and a separate audio recorder preserves speech, ambient noise and system output. If the piece includes projected visuals, test exposure and focus in advance so the image does not become washed out or flicker.
Make a running sheet for the person operating the camera. Mark entrances, key interactions, software changes and moments when the audience becomes part of the composition. For a work in a busy Sydney venue, allow for traffic noise, announcements and people moving through the frame. A quick tech rehearsal in the arvo can reveal problems that are difficult to fix once the doors open.
Record Space And Audience
A performance is shaped by its surroundings, so capture establishing images before the audience arrives. Photograph the entrance, floor plan, screens, speakers, cables, signage and accessibility arrangements. Short clips of the empty installation can show scale and spatial relationships more clearly than a final edit made entirely from live footage.
Audience response also forms part of the evidence, but it should be observed respectfully. Film hands, silhouettes, group movement and changes in attention when identifiable faces are not necessary. For participatory work, document the instructions people receive and the choices they make. This is particularly useful when a project tours from a Melbourne arts space to a regional community venue, where room layout and audience habits may change.
Handle Consent And Data
Prepare consent language that matches the project’s actual risks. Tell performers, visitors and collaborators whether recordings will appear on a website, in a grant report, at a festival or in an archive. Written releases are helpful, but clear verbal explanations and visible signage can support a practical process for casual attendees. Follow Australian privacy obligations, especially when the artwork collects faces, voices, movement patterns or biometric data.
If you need clarification about publishing credits, access conditions or a project record, use the ITP 30 contact page rather than guessing. Data should be minimised, stored securely and deleted when it no longer serves a documented purpose. For First Nations artists or communities, seek appropriate cultural permissions and follow the protocols requested by participants, not just the venue’s standard media policy.
Preserve Technical Context
Save the files that explain how the work functioned: source code, interface designs, cue sheets, sensor diagrams, sound stems, installation photographs and software dependencies. Include a simple readme with equipment models, operating systems, screen dimensions, network requirements and known limitations. A future curator may need to recreate the piece on a different projector or an updated laptop.
Projects involving sensors and automated environments deserve especially precise notes. An article about biometric lighting control demonstrates why the relationship between input, computation and visual output should be made legible. Preserve representative data samples where permission allows, while separating personal information from material intended for public access.
Edit A Coherent Record
Create several outputs for different audiences. A two-minute trailer can communicate mood and movement, while a longer documentation film can preserve sequence, dialogue and audience participation. Add captions, a transcript, descriptive metadata and an audio description where practical. Keep the edit honest: atmospheric music or dramatic cuts should not imply events that did not occur.
Retain the original camera files and an untouched audio master, then make access copies in widely supported formats. Name files consistently with the project, date, version and location. Store at least one backup away from the primary drive, and review the archive after upload. A clean, searchable collection is far more useful than a folder full of clips called “final-final-2”.
Practical Recommendations
A concise checklist can keep the documentation process manageable:
- Test cameras, microphones, power, storage and screen exposure during a full technical rehearsal.
- Assign one person to monitor sound and another to note timestamps, actions and technical changes.
- Collect consent before recording, with a clear opt-out path for audience members.
- Photograph the installation empty, active and dismantled, including labels and cable routes.
- Preserve source files, software notes, captions, credits and a short artist statement together.
Good documentation should serve the artwork rather than flatten it into promotional content. Review the final record with the artist, performers and relevant communities, correct credits, and make access conditions clear. Then publish the strongest version through the appropriate archive, showcase or project page so the work can continue to reach audiences beyond its original room.