How to evaluate suppliers after a paid event

The event's finished, your production lead says the crew were brilliant, and finance wants to know why the final invoice is higher than the quote. Meanwhile, you're still thinking about the session that started late. Which of those things should decide whether you book the supplier again?

Evaluate event suppliers against the work you agreed, the evidence of what they delivered, and the full cost of getting that result. Then hear their explanation before deciding whether to rebook them, require specific changes, or pause further bookings. A friendly crew can still miss an essential requirement. A higher invoice can be entirely justified by changes you approved.

The useful outcome is a booking decision you can explain. You should know what went well, what failed, who could have prevented it, and what would need to be different next time. Here's how to reach that decision without turning every supplier review into another production project.

Start with what you actually agreed

The first thing you want to do is find the final accepted scope. That means the quote or contract you approved, the relevant brief, and any changes agreed afterwards. Reviewing the first quote while ignoring a later approved change can make correct delivery look like a failure.

Say you initially requested two technicians until the end of the afternoon. You later added an evening session and approved another technician. The original staffing price is still useful for understanding how spending changed, but it isn't the complete standard for judging the final invoice or crew attendance.

Write each important expectation in terms you can check. Equipment arriving and equipment being ready for rehearsal are different milestones. Catering delivered to the loading entrance and meals ready for attendees are different results. Use the milestone the supplier accepted, including any work your team had to finish first.

Our event production brief template can help you find the requirements that mattered to delivery. For this review, work from the version used at your event. Improvements you wish you'd included belong in the next brief; they don't become promises the supplier made retrospectively.

Separate an agreed requirement from an assumption. If nobody specified whether the engineer would remain during the networking session, record that uncertainty. You can still decide that you need longer coverage next time. Calling the supplier unreliable for leaving at the booked time won't resolve the missing agreement.

New Zealand Government Procurement's guidance on conducting contract reviews includes comparing delivery, charges and quality with what was agreed. It concerns public purchasing, so we're adapting the review questions here, rather than applying government procurement rules to your event business.

Collect evidence from the people who saw the work

Ask the person responsible for the service to write their account while they can still distinguish what happened from what they later heard. Your production manager can describe rehearsal readiness. The door supervisor can describe arrival coverage. Finance can reconcile charges, but probably didn't see the loading entrance at setup.

Useful evidence includes the agreed running order, access records, crew sign-in notes, delivery confirmations, incident reports and messages approving changes. Gather the records needed to answer a disputed question. You don't need to export every conversation or ask everyone to write a report about an uneventful chair delivery.

For each concern, record what happened, when it happened, what supports the account, and what effect it had. "The team were disorganised" gives the supplier little to answer. "The replacement microphone arrived after the first session ended" describes a problem you can investigate against the equipment and support arrangement.

Keep the original record available for anyone checking your conclusion. A summary is helpful for the review, but someone should be able to check the message or log behind it. When records conflict, retain the conflicting accounts and name the missing information. Don't quietly choose whichever version supports the decision you already wanted to make.

Take care with attendee complaints. A complaint about poor sound tells you someone had difficulty hearing. It doesn't establish whether the cause was the sound system, a speaker holding the microphone badly, or noise from an adjacent room. Ask where the attendee was and which session they mean before assigning responsibility.

Also distinguish several reports from several incidents. A door supervisor, customer-support assistant and attendee may all describe the same delayed shuttle. Their accounts can help establish the sequence, but counting them as separate shuttle failures exaggerates what happened. Preserve the number of people affected only when your records support it.

For routine services, a short written review may be enough. Give more attention to services whose failure affected safety, stopped the programme or created substantial cost. The size of the invoice alone won't tell you which supplier deserves the closest examination.

Judge delivery before judging how much you liked the crew

It's easy to remember the supplier who answered your late call and forget the one whose work needed no intervention. Start with delivery itself. Did attendees receive the service you sold them? Did the supplier meet the accepted quality, quantities, hours and readiness requirements?

