Keep the review light. Compare what you asked for in the brief with what people actually requested, downloaded or published, and note the gaps. Use that to improve the next brief. Treat the pattern as a prompt for questions, not as proof that a photograph worked or failed, and avoid collecting data about individuals.
After an event, the gallery goes out and the requests begin. Some photographs are asked for repeatedly. Others are never touched. This guide shows how to learn from that pattern in proportion to the event, so that the next brief asks for what your people really need. It builds on reviewing photography against the original business brief, which looks at the delivery itself.
What are you trying to learn?
Decide the question before you collect anything. Three questions are usually enough.
- Did the brief ask for the right kinds of photographs?
- Which requests came after delivery that the brief did not anticipate?
- Which parts of the gallery were hard to find or hard to use?
Notice that none of these asks "which photograph was the best". Quality judgements belong in the gallery review. This page is about use.
Where does the evidence come from?
Use what already exists. You do not need new systems.
| Source | What it shows | Caution |
|---|---|---|
| Requests to the communications team | Which images people asked for and for what purpose | Reflects who asked, not who needed |
| Published items (newsletter, intranet, report) | Which photographs were chosen for output | Choice may reflect speed or availability |
| Designer or agency queries | Where the handover or labelling was weak | Small sample |
| A short check-in with requesting teams | What was missing, what was unused | Depends on honest, brief replies |
| Gallery or download counts, if your platform gives them | Rough interest by folder | Not a measure of value |
Why popularity is not proof
A photograph can be used often because it is the only clear image of the chief executive, because it was at the top of the folder, or because the deadline was tight. A photograph can be unused because nobody knew it existed, or because a restriction kept it off a channel.
So write findings as observations with a reason, for example: "The stage photographs were requested by three teams; the table photographs were requested by none, possibly because the folder was not labelled by table." That wording keeps you honest and points to a fix. For outcomes you did not measure, such as engagement or attendance, avoid claiming a link to the photographs. Our guide on separating attendance evidence from promotional storytelling explains the same caution.
How to keep the review proportionate
For one dinner or workshop, an hour is enough. Open the brief, open the gallery, list the post-event requests and ask two or three colleagues what they used. Write down what you would change.
Avoid collecting information about named individuals, such as who opened which file. It rarely helps the brief and creates personal data you would need to protect. If you are considering anything at individual level, check with your legal or data protection contact first. Our privacy and image-use guide covers keeping records of restrictions without over-collecting.
A hypothetical example
Suppose a company annual dinner brief asked for award moments, executive portraits and table candids. After delivery, requests come from four places: HR wants long-service recipients, sales wants the dealer table, the intranet team wants wide room shots, and the sustainability team wants the new recycling stations.
Three of those four were not in the brief. The review does not conclude that the original brief was wrong. It concludes that next year's brief should list the four requesting teams in advance, ask each for two must-have images, and ask the photography team how those can be fitted into the run sheet. The rules for must-have moments help here.
What do you do with the findings?
Turn them into three concrete changes for the next brief, such as naming extra requesting teams, asking for clearer folder labels, or clarifying how selections are made. How the team chooses photographs for the final gallery is explained in our guide to how event photographs are selected.
Keep the note with the event file. When you later plan a library from a year of events, these notes show which gaps repeat. The post-event image use planner can hold the same information in one place.
Checklist
- Put the original brief and the delivered gallery side by side.
- List every request received after delivery and who made it.
- Note which uses were planned and which were unplanned.
- Record what people could not find or could not use, and why.
- Check usage restrictions before reading too much into popularity.
- Write three changes for the next brief.
If you have a past gallery and a sense of what went unused, send us the original brief and a short note on what your teams wanted instead, and we will help you turn it into a sharper brief for the next event.
Improve our next photo briefCommon questions
Is it enough to ask colleagues which photographs they used?
It is a good start. A short message to the three or four teams that requested images, asking what they used and what they could not find, gives you most of the useful answer. You do not need a survey or a dashboard for a single event.
Can we say a photograph performed well because it was shared a lot?
Be careful. A photograph may be shared because it was the only one of a leader, because it came first in the folder, or because it suited a deadline. Sharing shows what was convenient or chosen, not necessarily what worked. Use it as a clue and say so plainly in any report.
Should we track which employees opened or downloaded which images?
Usually not. Counts by folder or request type answer your brief questions. Tracking named individuals adds personal data you may then have to justify and protect. Ask your data protection or legal contact before logging anything at individual level.
How often should we run this review?
Once after each significant event, and once a year across the whole year of events. The first tells you what to change in the next brief. The second shows repeat gaps that a single event cannot reveal.
Improve our next photo brief
If you have a past gallery and a sense of what went unused, send us the original brief and a short note on what your teams wanted instead, and we will help you turn it into a sharper brief for the next 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: