To report event outcomes to leadership, write one page: the purpose, five numbers with denominators and dates, the cost per attendee, three lessons and the decision you need. Pull every number from an export so that anyone can trace it, and attach the detail separately.
What leadership actually reads
Senior readers give an event report about two minutes. They want to know whether it did what it was meant to do, what it cost, and whether to do it again. A twenty-slide deck with a gallery of photos answers none of these quickly. A good one-pager does.
The context makes this more important than it used to be. Gallup reports that only 23% of Indian employees were engaged in 2025, with Indian managers’ engagement falling from 39% in 2024 to 30% in 2025 (Gallup, 2026). People who sign off event budgets are aware of it, and they will ask whether the event reached the people it was designed for.
Step 1: agree the questions before the event
Meet the sponsor a week before and ask: “On Monday morning, what will you want to know?” Write the answers down. Typical ones: did the right people come, did they take part, what did they think, what did it cost, and what should we change. These questions become the structure of the page.
Step 2: pull the numbers from the system
Do not retype numbers from memory. Export them. Attendance by activity, sign-ins against the member list, participation by module, feedback completion, and any programme-specific counts such as submissions approved. Keep each export with its date and filter, so you can show where a figure came from.
For a recurring programme, set a cadence. A weekly or monthly export, shared to a sheet the leadership can open, saves rebuilding the report each time.
Step 3: use the one-page structure
| Block | Content | Length |
|---|---|---|
| Purpose | One sentence, agreed in advance | One line |
| Five numbers | Activation, attendance, participation, feedback, one business outcome, each with denominator and date | Five lines |
| Cost | Total and cost per attendee, with a note on what is included | Two lines |
| What worked | Three specifics, with a number or example | Three lines |
| What to change | Three specifics, with owners | Three lines |
| Decision needed | One ask: approve repeat, change budget, adopt format | One line |
Resist adding a fourth lesson. If everything is a finding, nothing is.
Step 4: show the numbers honestly
Every number needs its denominator: “612 of 700 invited signed in.” Every percentage needs a date. Where a number is low, say so and explain. Where you do not have data, say that too. A report that admits what it cannot show is more believable than one with a tidy chart.
Avoid vague phrases like “high engagement” and “great feedback”. Replace them with a count and a quote: “198 of 240 completed the feedback form; here are the three themes.”
Step 5: add a small number of quotes and one picture
One or two direct quotes from participants, with permission, humanise the numbers. One photo or a screenshot of the leaderboard adds colour. Do not fill the page with images; the numbers are the report.
Step 6: send it early, and keep the detail ready
Send the page within a week of the event. Attach an appendix of exports for anyone who wants to check. Be ready to talk through any number; the person who asks “where does this come from?” should get a clear answer in seconds.
If the event is part of a recurring programme, add a trend line: last quarter versus this quarter, with the same definitions.
Step 7: close the loop
End with the decision you need and a date. Then record what leadership decided, so that next time you start from it. A report that produces no decision has not done its job.
Common mistakes
Mixing definitions. If you changed what “participation” means between events, say so, or do not compare.
Reporting only the good news. Leaders learn to distrust reports that never mention a problem.
Burying the cost. Put it on the page, next to the outcomes.
Treating the app’s counts as the whole truth. They record what happened in the app. Offline conversations, hallway deals and sentiment need a different instrument.
A sample one-page layout in words
Top line: the purpose, in the sponsor’s own words. Left column: five numbers, each with its denominator and the date it was read. Right column: cost, total and per attendee, with one line on what is included. Below: three things that worked, each with a figure or a quote, and three things to change, each with an owner and a date. Footer: the decision you need, such as approving a repeat next year, and the date by which you need it. Keep the font readable on a phone, because many senior readers open the file there first. Send the exports as a separate attachment, and name each file with the occasion, the data set and the date.
For a recurring programme, add a second page only if the cycle changes: a trend table with the same five measures across the last four cycles, each cell carrying its denominator. Readers should be able to see in ten seconds whether the programme is improving, flat or slipping. If a measure changes definition between cycles, mark the break clearly and restate earlier figures on the new basis where the data allows. When it does not, say so, and avoid drawing a line across the break.
How Sociana handles this
Reports and exports cover attendance (with scanner and time), game and score exports, hospitality exports, step reports and ticket exports, and activity logs record who changed what in the admin panel. In-app mobile dashboards show live counts, user-wise submissions and timeline moderation to Owners and Managers. For teams that report elsewhere, webhooks, Sheets and Airtable send selected data sets to a spreadsheet the client owns, configured with the Sociana team per occasion. The timeline feed holds the posts you may quote.
Integrity Champ is a recurring ethics and compliance ambassador programme that Carlsberg India runs on a Sociana multi-occasion app: employees submit proof, managers approve from their phones, approved work earns points, and quarterly leaderboards rank the cycle. Its recorded lesson: approval queues worked from a phone keep a recurring programme moving between events. Read the Integrity Champ case study. Note that Sociana provides reports and dashboards per occasion, not a portfolio BI layer across events.
Frequently asked questions
How long should an event report be?
One page for leadership, with an appendix for detail. If you need more than a page, the purpose is probably unclear.
Should I include photos?
One or two. The numbers carry the report, and photos belong in the gallery.
How often should a recurring programme report?
At the cadence of the programme’s decisions: monthly for a monthly review, quarterly for a quarterly cycle. Use the same definitions each time.
What if the numbers are disappointing?
Report them, explain the cause and propose the change. A low number with a plan is more useful than a missing number.
Related reading
Glossary: participation rate, activation rate, submission, tournament. Occasion hubs: corporate annual meets, employee programmes and recurring communities. Use the calculators and templates and checklists for a report layout.