Post-event report: define your MICE tracking.

Start with the decision the report should support.

Choose the questions your report should answer: which services need confirmation, which invoices are missing or which changes in scope need explaining? A useful indicator should lead to an identifiable action or check.

Define the scope, unit, source, update frequency and owner for each indicator. Without these references, a figure can mix events, quotes and statuses that cannot be compared.

• Name the decision needed.
• Describe the events and services included.
• Assign a source and owner to each indicator.

Distinguish forecast, commitment, invoice and payment.

An indicative estimate, received quote, confirmed order and invoice represent different statuses. Keep separate columns and a reference date rather than adding successive documents for the same service.

Keep the currency and tax presentation. Explain headcount, duration or inclusion changes before commenting on a difference. Do not add a deposit to the total cost a second time; it also belongs to the payment schedule.

• Separate statuses and their corresponding amounts.
• Avoid counting a quote and invoice twice.
• Compare only documented scopes and units.

Track open questions service by service.

An event may have a confirmed venue while catering still needs clarification. Prepare a status for each service, including its latest update, blocker and next action. Keep existing suppliers and agreements within the actual tracking scope.

In the Sourcing Force arrangement, BME acts as the single supplier; services keep separate statuses. Confirmation requires the corresponding official purchase order. The public brief prepares the request and creates neither a purchase requisition nor an order; it does not automatically feed an operational dashboard.

• Identify the service and reference version.
• Distinguish a proposal from a confirmation.
• Specify who handles each open question.

Add a review linked to event objectives.

A deliverable, prepared decision or summarised feedback can complement spending tracking. Specify the collection method and limits: a qualitative assessment is neither evidence of savings nor a return-on-investment calculation.

ADEME includes review within continuous improvement of events. Select topics actually tracked, using available information and its provenance; an environmental intention or missing data does not become a measured result.

Reference: ADEME · Responsible events.

• Link quality indicators to the initial objective.
• Distinguish observation, estimate and measurement.
• Plan the review and its limits from the outset.

Prepare a shared view without unnecessary data.

Fictional example: the venue is confirmed, a catering invoice is awaited and a headcount change needs explaining. The report assigns an action to each point; it does not declare the whole event closed because one service is complete.

CNIL highlights purpose limitation and data minimisation. Prepare a summary for authorised recipients without unnecessary individual data. Describe the tracking needed and entrusted services in your brief rather than copying invoices, bank details or internal files.

Reference: CNIL · Six GDPR principles.

• Show the update date and unconfirmed points.
• Choose recipients and necessary information.
• Request a quote for the tracking scope needed.