Write an Event Closure Report PDF

Three days after the gala, your chair asks for "a quick summary for the committee". A quick summary needs attendance, money, what was done and what was not, and what to change next year, and every one of those lives somewhere different. Event Closure Report Maker assembles the factual half from your event project and gives you four boxes for the part only you can write. The result is a PDF or a block of text for an email.

If you are closing the whole event, including certificates and the profit statement, the wrap-up workspace is described in close an event with report and certificates. This guide is about the report itself.

What the report pulls in

The tool reads the project that your other event tools filled, in your browser tab. You tick which of six sections to include, and each one is built from the data, not typed:

• Overview: the event name, the date or date range taken from the programme sessions, the venue and the organiser, which you type.
• Attendance: guests on the list, how many attended, confirmed but not marked attended, invited with no reply, declined, waitlist and plus-ones, then an attendance rate and the count of people to feed or count. The rate is attended divided by attended plus confirmed. If nobody is marked Attended, it says so instead of inventing a number.
• Programme: how many sessions over how many days, with a count for each day.
• Finance: income, costs against budget (and how far under or over), profit and margin, the biggest three cost categories and per-head figures. It also warns about expenses with no category and about entries in other currencies that were left out.
• Tasks: how many tasks are done and the first ten still open with their owners.
• Vendors: vendors on file and the accepted quotes in your currency.

A section with nothing behind it is left out, so an event without vendors does not get an empty heading.

What you write yourself

Four text boxes, each taking one point per line: Highlights, What went wrong, Lessons and recommendations, and Thanks. Leading dashes and bullets are stripped and each line becomes a bullet in the PDF, so you can paste a list from anywhere. The first three are what a committee actually reads. The tool cannot know that the shuttle was late or that the sponsor banner hid the registration desk, so say so in plain words.

Other fields: the report title (the default is the project name followed by "closure report"), venue, organiser and a colour for headings. The PDF subtitle joins venue and organiser, the footer carries the project name with page numbers on longer reports, and the paper follows the project setting, Letter or A4.

A worked example: a 140-guest gala

A club's Harvest Gala had 140 people on the list. After the event the organiser marked 112 as Attended; nine stayed Confirmed, eleven never replied, six declined and two were waitlisted. Fourteen confirmed or attended guests brought a plus-one. The preview reads:

• Attendance: 93% of those expected (112 of 121), and 135 people to feed or count.
• Programme: one session over one day.
• Finance: income $31,600.00, costs $24,350.00 against a budget of $26,000.00, which is $1,650.00 under. Profit $7,250.00, 22.9% of income. Biggest costs: Venue $9,800.00, Catering $8,400.00 and AV and Production $3,100.00. Per head: cost $180.37, income $234.07.
• Tasks: 1 of 2 done, with "Send thank-you notes (Dana)" still open.

The organiser then types the human part, one line each:

• Highlights: the silent auction raised more than the ticket line; doors opened on time.
• What went wrong: the coat check queue reached the street; two vegetarian meals were swapped between tables.
• Lessons: add a second coat desk at 120 guests or more; label meals by table number.
• Thanks: the volunteer team and the venue manager.

The finished report is a clean two-pager that a treasurer, a sponsor and the next year's chair can all use.

Steps

1. Open your saved project, or work in the same tab as the planning. Mark attendance in Guest List Tracker, enter the final expenses and tick finished tasks in Event Checklist Planner.
2. Check the money in Event Profit Ledger; the finance section uses the same figures.
3. Open Event Closure Report Maker. Enter the title, venue and organiser, and choose a colour.
4. Untick sections the reader does not need. A sponsor may want attendance and finance only.
5. Write the four note boxes while the event is fresh, one point per line.
6. Read the preview from top to bottom. It is exactly the text that goes into the PDF.
7. Press Copy text for an email body or Download PDF. The PDF is named event-closure-report.pdf.
8. Save the project so the report can be rebuilt after a late invoice.

Copy text is not metered; the PDF download counts as one usage. Event Closure Report Maker is a Professional Tool with 10 trial uses a day before a day pass or plan applies.

Common mistakes

Building the report before attendance is marked, which leaves the attendance section without a rate. Letting the finance section run before the last invoice arrives; rebuild after it. Putting names of guests with allergies or access needs in a report that goes to sponsors; the report carries counts only, so keep your notes the same way. Writing paragraphs in the note boxes instead of short lines, which makes dense bullets. Leaving every section on by default when the reader is a sponsor who never asked about your tasks.

Summary

Get the project honest first, then let the tool assemble attendance, programme, finance, tasks and vendors, and spend your own effort on the lines that explain them. Open Event Closure Report Maker, write the highlights, problems and lessons, and download the PDF. For the rest of your toolkit, see the event tools.

Open Event Closure Report Maker→

Would a comparison with last year's event help your committee more than a single report? Tell us on the contact page.