Consider a paid workshop where every participant needs equipment. Supplying the correct total quantity isn't enough if some units don't work. Your review should explain how many usable units were available, whether the supplier corrected the shortage, and what participants could actually do while they waited.

Then look at coordination. Did the supplier send the information other teams needed? Did the crew supervisor raise a delay early enough for you to change the plan? Were replacements or substitutions discussed with the person authorised to accept them? These behaviours matter because they affect what your team can prevent.

You should recognise good recovery. A technician who identifies a failing unit before doors and installs the agreed spare has done useful work. Record the fault and the successful response. Otherwise a review that counts only visible problems can discourage suppliers from telling you about things they caught themselves.

Recovery doesn't erase the original failure. If a supplier repeatedly needs emergency replacements for equipment that should have been checked, your team is still carrying uncertainty. Ask whether this was an isolated defect or evidence that preparation needs to improve. The answer affects the conditions of another booking.

Keep technical judgments with someone qualified to make them. As the organiser, you can record that a session lost sound and how delivery suffered. You may need an independent specialist to establish why a system failed or whether a proposed fix is suitable. A confident explanation from either side isn't technical verification.

Include successful decisions in the evidence you retain. Perhaps the supplier recommended an earlier rehearsal, checked the presentation files and discovered that a video wouldn't play. If that preparation prevented a problem, record what they checked and when. A review that mentions only the final smooth session leaves your next event lead unable to see which preparation they should preserve.

Be specific when you share that feedback with the supplier. Tell them that the advance file check helped your speakers rehearse with working media, and ask for the same preparation in the next scope. If it required extra paid time, retain that cost when comparing a different proposal. Otherwise you can remove the work that made delivery reliable, choose a cheaper scope and wonder why the next event needs more help on the day.

Ask questions that match the service

A common review format helps your team find the evidence, but identical measurements can produce poor judgments. The requirement that matters for a security contractor won't necessarily tell you anything useful about a caterer. Start with the result each supplier was actually responsible for, then examine how they delivered it.

For security, your competent event lead should review the agreed positions, supervision, briefings and incident response against the actual arrangements. A quiet evening doesn't establish that every position was covered. Likewise, an intervention doesn't prove poor performance; it may show that staff recognised a problem and responded as intended.

For catering, compare the accepted quantities and service window with what attendees received. An unused meal isn't automatically waste caused by the caterer if you guaranteed that quantity. A shortage isn't automatically their fault if your team gave them the wrong confirmed count. Review substitutions and dietary arrangements against the accepted requirements too.

For transport, distinguish vehicle arrival from the service attendees could use. Check the agreed departure points, boarding arrangements, operating hours and response to missed journeys. If passengers waited longer than expected, identify whether you specified departure times, maximum waits or another service measure. Those promises require different evidence.

For hired equipment, check condition, usability, delivery and collection against the accepted scope. A supplier may have delivered every item while your own floor plan left nowhere suitable to install it. Equally, a complete delivery note doesn't resolve a fault discovered when the crew tested the equipment. Both the handover and the actual result matter.

Work out who could have prevented the problem

A late start doesn't automatically belong to the supplier whose work finished last. Reconstruct the sequence far enough to identify the decisions and dependencies. Who controlled access? When did they release the room? What information had the supplier received? When did someone recognise that the agreed timing was becoming impossible?

Suppose the venue opened the loading entrance late, leaving the lighting crew less setup time. That matters when judging their readiness. It doesn't answer whether the crew had arrived at the agreed time, whether they warned production about the consequence, or whether another delay came from missing equipment.

Your review can therefore find shared responsibility. The venue may have caused the initial delay, the organiser may have omitted a contact for urgent access problems, and the lighting company may have failed to communicate its revised ready time. Each finding needs its own evidence and correction.

The UK Health and Safety Executive's event management guidance emphasises coordination between contractors and reviewing arrangements after an event. Its guidance applies in Great Britain. The practical question for your review is whether the people doing connected jobs received the information and time they needed.

Record your own team's contribution clearly. If you sent the final running order after the agreed deadline, say so. If your event lead authorised a change verbally but finance never received it, the missing approval record is partly your process to fix. Suppliers can't improve an instruction you keep pretending they received.

Be equally careful about outside conditions. Weather might explain why a delivery route changed, but the review still needs to examine the arrangements that were agreed for disruption. You can't fairly invent a contingency requirement afterwards. You can decide that the next booking needs one before you commit.

Where the cause remains uncertain, write a narrower finding. You know the equipment wasn't ready for rehearsal; you don't yet know whether the fault began before transport or during setup. That supports asking for an investigation. It doesn't support presenting a guess as an established failure of maintenance.

Reconcile the invoice and the cost of the disruption

Finance needs to answer whether the invoice matches the accepted commercial terms. Your operational review needs another answer too. What did this service actually cost the event to deliver, including additional spending caused by problems? Keep those questions connected without treating them as interchangeable.

Start with the agreed price, then identify approved additions, credits, corrected errors and any amount still disputed. Check quantities and hours against the records that establish them. An unexpected charge needs an explanation even if you eventually accept it. A familiar supplier shouldn't receive less scrutiny because you're used to their invoices.

Next, record related costs paid elsewhere. These might include a replacement rental, venue overtime, an extra transport run or attendee refunds tied to the failure. Explain why each cost belongs in the review. Spending that happened during the same period isn't automatically a consequence of the supplier's work.

New Zealand Government Procurement's review of previous purchasing recommends examining contract charges alongside other associated costs. For an event operator, that makes the supplier review more useful than a comparison between the original quote and final invoice alone.

Your team's time matters too, but describe it honestly. A salaried manager spending an evening solving a delivery issue doesn't necessarily create another wage payment. It does use time that could have gone into another event. Keep additional cash spending separate from estimated staff effort so your financial comparison remains understandable.

Be cautious with lost revenue. A cancelled session and documented refunds can support a specific cost. A claim that poor lighting reduced next year's ticket sales usually needs evidence you don't have yet. Record concerns about future demand as concerns, then decide whether follow-up research is worthwhile.

Finally, distinguish your assessment from a claim against the supplier. You may reasonably include disruption costs in a future booking decision without having a contractual right to recover them. Follow the agreement for invoice disputes and obtain appropriate advice for a contested claim. An internal evaluation doesn't create payment or compensation rights.

A worked example of a production supplier review

Here's a fictional paid conference to show how those distinctions change the decision. Every figure in this example is illustrative and in US dollars. These are invented working numbers, not a market rate, customer result or recommended level of production spending.

The organiser accepted a production quote of $4,800. Before the event, they approved a $600 addition for another breakout room. The agreed production price therefore became $5,400. Finance receives an invoice for that amount and initially flags a $600 overrun against the first quote.

The approval record resolves that question. The supplier charged the accepted amount for the expanded scope. The budget should show the addition, but the review shouldn't describe it as unauthorised billing. Our event budget guide explains why retaining the original budget alongside later commitments makes that distinction easier.

There is a separate delivery problem. The supplier was responsible for providing tested playback equipment in the main room before rehearsal. A missing unit meant the organiser rented a replacement locally for $250. The delay also caused $300 of venue overtime, supported by the venue's hours record and invoice.

The production supplier confirms the omission and issues a $200 credit. The final supplier bill becomes $5,200. Adding the replacement rental and venue overtime brings the event's recorded cash cost for this production service to $5,750. Against the approved $5,400 scope, the remaining additional cash cost is $350.

The chart compares four views of the same fictional job. The last bar includes the $5,200 supplier bill, $250 replacement rental and $300 venue overtime. It isn't another bill to add to those amounts. There are no tax adjustments in this simplified example; use a consistent tax basis in your own review.

Now consider the response. The supplier identifies where the equipment check failed, names the person who will verify the revised packing process, and agrees to send confirmation before the next load-in. Your production lead can assess that proposal against the actual omission. A credit alone would reduce the cost without explaining prevention.

The organiser decides a further booking can proceed only after checking the corrective action. They also improve their own rehearsal escalation contact, because the original message took too long to reach someone who could authorise the replacement rental. That second change doesn't remove the supplier's responsibility for the missing unit.

Keep critical failures out of the average

A numerical rating can help you compare repeated delivery of similar work, but an average can conceal the finding you most need to act on. Pleasant communication, a correct invoice and a tidy departure don't compensate for an unresolved failure involving crowd safety or essential accessibility arrangements.

Record any such issue separately, with the evidence, the immediate response and the person qualified to assess what happens next. Your routine commercial review shouldn't delay incident handling, required notifications or specialist investigation. Those follow the relevant arrangements and local requirements, rather than the date you've booked for a supplier catch-up.

Be precise about severity. "Critical" shouldn't become a label for anything that frustrated you. Explain the risk or essential service that failed and why another booking depends on resolving it. A late decorative delivery has different consequences from equipment that a competent reviewer considers unsafe to use.

If your business uses scores, retain the individual findings and booking restrictions next to the overall result. Someone scanning the review before paying a deposit must be able to see an unresolved concern immediately. A favourable average is a poor reason to overlook a condition nobody has checked.

The same principle applies to excellent suppliers. One minor paperwork mistake shouldn't erase delivery that met the agreed requirements and helped the programme run well. Explain its consequence and fix it proportionately. Fairness makes your criticism more useful because suppliers can see you're distinguishing inconvenience from serious failure.

Hear the supplier's account before settling the decision

Send the supplier the relevant findings and evidence, including the things they did well. Explain which facts you want them to confirm, which points remain uncertain, and what decision you're considering. A supplier can respond more usefully to a specific sequence than to a broad request to improve communication.

Ask who was responsible for the work, what they understood the requirement to be, what changed, and what they would do differently. Include your team's contribution where you have identified it. You're more likely to get a useful answer when the discussion reflects the whole job they were asked to deliver.

New Zealand Government Procurement's performance management guidance recommends addressing problems promptly, keeping the discussion about performance, and recording agreed actions. Those are sensible habits for this conversation too, without importing the public sector's formal processes into an ordinary event booking.

Evaluate the answer as carefully as the original performance. A useful response addresses the evidence, accepts confirmed responsibility and explains a feasible correction. The supplier may also provide records that change your conclusion. Correct the review when that happens, and retain the reason for the change so another colleague understands it.

An apology is welcome, but it doesn't tell you what will change. Ask who will do the corrective work, when it will be complete, and what evidence you can check. If the problem concerned qualified supervision, a new generic checklist may leave the actual cause untouched.

You don't need to force agreement on every point. Mark an unresolved disagreement and explain how it affects the booking decision. For a substantial dispute, follow the agreed escalation route. Repeating the same argument in another meeting won't produce a record that neither side has or settle a contractual question.

If the supplier offers a discount on your next event instead of addressing the cause, calculate what that offer changes. You may save money only by committing to another booking. Consider whether you'd accept the operational risk at the normal price first. A cheaper repeat of an unresolved problem can still cost your business more.

Also check who would deliver the next job. A corrective action involving a supervisor who won't attend your next event needs an explanation of how the replacement will work. You don't need to interview every crew member, but the supplier should be able to explain how its agreed correction survives a change of personnel.

Decide whether to rebook, add conditions or pause

Rebook when delivery met the important requirements and any minor problems have an acceptable resolution. State what you want repeated, including the staffing or preparation that made the job successful. Otherwise the next booking can quietly lose the conditions that made this supplier a good choice.

