The event is judged on its file as much as its day
A training workshop for a donor-funded programme produces two outputs. One is the session itself. The other is a file: an attendance record that matches the approved participant list, a payment record that reconciles to it, photographic evidence, and a financial reconciliation that ties every cost back to the budget line that authorised it.
Teams that plan only the first output tend to discover the second in the week after the event, when participants have dispersed and signatures cannot be obtained. Treating the file as a deliverable with its own owner — decided at planning, not at closeout — is the single change that most reduces the effort an event costs.
This guide covers running the event and closing it out. Writing the request for quotation, and comparing what organisers quote, is covered in the event management RFQ and budget template.
Participant logistics decide the attendance rate
Where participants travel in from districts, the variables that determine whether they arrive are transport, accommodation and allowance clarity — usually in that order. An invitation that leaves any of the three ambiguous produces both no-shows and disputes on the day, and both damage the attendance record the programme needs.
The practical approach is to confirm, in the invitation itself, how the participant will travel, where they will stay, what will be paid, on what basis and against what documentation. This is administrative work that sits awkwardly between the programme team and the event organiser, and it should be explicitly assigned rather than assumed.
For multi-province events, travel time compresses the usable agenda more than planners expect. Participants arriving from distant districts on the morning of a one-day session will arrive late or not at all; either the event becomes a two-day event with an arrival day, or the catchment narrows.
Choose the venue against the operation, not the brochure
Venue selection for institutional events is mostly a suitability check rather than a preference. Capacity at the actual seating layout, access for participants arriving by road, power reliability, whether the room can be set up for interpretation, whether catering can be produced on site, and whether the space can host a registration desk without creating a queue outside — these decide the day.
Capacity at working layout
Rooms are quoted at theatre capacity; a training session in cabaret or U-shape layout holds substantially fewer people.
Registration space
Somewhere to run attendance controls that is not the doorway, especially where allowances are paid on arrival.
Power and audiovisual
Reliable power for sound, projection and interpretation equipment, with a fallback arrangement.
Catering on site
Meals and refreshments produced or delivered without moving participants off site mid-session.
Access and safety
Approach roads, parking for participant transport, and a layout that suits the profile of the attendees.
Interpretation setup
Space and equipment for Dari, Pashto and English interpretation where the audience needs it.
Put payments and attendance under one team
Where per diems or transport allowances are paid to participants, the attendance record and the payment record describe the same people on the same day and must reconcile exactly. Splitting them between an event organiser and a separate finance arrangement creates two lists that have to be matched afterwards, and any mismatch becomes an audit question.
Running both under one team does not remove the reconciliation; it moves it to the day itself. The person verifying identity at the registration desk is the person producing the acknowledgement, so attendance, payments and cash are reconciled at the end of each day, with every difference explained and signed for, rather than matched in the following month. The worked example below shows how. Zhikal delivered 27 workshop days across five provinces under a single cash-disbursement and event-management contract, covering venue, catering, participant transport allowances, sound, media and IT equipment, with a payment record for every disbursement. The event management and cash administration pages describe how the two services combine.
What should the closeout file contain?
The file is easiest to produce when its contents are agreed with the funder before the event and each item has an owner. For a multi-day workshop with participant allowances, the usual set is:
Approved participant list
The version the event ran against, with any substitutions and the rule that allowed them.
Daily attendance sheets
Signed by each participant for each day attended, matching the approved list.
Allowance and per-diem schedule
Rates, eligibility and individual signed or thumb-printed acknowledgements, reconciled daily.
Travel and accommodation records
Who travelled, how, and where they stayed, against the confirmation each participant received.
Supplier invoices
Venue, catering, equipment and interpretation, each tied to the budget line that authorised it.
Photographs and closeout report
Dated evidence of the sessions and a report reconciling planned against actual attendance and cost.
Who owns each record
Every record in the file needs one person who prepares it, one who checks or approves it, and an agreed place where it is kept. Settle this in the contract or the event plan, not on the day:
| Record | Prepared by | Checked or approved by | Kept by |
|---|---|---|---|
| Approved participant list | Prepared byProgramme team | Checked or approved byProgramme manager | Kept byBoth; the organiser keeps the version used |
| Substitution approvals | Prepared byProgramme focal point, in writing | Checked or approved byProgramme manager | Kept byThe organiser, with the list |
| Daily attendance sheets | Prepared byOrganiser's registration desk; each participant signs | Checked or approved byProgramme focal point, each day | Kept byThe organiser until closeout, then you |
| Allowance schedule: rates, eligibility | Prepared byProgramme team | Checked or approved byAt your organisation's authority level | Kept byBoth |
| Payment acknowledgements | Prepared byOrganiser's paying officer; each participant signs or thumb-prints | Checked or approved byA second person at the desk | Kept byThe organiser until closeout, then you |
| Daily reconciliation and exception log | Prepared byOrganiser | Checked or approved byProgramme focal point, signed each day | Kept byThe organiser until closeout, then you |
| Travel and accommodation records | Prepared byOrganiser | Checked or approved byProgramme focal point | Kept byThe organiser until closeout, then you |
| Supplier invoices | Prepared byVenue, caterer, equipment and interpretation suppliers | Checked or approved byOrganiser, against what was confirmed | Kept byThe organiser, then you |
| Photographs | Prepared byOrganiser, under your consent rules | Checked or approved byProgramme focal point | Kept byAs the contract's data terms say |
| Closeout report | Prepared byOrganiser | Checked or approved byProgramme manager | Kept byYou |
Payment and attendance records carry personal data. Agree who may see them, how they are handed over and when the organiser's copies are destroyed.
Reconciling attendance and payments: a worked example
The figures below are invented to show the method; they describe no real event and contain no personal data. Participants are identified only by list number.
Invented example. A two-day workshop with 40 participants on the approved list and a daily allowance under the programme's written rule: paid only for a full day attended. The organiser prepared cash for the whole list each morning.
| Check | Day 1 | Day 2 | Both days |
|---|---|---|---|
| On the approved list | 40 | 40 | |
| Signed the attendance sheet | 37 | 36 | 73 participant-days |
| Allowance paid and acknowledged | 37 | 35 | 72 |
| Difference to explain | 0 | 1 | 1 |
| Cash prepared, in daily allowances | 40 | 40 | 80 |
| Cash paid out | 37 | 35 | 72 |
| Cash returned and counted by two people | 3 | 5 | 8 |
The difference on day 2 goes on the exception log, signed by the programme focal point that evening:
| Day | List no. | Exception | Rule applied | Decided by |
|---|---|---|---|---|
| 2 | 23 | Signed in, left before the afternoon session | Full day required; no allowance due | Programme focal point |
| 1–2 | 08, 31, 35 | Did not attend | No allowance due | Recorded at the desk |
| 2 | 14 | Did not attend day 2 | Day 1 paid only | Recorded at the desk |
Attendance, payments and cash each reconcile to the list, and every difference has a rule and a name beside it. The closeout report repeats the totals; the file holds the signed sheets behind them.
A planning checklist that holds up in the provinces
The items below are the ones that most often go missing when an event is organised remotely, and each of them has an owner who should be named at planning.
Approved participant list, locked
With a stated rule for substitutions, since a list that changes on the day breaks both the attendance and the payment record.
Travel and accommodation confirmed per participant
Not aggregated — an unallocated block booking is where individual participants fall out.
Allowance basis stated in writing
Rate, eligibility and required documentation communicated before travel, not explained at the desk.
Materials produced and delivered ahead
Printing, banners and handouts on site the day before, particularly outside Kabul.
Interpretation arranged for the actual audience
Confirmed against the participant list rather than assumed from the location.
Evidence pack defined
Attendance sheets, photographs, payment acknowledgements and the closeout report format agreed with the funder in advance.
Closeout checklist
Event closeout checklist
Completed by the organiser and checked by the programme focal point before the final invoice.
The event
Event and reference
Place and dates
Organiser's lead and programme focal point
Participants and attendance
The approved participant list used on the day, with every substitution approved in writing
Daily attendance sheets, signed, one per day, matching the list
- Planned against actual attendance, by day
Payments
- The approved allowance schedule: rates and eligibility
An acknowledgement for every payment, signed or thumb-printed
A daily reconciliation of attendance, payments and cash, signed
- The exception log, with the rule applied and who decided
- Cash returned, counted by two people and recorded
Costs
Supplier invoices for venue, meals, rooms, transport, equipment and interpretation
- Each invoice tied to the budget line that authorised it
Planned against actual cost, line by line, with differences explained
Evidence and report
- Dated photographs taken under the consent rules
- Travel and accommodation records against each confirmation
- Closeout report issued in the agreed template
Personal data handed over and the organiser's copies dealt with as agreed
Sign-off
| Name | Signature | Date | |
|---|---|---|---|
| Prepared by (organiser) | |||
| Checked by (programme focal point) | |||
| Accepted by (programme manager) |