How to follow up unpaid pledges after a fundraising event

Your fundraising dinner is over. The guests have gone home, the suppliers want their balances, and the total announced from the stage looks encouraging. Then you open the payment report. Some of the money is there. Some is still a promise. A few names on the pledge cards don't quite match the names beside the payments.

The first thing you want to do is check those records before sending anyone a reminder. Confirm what each person promised, find payments already made, and separate amounts due now from instalments agreed for later. Then contact the right person privately, with the correct balance, a straightforward way to pay and a named person who can resolve a mistake.

That sounds like ordinary administration, and much of it is. But fundraising event pledge collection also involves trust. Someone might have forgotten, paid from a company account, misunderstood the amount or had their circumstances change. A message that assumes the worst can damage a relationship while failing to answer the practical question holding up payment.

This guide explains how to organise that follow-up after a paid charity dinner or similar ticketed fundraiser. It includes adaptable messages, a pledge-record template and a fictional reconciliation in USD. The examples are planning recommendations, not collection-rate benchmarks or claims about how donors usually behave. The charity should approve the process, including the rules that apply where it operates.

Establish what the donor actually committed to

Start with the original record. That might be a completed pledge card, an entry through the charity's approved system or an email confirming an amount and payment date. Keep the source available to the people checking it. A volunteer's recollection that someone at table seven offered a large gift is a reason to investigate, not enough information to send a demand.

Check the amount, currency, donor identity, purpose and conditions. Was the person promising a total gift or an additional gift? Did the amount include a payment they had already made? Were they speaking personally or offering to ask their employer? If the original promise depended on something happening, record that condition before deciding whether payment is due.

Take particular care with a live appeal. A guest might raise a paddle at one level and then increase their contribution. You need to know whether the second record replaces the first or adds to it. A pledge card and a digital entry can also describe the same gift. Ask the appeal lead to resolve the evidence rather than adding every record together because each has a different timestamp.

For an unclear entry, send a neutral confirmation. You can say that you are checking the dinner's records and ask whether the recorded amount matches the support they intended. Don't attach a payment deadline to an amount you haven't established. The correction may reduce the apparent total, but it gives you a balance you can explain.

Keep admission purchases and other obligations identifiable. An unpaid table invoice, a winning auction bid and a voluntary appeal pledge arise from different arrangements. Our ticketed charity gala guide covers the wider event budget. Here, the job is to follow through on recorded gifts without confusing them with everything else someone bought that evening.

Agree who owns the follow-up after the event team leaves

A commercial producer may organise the dinner while the beneficiary receives the gifts. Decide which organisation answers pledge questions, can see donation records and approves changes. A donor shouldn't have to explain the same payment to the producer, a volunteer and the charity because nobody knows who is responsible after event day.

Name one person to manage the collection list. Finance should verify payments and balances, while an appropriate charity contact handles sensitive donor conversations. In a small team, one person might perform several jobs, but someone else should check material corrections. Agree who can approve a revised commitment, a payment schedule or the closure of an unresolved record.

Give volunteers a defined task. A table host can help identify a guest or make an introduction when appropriate. That doesn't automatically mean the host should receive everyone's pledge balances or chase their colleagues. The person who sold the table may have no role in the additional giving. Ask the charity what information can be shared and what contact is appropriate.

For charities in England and Wales, the Charity Commission's internal financial controls guidance explains the need for suitable controls and reliable financial information. The practical arrangement here is a named owner, documented approvals and a payment check someone can repeat. Other jurisdictions have their own requirements.

Also agree how long the producer's contract covers this work. If the charity expects six weeks of donor support but the producer priced only event delivery, settle that gap explicitly. You can hand the records to the charity's named team or agree a paid extension. Leaving the question open creates a predictable problem when a donor replies to an inbox the event team has stopped monitoring.

Build a pledge record that supports the next action

Use the charity's existing donor system when it already handles these records properly. If a controlled spreadsheet is appropriate for a small event, agree where it is stored, who can edit it and how finance receives changes. Avoid creating another collection list if the approved system already contains the same information and can manage the work.

Each pledge needs a unique reference. Use that reference in the record and payment instructions where the payment method supports it. Keep a way to connect the entry to its original evidence. A reference is particularly useful when the person making the payment has a different name from the guest who made the promise.

Use these fields to decide what your record needs. If your donor system already holds a detail, link to it where possible instead of copying it into another file.

• Pledge reference, event name and date, with a link to the original commitment.

• Donor or paying organisation, approved contact details and the person responsible for the relationship.

• Original amount, currency, intended purpose and any qualifying condition.

• Agreed payment dates, instalment amounts and remaining balance.

• Verified payments, dates and transaction references, with charges recorded separately.

• Current status, last contact, response and next permitted action.

• Corrections, approvals, contact restrictions and the date finance last checked the balance.

Keep the status factual. Useful descriptions include awaiting confirmation, due, partly paid, future instalment, payment being checked and closed after approval. If a donor disputes the amount, record that dispute. Calling every unresolved entry overdue hides the reason someone needs to act and encourages the wrong message.

Write notes another authorised colleague could understand without knowing the guest. "Donor says paid on 22 March; finance checking reference" is useful. Speculation about wealth, generosity or why someone hasn't replied isn't. You need evidence for the follow-up, not a private commentary on the donor.

The UK Information Commissioner's Office explains that personal data should be relevant and limited to what is necessary. Its guidance is under review following legislative changes. Apply current local rules and the charity's retention policy, and keep detailed sensitive conversations out of a broadly shared event list.

Check the payments before deciding someone hasn't paid

Bring the pledge list together with the charity's approved payment reports. Check event-night payments, later online gifts, bank transfers and other accepted methods. Look at what the records actually show. An email saying a transfer has been arranged is useful information, but it doesn't establish that the charity has received and identified the payment.

Match using more than a familiar name. Compare the amount, reference, date, payer and any donor explanation. A company may pay on behalf of an employee. A partner may use their own card. Someone may split one pledge across two payments. Record the connection once verified so the next person doesn't interpret the same payment as an unrelated new gift.

Don't force an uncertain match. If two people promised the same amount and an unidentified transfer arrives, finance needs more evidence. Mark both relevant records for checking and pause the affected reminder. Ask for a transaction date or reference through the approved contact route. You shouldn't require a donor to reveal full account or card details to help identify a payment.

Separate payment progress from the donor's remaining obligation. A payment provider can show a successful transaction before the money reaches the charity's bank. Once the authorised payment owner has verified that transaction, stop asking the donor to pay it again while finance follows the payout. Show the bank timing separately so the cash forecast remains accurate.

Check reversals and refunds too. If a payment later fails or is returned, establish what happened before restoring an outstanding balance and restarting contact. The donor may need help completing the gift, or the charity may have approved the refund. Those cases require different actions. Preserve the original record and the correction so the history remains understandable.

If a donor says they paid, acknowledge the message and pause the reminder while finance checks. You could reply: "Thanks for letting me know. I've paused the reminder while we look for the payment. Please send its date and reference if available, and I'll come back to you after the check." Set an internal review date so the investigation doesn't remain open indefinitely. Then confirm the result to the donor, including a correction and thanks when the payment is found.

Run this check immediately before a reminder batch, not only when the list was first created. Someone can pay after you prepare the messages and before they go out. For a small event, a final finance check may be manageable manually. If software manages the reminders, test how it identifies payments and removes paid records from the next send.

Sort the outstanding balances by what needs to happen

Once the records agree, divide the work by the next action. Start with confirmed amounts that have reached their agreed payment date. These may be ready for a reminder. Keep future instalments on their own schedule. A donor who agreed to pay in June isn't late because you want to finish the dinner report in April.

Then identify problems the charity must resolve first. These include an unclear amount, an incorrect email address, a payment under investigation or a question about the promised use of funds. Assign each to someone who can answer it. Sending another payment link while ignoring the question can make the process feel automated and indifferent.

Keep conditional commitments separate. "I will ask my company to contribute" isn't the same as the company approving a gift. A matching funder may need evidence of eligible donations before its amount becomes payable. Record the condition, the evidence required and the responsible person. Don't place an unapproved corporate request in a queue for overdue personal donations.

Give sensitive cases a private review. If someone reports financial difficulty or another serious change, pause the standard sequence and refer the conversation to the authorised charity contact. The goal is a considered decision under the charity's policy. Volunteers don't need to collect a detailed personal explanation or negotiate independently to prove that they tried hard enough.

Finally, distinguish unresolved from uncontactable. A message that bounced hasn't been read and ignored. Check whether you have an approved alternative contact method. Don't search through unrelated guest records or ask a table of colleagues to locate someone simply because the first email failed. Record the problem and let the responsible charity team decide the proportionate next step.

Choose a timetable around the promise and the support available

There is no useful universal rule that every pledge should receive three emails over fourteen days. The amount, agreed date, donor relationship and problem being resolved all matter. Decide the follow-up plan with the charity, then record the next action for each pledge so staff don't independently contact the same person.

Here is an example timetable for a fictional dinner on 20 March 2027. The team checks records on 22 March and sends individual confirmations after that check. Pledges with an agreed payment date of 31 March can receive a courteous reminder after that date, following another payment check. Future instalments remain outside that batch.

For a donor who hasn't replied, the charity might review the record on 8 April and approve one personal contact through an appropriate channel. It could then review unresolved cases on 15 April and decide whether to pause, correct, continue or close the follow-up. These dates illustrate an operating choice. They aren't a required sequence or evidence that a particular interval improves collection.

State what happens when someone replies. A response should reach a person who can help, and the pending messages should pause while that person checks the issue. If a donor says they will pay on an agreed revised date, update the record and confirm that date. Don't leave the original overdue sequence running behind the conversation.

The public appeal's closing date may differ from the date for paying existing pledges. Our guide to event fundraising windows explains that distinction. When the public page closes, keep an approved way to settle earlier commitments and ask questions. A broken payment link shouldn't become the reason a donor cannot complete a gift they still intend to make.

Send a confirmation that makes mistakes easy to correct

The first message should tell the donor what you recorded and how to respond. Thank them for their intended support without saying the money has already arrived. Include the charity, event, pledge reference, amount, purpose and agreed payment date. Use clear ordinary wording, especially when the message could be mistaken for an unfamiliar invoice.

For the fictional dinner, a confirmation could read as follows. The example assumes the charity has verified the pledge and approved the communication channel. Replace the names, dates, amounts and payment destination before use.

Subject: Your Cedar Learning Dinner pledge, reference CLD-014

Hi Morgan,

Thank you for offering to support Cedar Learning at the dinner on 20 March. We recorded a gift of $1,500 for the charity's general work, with payment agreed by 31 March. We've received $500 against that pledge, leaving $1,000 to complete it.

You can pay the remaining amount through the charity's approved payment page using reference CLD-014. If you've already sent it, please reply with the payment date and reference so our finance team can check. Please don't email card details.

If the amount or payment date doesn't match what you intended, reply to me and we'll review the record with you. Thank you, Alex, Cedar Learning supporter team.

Put the actual approved link behind descriptive words in the finished message. Check it opens the correct charity page and allows the donor to identify the pledge. If the page asks for an amount, make the remaining balance clear before the person reaches it. If it preloads an amount, verify that the saved link reflects partial payments.

Don't add a new appeal to this confirmation. Asking the person to complete an existing promise and increase it at the same time makes both actions less clear. You can continue the wider relationship through separately approved communications. For broader attendee messages, our post-event email examples cover useful distinctions between thanks, resources and other follow-up.

Write a reminder that helps the donor finish the gift

A reminder needs a checked balance and a practical reason to contact this person now. Avoid language that suggests deliberate avoidance when you don't know what happened. Start with the event and reference, explain what your records show, then provide the payment or correction route. Make the person sending it identifiable.

Here is an overdue reminder for the same fictional pledge, assuming no further payment has been found and the agreed date has passed.

Subject: Checking the remaining balance on pledge CLD-014

Hi Morgan,

I'm following up on the $1,000 remaining from your Cedar Learning Dinner pledge, which was due on 31 March. Our finance team checked the payment records today and hasn't yet identified that balance.

If you'd like to complete it now, the charity's approved payment page is available using reference CLD-014. If you've paid already, please send the payment date and reference so we can investigate before contacting you again.

If you need to discuss the amount or timing, you can reply directly to me. Thank you, Alex, Cedar Learning supporter team.

The payment request is clear without a threat. It also tells someone who has paid exactly what information would help. Use this structure only when the underlying record is reliable. If no date was originally agreed, ask the donor to confirm a workable date rather than inventing an overdue deadline retrospectively.

For a brief personal call, begin by checking that the person can speak privately. Explain that you are checking the recorded pledge and ask whether they received the payment information. Don't leave a detailed balance on a shared voicemail or discuss the pledge with whoever answers. Follow the charity's contact procedures and record the outcome accurately.

The UK Fundraising Regulator's standards for fundraising behaviour prohibit undue pressure and unreasonably persistent approaches, and require a request to end an interaction to be accepted. Your charity must apply the rules relevant to its location. A donation reminder should never become an excuse for public embarrassment or repeated unwanted contact.

Keep pledge reminders separate from new fundraising

Before sending, check why you can contact this person through this channel. A guest may have bought dinner admission through the producer but given their pledge details directly to the charity. The person responsible for donor communications needs to understand that relationship. Possessing an email address doesn't settle how it may be used.

The UK Fundraising Regulator's guidance on fundraising marketing and administrative messages distinguishes those purposes. A purely administrative message will not normally be marketing, while asking for donations generally is. The actual content and context matter. Have the responsible team check the applicable rules rather than assuming anything called a pledge reminder is exempt.

For example, a message about a verified payment problem can focus on that problem. Adding an invitation to next year's gala or a request to increase the gift introduces another purpose. Keep that promotion in the relevant marketing process, with the permissions and choices it requires. The charitable purposes soft opt-in is a conditional exception to the usual consent requirement for a charity's electronic fundraising marketing. A commercial producer cannot assume it can use that exception to send the charity's appeals.

Treat a request to stop contact seriously and refer any remaining administrative issue to the charity's responsible team. Record exactly what the person asked, which messages must stop and who decides whether any necessary contact remains appropriate. An unsubscribe from promotional emails and a dispute about a pledge need accurate handling. Neither should disappear because two systems store them differently.

Check the final recipient list against the current records. Exclude paid commitments, future instalments that aren't due, paused disputes and people whose contact restrictions prevent that message. If you use a sending tool, confirm that last-minute changes reach it. A correction made in the pledge record is ineffective if a stale exported list still controls tomorrow's email.

Keep payment instructions secure and recognisable

Use the charity's approved collection route and identify the organisation receiving the gift. A donor should be able to verify the request through a known website or contact, especially if the dinner's trading name differs from the beneficiary's legal name. Test the page on a phone and check that its confirmation reaches the right person.

Don't ask people to reply with card numbers or security codes. The PCI Security Standards Council explains that receiving card data through email or similar messaging brings those channels within applicable security requirements. For this workflow, direct donors to the approved payment process instead of turning an ordinary event inbox into a place for card information.

If a donor needs another method, offer only those the charity has authorised. Bank transfer instructions need a consistent reference and a way to resolve unidentified payments. Cheques require an agreed receiving address and handling process. Staff should know where to refer a question without sending unverified bank details copied from a private conversation.

Keep admission payments connected to the admission record. Loopyah's ticket checkout displays ticket types and prices, takes payment and sends confirmation linking to QR tickets. That supports the paid event's entry sale. The charity's pledge follow-up needs its own approved gift record and payment instructions, so a donor isn't asked to buy another dinner ticket to complete a separate promise.

Offer help in a form the donor can use. If someone cannot complete the online page, provide a named contact who can explain the charity's available alternatives. Check that payment instructions are readable text and don't depend on a tiny image or a colour alone. Don't make someone disclose a disability to an event committee just to obtain another way to finish their gift.

Test errors as well as a successful payment. Can someone report a duplicate? Does the payment owner know how to find a pledge reference? What happens when a donor pays only part of the balance? Resolve those questions before sending a batch. A correct link is useful only when the team can understand and support the payment that follows.

Make instalments and revised commitments explicit

An instalment arrangement should state the total, each amount and its due date. Confirm whether the donor has agreed to scheduled payments through an approved provider or intends to make each payment themselves. Permission to record a pledge doesn't, by itself, authorise charging a card or creating recurring payments.

Suppose a donor promises $1,200 and agrees to four payments of $300. After the first verified payment, the remaining commitment is $900. The next reminder concerns the next $300 when its agreed date arrives. Asking for the full $900 immediately would contradict the schedule and make your records look unreliable.

If the donor asks to change the dates, let the authorised charity contact approve the arrangement. Record the old schedule, the change, the approval and the new dates. Confirm the revised plan with the donor and update any reminders. Finance also needs to know when it can realistically expect the money, particularly if the original forecast assumed collection immediately after dinner.

A smaller commitment needs a similar correction. If a $500 promise is revised to $200 with the charity's approval, the record should show the $300 reduction and the reason at an appropriate level of detail. Once the $200 is received, the revised commitment is complete. Leaving the original $500 untouched would keep a false $300 balance in the collection queue.

Don't let a courteous conversation conceal a forecast problem. If several substantial gifts move into later months, update the cash plan and tell the people approving expenditure. You can respect the agreed donor schedule while being candid internally that the money won't fund next week's bill. Those are compatible responsibilities.

Handle employers and matching gifts without doubling the promise

Confirm who made the commitment and who is expected to pay. A guest can offer a personal gift, make an authorised company commitment or say they intend to seek an employer contribution. Those statements create different follow-up jobs. Ask for the paying organisation and approval process before treating a possible company gift as confirmed.

If the company has approved a contribution, use its required payment information and named contact. An employee may need to submit a request, while finance needs a charity document or reference. Help supply the agreed information securely. Don't invoice the employee personally because their employer's internal process takes longer than the dinner committee expected.

An employer match is a separate potential payment. Record the employee's gift, the match application and the employer's approved contribution distinctly. A donor saying their employer usually matches gifts doesn't establish an amount received or guaranteed. Keep the status accurate until the relevant approval and payment evidence arrive.

The same applies to an event matching funder. Check whether the agreement requires gifts received, pledges recorded or another qualifying event. A late pledge payment might qualify or miss the terms. Ask the authorised team to interpret the actual agreement rather than promising the donor a match merely because there is unused money under the cap.

When a company pays on behalf of a guest, link the payment to the correct commitment once finance verifies it. Don't create a new company donation and leave the original personal pledge outstanding for the same money. Record who needs the acknowledgment through the charity's approved process, especially when the person attending and the legal donor differ.

Pause when the donor disputes the record or needs support

A dispute about the amount needs investigation before another request. Preserve the original card or system entry, review any later change and ask the donor what they understood. The charity should resolve the discrepancy and document the outcome. Don't send the original record around a committee asking who remembers the conversation most confidently.

If the donor says they cannot proceed, refer the case through the charity's policy. A responsible review may consider a revised date, a reduced commitment or stopping contact. The appropriate decision depends on the actual agreement and circumstances. Keep the conversation private and avoid making promises about legal release that you aren't authorised to give.

For a complaint, pause routine reminders and use the charity's complaints process. A donor who is waiting for an answer about misleading appeal wording shouldn't keep receiving the same payment message. Record which team is handling the issue and what communication is appropriate while it is investigated. The eventual financial correction must reach finance as well as the relationship owner.

Be careful about treating any pledge as either automatically enforceable or automatically optional. The University of Iowa's Nonprofit Resource Center discusses when charitable pledges may be legally binding and the need to consider recovery case by case. Legal treatment depends on jurisdiction and the agreement. Obtain relevant advice before threatening recovery, releasing a material claim or making expenditure decisions that rely on it.

Routine event staff should have a clear boundary. They can confirm a balance, supply approved payment information and refer an exception. Decisions about legal recovery or a significant change belong with the charity's authorised leadership and advisers. For a substantial pledge, arrange that review before another volunteer contacts the donor. Everyone involved should know which conversation is authorised and who will handle the reply.

Work through the reconciliation before announcing a result

Here is a fictional example for Cedar Learning's dinner. All amounts are USD and describe the pledge collection only. Admission income, sponsorship, auction sales and the dinner's operating costs are outside this example. The figures are invented to explain the records, with no tax or currency conversion, and are not Loopyah charges or donor-performance benchmarks.

The initial list shows $9,000 across eight entries. One $1,000 entry duplicates part of a gift already recorded elsewhere, so it adds no further commitment. The charity also approves reducing one $500 pledge to $200. Corrected commitments total $7,700 after removing the $1,000 duplicate and the $300 reduction.

The checked records now show these positions:

• A $2,000 commitment is fully paid, leaving nothing outstanding.

• A $1,500 commitment has $500 received and $1,000 remaining, now due.

• A $1,200 instalment commitment has $300 received and $900 scheduled for later dates.

• The duplicate $1,000 entry is closed as a duplicate, with no separate gift or balance.

• An $800 commitment is paid by a verified bank transfer initially recorded without a pledge reference.

• A confirmed $1,000 company commitment is unpaid and has reached its agreed date.

• The revised $200 commitment is fully paid, with the original $300 reduction approved and recorded.

• A $1,000 commitment has no payment identified and has reached its agreed date.

Verified gifts received total $3,800. That's $2,000, $500, $300, $800 and $200. Remaining commitments total $3,900. Of that balance, $900 belongs to future instalments and $3,000 has reached the agreed payment dates. The reminder list must reflect those differences. Sending a demand for $3,900 would wrongly accelerate the instalments.

The corrected $7,700 total equals $3,800 received plus $3,900 outstanding. It doesn't equal the original $9,000, because the duplicate and approved reduction changed what was genuinely expected. Keep that explanation available when the committee compares the final records with the event-night announcement. A lower corrected total is preferable to chasing money nobody separately promised.

Assume the $3,800 has settled and there are $100 of payment charges and $240 of approved collection administration costs. The pledge collection has produced $3,460 after those costs. This is an unrestricted appeal with those costs permitted and no other collection costs in the example. It isn't the whole dinner's net proceeds, and the unpaid $3,900 isn't available cash.

Now suppose the donor with $1,000 remaining on the $1,500 pledge pays that balance. Received gifts become $4,800 and outstanding commitments become $2,900. If cumulative payment charges rise to $130 while administration stays $240, the collection leaves $4,430. The payment moves money from outstanding to received. It doesn't add another $1,000 to corrected commitments.

Confirm the gift and report what is still unresolved

After verifying payment, stop the relevant reminders and send the appropriate acknowledgment through the charity's process. Thank the person for the gift actually received. If the payment completes an instalment rather than the whole commitment, state the remaining schedule accurately so the donor understands whether further action is expected.

In the United States, the IRS explains the written acknowledgment needed to substantiate charitable contributions of $250 or more, including the organisation, amount and relevant goods or services information. This is US guidance, not a universal receipt rule. The charity must establish the correct documentation for its location and the actual gift.

A pledge confirmation and an acknowledgment of a received contribution perform different jobs. Keep their wording accurate. Don't issue a document saying the full gift was received when only an instalment arrived, or promise a donor that a payment is deductible without the charity's approved basis. A normal payment email may also need separate charitable documentation.

For the committee, report the position as of a named date. Show corrected commitments, verified receipts, future instalments, overdue amounts and cases needing a decision. Include material charges and the cost of remaining work where relevant. Finance should reconcile this operational report with the charity's accounts under its applicable accounting rules. These collection figures don't determine when a pledge counts as income in the charity's formal accounts.

For the public update, describe received gifts and outstanding pledges in terms people can understand. Avoid publishing donor names or balances to encourage collection. If the event-night figure was materially overstated, agree a clear correction with the charity and use the channels where that figure mattered. Our guide to displaying live fundraising totals explains why the definition behind an announced number needs to stay consistent.

Finish the handover and improve the next appeal

Before closing the production job, hand over every open pledge with its evidence, current balance, approved contact history and next action. Include future instalments and paused cases. Ask the charity's named owner to confirm receipt and access. A file sitting in a shared folder doesn't establish that anyone has accepted responsibility for the remaining work.

Review what further collection will cost and who will do it. A short administrative correction and a complex donor dispute need different people and amounts of time. Fund any continued work explicitly. The cost review helps allocate staff; it shouldn't become an automatic rule to abandon a pledge or override the charity's duties. Material decisions still need the appropriate approval.

Retain the original evidence and necessary financial records according to the approved policy. Remove temporary working copies through the charity's process once they are no longer needed. Keep enough information about corrections and contact restrictions to prevent the next team recreating a closed balance or restarting unwanted reminders. Don't retain sensitive personal detail simply because it appeared in an email conversation.

Then review the collection problems while the event is still recent. Did people misunderstand whether their paddle increase was additional? Were payment references missing? Did the host announce a deadline that differed from the pledge card? Fix the relevant form, script or payment instruction before the next dinner. Our fund-a-need appeal guide covers the live giving process that creates these records.

For the next event, prepare the pledge confirmation and test the payment record before guests arrive. Give the appeal team a way to distinguish an increase, a duplicate and a completed payment. Agree who takes over after dinner and what they will need. Then a donor who follows through receives thanks, someone with a genuine question receives help, and the charity has a checked account of what remains to collect.