Rebooking still needs a check against the next event. A supplier who delivered a single-room workshop hasn't automatically demonstrated readiness for a larger multiroom programme. Ask what remains comparable and what requires fresh assessment. The review is evidence of a particular job, rather than a promise about every future one.

A conditional booking suits a supplier whose problem has a credible, checkable remedy and whose remaining risk you can accept. Write the condition as a requirement before a defined commitment. For example, your production lead must review confirmation of the replacement equipment before you authorise the next deposit.

Don't use conditions to postpone a decision indefinitely. Identify who checks them and what happens if they aren't met. If your next event starts before a suitable correction can be verified, you need another arrangement for that event even if you hope to work with this supplier again later.

Pause new bookings when a material concern remains unresolved, the supplier's explanation contradicts the available evidence without addressing it, or the proposed correction can't reasonably protect the next event. Record the scope of the pause and who can reconsider it. Existing commitments need separate handling under their actual terms.

Business Victoria's supplier relationship guidance recommends monitoring suppliers against your business priorities as those priorities change. That matters here because retaining a relationship only makes sense when the service still fits what you're selling and how you need to deliver it.

You may also decide the service itself was unnecessary. If attendees didn't need a separately staffed room, reducing that scope could be sensible even when its supplier performed perfectly. Keep that commercial decision separate from a negative performance finding. There's no value in blaming a good supplier for an expensive choice you made.

Use a review record someone else can understand

Keep the final record short enough that the person arranging the next event will read it. Link the supporting detail rather than pasting entire message histories into the summary. You want a colleague to understand the decision without needing to know what everyone said in the loading entrance.

A practical review record contains the following information:

• The event, supplier, service, review owner and date, with the accepted scope and approved changes linked.

• The important delivery expectations, what happened, and the records supporting each material finding.

• The supplier invoice position, related additional costs and any estimates or disputed amounts labelled clearly.

• Your team's contribution, the supplier's response, and any unresolved technical or factual questions.

• The booking decision, corrective actions, named people responsible, and the condition for checking completion.

Write the summary after you've heard the supplier's response. If an urgent booking decision came earlier, label that earlier decision as provisional and record why it couldn't wait. That avoids leaving two apparently final conclusions for the next person to choose between.

Keep access appropriate to the information. Supplier reviews can include commercial details, staff accounts and attendee complaints. Share the relevant findings with the people resolving the issue without copying unrelated personal information into a general planning record. A colleague needs to understand the service problem, not browse every complainant's correspondence.

For a small event, the record might be a few paragraphs. For a complex production contract, you may need a summary with separate technical and financial findings. The purpose stays the same. The person who can authorise another booking needs enough supported information to make that decision responsibly.

Don't wait for every invoice before capturing delivery evidence. You can record what happened now and leave the commercial assessment open until the remaining bills arrive. Mark the missing amounts and who will confirm them. That lets people correct their accounts while the event is fresh without pretending the financial result is final.

For a recurring series, distinguish an isolated failure from a repeated one by reviewing comparable jobs. Check whether the same requirement was missed after an agreed correction, and whether the service changed between editions. A growing audience or shorter access window may explain why an earlier arrangement stopped working, even with the same supplier.

Ask another colleague to challenge a consequential recommendation if you're particularly angry about the event or particularly attached to the relationship. They should examine whether the evidence supports your decision, rather than rerun the whole review. Someone outside the dispute may notice that you've forgiven a repeated failure or attributed an organiser mistake to the supplier.

Finish the review before the next booking makes it irrelevant

Connect supplier findings to the wider event debrief when the cause involves several teams. Keep the supplier decision specific. A broad action to improve next year's communication won't tell the booking manager whether they're allowed to pay this month's deposit.

Put the agreed change into the next scope, briefing or approval process, then have the named person verify it before the relevant commitment. When you rebook, check whether the promised correction actually happened. That gives your next review something better than the same explanation and another assurance that things will improve.