Review a year of events together and list which subjects keep appearing, which uses were never covered, and what each folder lacks to be found again. Then agree a short, fixed set of labels for every future delivery. A library grows from consistent labelling and clear usage notes, not from collecting more photographs.
A year of company events leaves a lot of photographs and surprisingly few usable ones. Each commission answered its own brief. Put together, they can leave obvious gaps: a leadership team portrait that is two years old, no image of the new production line, nothing that shows the regional offices. This guide helps you plan the collection deliberately. If your immediate problem is finding one photograph again, start with finding event photographs again in a company archive.
What is the library for?
Name the real uses before you design anything. A library built for "everything" ends up serving nothing. Typical business uses are the website, the annual report, recruitment, internal communication, sponsor reporting and press requests. Our overview of using event photographs for business and reporting describes these in general.
Choose the three or four your organisation actually has. Everything else in the plan follows from them.
How do you review a year of events together?
Lay the year out as a simple grid, one row per event.
| Event | Main subjects photographed | Uses that happened | Uses that were missed |
|---|---|---|---|
| Annual dinner | Awards, executives, tables | Report, newsletter | Recruitment |
| Product launch | Product, speakers, guests | Press, social | Website hero |
| Staff family day | Families, activities | Intranet | Culture stories |
| Regional town hall | Presenters, audience | Intranet | Regional office pages |
The grid is hypothetical, but the exercise is real. Read down the columns. Subjects that repeat show your core library content. Missed uses show where the next brief needs to ask for something specific.
What goes missing between separate commissions?
Three things usually do. Subjects are inconsistent, so the leadership team appears in five styles with five background colours. Labels are inconsistent, so one folder is "Dinner 2026 final" and another is "AGM photos new". Usage notes are absent, so nobody knows which images were approved for the website and which were for the internal slide deck only.
Fixing the second and third costs very little. Our guides on file names, folders and corrected versions and organising delivered photographs by session or activity show practical patterns you can ask each photography team to follow.
Which labels are worth keeping?
Less is more. A short, mandatory set beats a long set people skip.
- Event name and date.
- Venue or location.
- Main subject or activity.
- Photographer or team that made the set.
- Usage notes and any restriction, in the words of the approval.
- Approver and approval date.
Add names of individuals only where you have a clear reason and the right to use them. Keep the record of restrictions tidy; our guide on keeping records of agreed image-use restrictions explains what to write down.
How do you brief future events to fill the gaps?
Take the missed-uses column and turn it into briefs. If recruitment had no usable photographs, tell the next event's photography team that two or three people at work images are a priority, subject to the permission of those people. If the regional offices are never shown, plan coverage there on purpose rather than hoping.
Keep gap-filling realistic. A live event cannot produce every library image. Some subjects need their own session. Our guide on deciding between event coverage and a separate portrait session helps you choose.
Who owns the library?
Pick one named person, and a back-up. They keep the folder structure, check that new deliveries carry the agreed labels, and answer questions about what may be used. When that person changes, follow the steps in image handover when staff or agencies change.
Review the library once a year, before the next round of briefs. Our photo archive planner can hold the structure and labels in one worksheet.
Common mistakes to avoid
Three habits slow a library down. The first is collecting everything and describing nothing, which leaves thousands of files with no way to search them. The second is letting every department invent its own folder names. The third is treating the library as a one-off project instead of a yearly routine.
Start small. Ten well-labelled sets are worth more than a hundred loose ones, and a short yearly review keeps the rules alive.
Checklist
- List every event photographed in the past year with its folder location.
- Tally the subjects that appear repeatedly and those that never appear.
- Agree one folder structure and one file-naming pattern.
- Choose five to eight labels that every delivery must carry.
- Attach the usage terms and restrictions to each set.
- Name one person who owns the library and its rules.
- Mark outdated material instead of deleting it.
If you commission several events a year, tell us the subjects your teams keep asking for, and we will help you write the next briefs and delivery labels so each event adds something usable to the same collection.
Plan briefs that build a libraryCommon questions
Do we need special software to build a company image library?
Not at the start. A shared drive with a fixed folder structure, consistent file names and a simple log of usage notes works for many organisations. Dedicated software helps when volume or access control grows, but good labelling comes first, because software cannot fix files nobody described.
How many labels should every image carry?
Keep it small enough that people actually fill it in. Event name, date, venue, main subject, usage notes and the approver are usually enough. Add people names only where there is a clear need and the right to use them, and leave them out otherwise.
Can a library include photographs from different photographers?
Yes, but record who made each set and the usage terms attached to it. Terms can differ between commissions. Ask each photography team to state those terms in writing, and keep that statement with the files so the library does not blur them together.
How do we handle old photographs that may no longer be suitable?
Mark them rather than delete them. Add a note such as superseded, restricted or historical only, with the reason and date. This keeps the record of what happened while preventing accidental reuse of outdated logos, buildings or staff.
Plan briefs that build a library
If you commission several events a year, tell us the subjects your teams keep asking for, and we will help you write the next briefs and delivery labels so each event adds something usable to the same collection.
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: