Student hackathon photography

At a hackathon, most of the work is done by people staring at laptops. A photographer who follows the clock will produce a gallery of screens and tired faces. A photographer who follows the structure of the event will find the teamwork, the mentor conversations and the nervous final minutes.

This page belongs to our overview of youth-programme and student-competition photography. It looks at what makes a useful hackathon record and what to protect.

What is the meaningful record of a hackathon?

The meaningful record shows people working together, getting help and presenting what they built. It is not the code. Typical moments include:

• The opening briefing and the energy in the room.
• Teams forming and agreeing on a plan.
• A mentor or judge crouching beside a table to talk.
• A whiteboard sketch, a prototype or a device on a desk.
• Late-night concentration, with permission.
• Demonstrations and the final presentation.
• The winners, runners-up and the room afterwards.

Planning windows instead of continuous coverage

A twenty-four-hour event does not need twenty-four hours of photography. Our coverage hours planner helps you decide which windows matter. A common structure is the opening, a mid-event checkpoint, the demonstration or pitch block, and the awards.

For overnight sessions, ask the organiser whether photographs are welcome at all. Tired students and sleeping areas are sensitive, and a short, agreed window usually works better than someone wandering around at 3am. If you think an overnight window is needed, ask us whether it can be included.

Protecting screens, accounts and unapproved project material

Hackathon screens may contain credentials, personal data, messages or ideas that teams do not want shared. A photograph of an open browser tab can be more revealing than it looks. Brief the photographer on three levels:

Item	Suggested rule
Login pages, tokens, personal messages	Never photographed in readable form
Project screens and prototypes	Photographed only with the team's agreement
Whiteboards and sticky notes	Photographed with agreement; ideas may be unreleased
Team members working	Photographed, from angles that avoid screens

Our guide to venue permission, participant permission and photographer terms explains how these layers fit together. Where a project uses licensed or third-party material, check with the organiser before anything is published. Read our guide to copyright ownership and permission to use event photographs for the general principles, and confirm specifics with the organiser or a qualified adviser, because event labels alone do not settle the question.

Sponsors, mentors and judges

Hackathons often have sponsors and industry mentors. Their branding and presence are part of the story, but each may have its own rules. Our sponsor photography checklist helps you set expectations before the day. Tell us who needs to be photographed, who must not appear, and whether sponsor logos should be visible in presentations.

Participants who are minors or sensitive about appearing

Student events often include participants under 18, and some adult participants prefer not to be photographed. The organiser should tell us in advance who has opted out, and agree a discreet signal for changes on the day. Our team then avoids those participants without drawing attention.

A hypothetical example

For example, imagine a one-day school hackathon with 10 teams, an opening briefing, a lunch break, a mentor round and final pitches. The organiser asks for no readable screens, and for sponsor logos only on the stage banner.

A plan could cover the opening, a brief walk through the working room, mentor visits, the final pitches and the awards, with team portraits at the end. The photographer would avoid screens, and any team that asks for a break from photography would get one. A short delivery checklist would state which images go to the organiser and which can be shared with teams.

What to tell the photographer

• The event timeline, with key blocks and breaks.
• Venue layout, working areas and rooms that are off limits.
• Your rules on screens, accounts, project material and sponsors.
• Who must not be photographed, and how to signal changes.
• How images will be reviewed and used afterwards.

You can record usage decisions in our image-use and approval register so teams and sponsors can see what has been agreed.