Photograph the energy of the day, the teams at work and the presentations, while agreeing in advance how unfinished ideas, screens and judging notes are treated. Many organisers decide that screens and prototypes may be shown only in wide shots, and that judging scores stay off camera. Agree these rules with the organiser and tell the teams.
An innovation day has two speeds. In the morning, teams huddle over laptops and sticky notes. In the afternoon, they stand up and present to people who will decide what happens next. Photography should respect both: the quiet working phase and the performance.
This page belongs to our guide to workplace communication and learning-event photography.
What does an innovation day look like on camera?
A typical day has a briefing, team working time, mentoring conversations, presentations and an announcement. Each phase suits a different type of image.
| Phase | What to photograph | What to watch |
|---|---|---|
| Briefing | Organiser, audience, team formation | Name tags, slides with strategy |
| Working time | Teams discussing, sketching, building | Screens, notes, prototype details |
| Mentoring | Pairs in conversation | Candid advice, personal topics |
| Presentations | Presenters, judges, audience | Slides, demos, unfinished claims |
| Results | Announcement, reactions | Timing of publication |
How do we treat unfinished ideas?
Employees often share ideas that they would not want presented as company decisions. A photograph of a team in front of a slide may suggest management support that does not exist. Ask the organiser how ideas should be described if they appear in captions or stories, and avoid captions that imply approval.
For a related situation in which ideas are submitted for review, see employee pitch and suggestion events.
Screens, code and prototypes
Teams working on screens create a framing problem. A wide shot from behind shows a person at a laptop without revealing the code or design. A close shot from the front may show everything. Agree the approach with the organiser and mention it in the team briefing.
For prototypes, ask each team if they are happy to be photographed with it. Some will be, and some will want to hold back until a patent or internal review is complete. Our guide to projected slides and confidential screens explains the framing options.
An example scenario
For example, a company holds a one-day innovation event with eight teams of five in a large training room. Teams build proposals in the morning, and present for five minutes each in the afternoon to a panel of three directors. The communications team wants photographs for the intranet and a year-end report.
The photographer covers the opening briefing, takes wide shots of teams working with screens turned away, and photographs the presentations from the side. During judging the crew leaves the room. The winners are photographed after the announcement. The communications team checks captions so no proposal is described as approved.
How should we plan the crew?
If teams work in several rooms, one photographer cannot cover them all at once. Our concurrent activity and crew planner helps compare options, and breakout learning groups with concurrent exercises describes how to plan around parallel activity.
Presentations are more predictable than working time, so many organisers book a longer window around the final session. See coverage hours planner to test the options.
What about the energy outside the formal sessions?
Some of the best moments happen between sessions: a team pinning notes to a wall, a mentor drawing on a whiteboard, or a short cheer when a build works. These cannot be scheduled, so a crew that stays through the working phase, rather than arriving only for presentations, finds more of them. If budget limits attendance, choose the window where teams are most active and say so in the brief.
Who should see the images first?
Agree a review step. A team that was photographed mid-argument may not want that image shared, and a judge may not want to be identified before results are public. The organiser reviews the selection, and we deliver the gallery to that person.
What to send us
The agenda, the team list, the room plan and the rules for screens and prototypes are enough to begin. If the event also has external guests, tell us; then the event may overlap with professional meetings and associations in how consent is handled.
Checklist
- Share the day's format, rooms and start and end times.
- Agree how prototypes, screens and whiteboards may appear.
- List team names, members and presentation order.
- Decide when winners may be photographed and published.
- Keep judging scores and notes out of frame.
- Name who reviews images before wider internal release.
Send us the format of your day, the stages of the hackathon and your rules for screens and prototypes, and we will propose coverage that fits the pace of the event.
Plan our innovation day coverageCommon questions
How do we handle screens full of code or designs?
Treat them as confidential unless the team says otherwise. The photographer uses angles and framing that show people working without a legible screen. If a team wants its screen shown, they can say so, and the organiser approves it.
Should we photograph the judging?
Judges deliberating can be photographed from a distance if everyone agrees, but score sheets and rankings should stay out of frame. Many organisers photograph the announcement of results only after the winners have been told.
What if the hackathon runs overnight?
Long, late sessions need a coverage plan. A crew can attend the opening, a mid-point check and the final presentations. Overnight coverage affects the booking, so tell us your hours and what you want captured.
Will every team be photographed?
We plan so each team appears at least once if that is the brief, but it is not guaranteed unless it is stated in the quotation. Give us a team list and the order of presentations.
Plan our innovation day coverage
Send us the format of your day, the stages of the hackathon and your rules for screens and prototypes, and we will propose coverage that fits the pace of the event.
What happens next: You send your event details on WhatsApp. Our team reads the brief, asks what is missing, then confirms in writing whether the date, venue and coverage can be booked, with a quotation. Opening WhatsApp does not send anything, and a message is not a booking until both sides confirm.
Last reviewed: