Early access: features described here are planned. The public demo is an interactive preview with sample data. Live availability and pilot scope are confirmed with the team.
In brief
Event recap report template, in brief
An event recap report is the document an agency sends a client after an activation, sampling, demo or street team shift. It shows who worked, where and when the team was on site, what happened and the photos or other proof that the work was done as booked. A good recap answers three questions fast: did the booked team work the booked hours, what happened on site, and what should change next time.
- Event basics: client, campaign, venue, date and hours.
- Staff roster and attendance, with check-in and check-out times.
- A short event summary in plain language.
- Activity tracking, using only the fields the client asked for.
- Consumer feedback and field notes.
- Photos and proof, captioned with venue and time.
- Issues and resolutions.
- Recommendations and next steps.
What a good recap does
A recap report is the moment a client sees the work. The event happened in a parking lot, a grocery aisle or a campus quad, and the client usually was not there. The recap is how they know the right people showed up at the right time, did what the brief asked and came back with something useful.
A good recap answers three questions fast: did the booked team work the booked hours, what happened on site, and what should change next time. Everything in the template below supports one of those three questions.
Recap, summary or post-event report?
Brands and agencies use event recap report, event summary report and post-event summary report for the same document. Some teams keep a one-page summary for executives and a full recap with photos for the program manager. The structure is the same, so build one template and decide how much of it each client receives.
The template
Event recap report template, section by section
Copy these sections into your report format of choice. Keep the order the same for every event in a program so the client can compare one market or week with the next.
1. Event basics
- Client, brand and campaign or program name.
- Event type: sampling, retail demo, street team, activation, tour stop, campus event or trade show booth.
- Venue name, address and the exact spot the team worked, such as the entrance, aisle or booth number.
- Date, scheduled hours and actual hours.
- Agency contact and on-site lead.
2. Staff roster and attendance
- Each person who worked, with their role (lead, ambassador, sampler, setup crew).
- Check-in and check-out times for each person.
- Breaks, late arrivals, early departures and any replacements, with the reason.
- Confirmation that dress code and required materials were in place.
3. Event summary
Two to four sentences in plain language: what the team did, how the location performed and anything the client should know before reading further. Write this last, even though it sits near the top.
4. Activity tracking
Only track what the client asked for in the brief, and define each field before the program starts so every team counts the same way. Common fields include samples or items handed out, conversations or interactions, sign-ups or scans, product moved where the venue reports it, and inventory received versus inventory left. If a number is an estimate, label it as an estimate.
5. Consumer feedback and field notes
- Common questions people asked.
- Positive and negative reactions, quoted where possible.
- Competitor activity seen at or near the venue.
- Venue notes: traffic patterns, store staff support, signage and display condition.
6. Photos and proof
Ask for the same shots at every event: setup complete, team in uniform, display or table with branding visible, the activation during peak time and breakdown. Name or caption each photo with the venue and time so the client can match it to the roster.
7. Issues and resolutions
Record anything that went wrong and what the team did about it: missing product, a venue that was not expecting the team, weather, a staff no-show and the replacement. Clients trust recaps that report problems honestly more than recaps where every event looks perfect.
8. Recommendations and next steps
Close with what the on-site lead would change: better hours, a better spot in the venue, more or fewer staff, different materials or a follow-up visit. This turns the recap from a receipt into a planning tool for the next booking.
Common mistakes
Why recaps fall apart
Most recap problems start before the event. Fields are not defined in the brief, so one team counts every conversation and another counts only sign-ups. Photos arrive by text message without captions. Check-in times live in a group chat, and the person assembling the report has to piece the day together from screenshots.
The fix is to collect recap inputs as part of the shift itself: check-in and check-out on arrival and departure, photos uploaded to the right event, counts entered in the same fields every time and notes added before the team leaves. When the inputs are structured, the report is mostly assembly. That connects recaps to the rest of the job, from event staff scheduling to event staffing and field marketing team reporting.
Recap questions
Event recap report FAQ
What is an event recap report?
An event recap report is the document an agency sends a client after an activation, sampling, demo or street team shift. It shows who worked, where and when the team was on site, what happened, what the team observed and the photos or other proof that the work was done as booked.
What should an event recap report include?
At minimum: the event basics (client, campaign, venue, date and hours), the staff roster with check-in and check-out times, a short summary of what happened, the activity counts your client asked you to track, consumer feedback and field notes, photos, any issues and how they were handled, and next steps or recommendations.
Is an event summary report the same as a recap report?
In practice, yes. Agencies and brands use event recap, event summary and post-event summary report for the same document. Some teams use summary for a short one-page version and recap for the full report with photos, but the structure in this template works for both.
How soon after an event should the recap go to the client?
Agree on a turnaround with each client before the program starts and put it in the staffing brief. Recaps are easiest to finish while the shift is fresh, so many teams collect the field inputs before staff leave the venue and assemble the report shortly after.
Does ForgeCrew build recap reports automatically today?
Not as a live product yet. ForgeCrew is in early access: branded client recaps built from check-ins, field content and shift notes are a planned workflow, and the public demo is an interactive preview with sample data. An early-access conversation confirms scope and availability for your team.
