Reviewing a recurring programme before the next commissioning cycle

Recurring programmes tend to repeat themselves. The brief from last year is reused, the same events are covered, and a renewal happens by habit. A short review before the next cycle gives you a chance to correct what did not work and to drop what nobody used.

This page belongs to our guide on agency and recurring event-photography commissions. It sets out a review method based on evidence.

What is the review for?

A good review answers three questions: Did the programme do what we asked? Did the outputs get used? What should change? It is not a contest between suppliers and not a forecast of results. It is a way to turn a year of experience into a better brief.

Our guide to reviewing photography against the original business brief covers the same idea for a single event, and the post-event photography review worksheet provides a structure you can repeat across events.

Gather what you hold

Collect the records that already exist:

1. The master brief and any event briefs.
2. The scope-change log, showing what was added or dropped.
3. Delivered galleries and delivery dates.
4. A list of images actually used, and where.
5. Written feedback from approvers and users.
6. Notes on problems, with causes.

If some of these were not kept, note that as a finding. Starting a record this cycle is an improvement in itself.

Find out what was used

An archive full of images is not the same as a set of useful images. Ask the teams that use photographs which ones they chose and why. Our guide to learning which event photographs people actually use explains simple ways to do this, such as a tally by image type.

You may find that group photographs, speaker portraits and venue shots were used again and again while candid wide shots were not. That tells you where to put hours in the next cycle.

Compare against the scope

Lay the original scope beside what happened:

Scope item	What happened	Keep, change or drop
Events covered
Hours per event
Crew size
Deliverables
Delivery times
Approvals

The right-hand column is the output. Each "change" or "drop" needs a short reason.

A worked example

For example, an agency has managed twelve monthly staff events for a client. At the end of the cycle, the agency reviews the log. Two events needed extra hours because programmes ran long. Previews were rarely opened, but the group photographs were used in every internal newsletter. Approvers changed twice, and one delivery was delayed because a selection decision was missing.

For the next cycle, the agency proposes slightly longer coverage windows for two event types, a smaller preview set, a standing list of group photographs, and a named approver per event. It records the reasons so the new brief is traceable. No claim is made about business results, only about what the evidence shows.

What to leave out

Avoid ranking suppliers against each other without evidence, and avoid promising commercial returns. Photography supports records and communication. Its effects on sales or reputation depend on many factors. State what the images enabled, for example "the report was prepared sooner", and stop there.

Update the structure, not just the scope

A review should also refresh the machinery of the programme: the approver record, the file naming, the archive and the calendar. See recurring assignments with changing end-client approvers and recurring photography with only some dates confirmed. A multi-event photography commission organiser keeps the calendar and briefs in one place.

For cost, look at how a multi-event commission is priced in our guide to pricing a multi-day photography commission.

What we confirm with you

Once you share your review, we confirm in writing the proposed scope for the next cycle, what changes from the last, and how dates, venues, crew and deliverables will be confirmed for each event.