Office Collections for Weddings and Funerals: Running One
#group#communication
When a team collects money for a wedding, a new baby or a bereavement, the friction comes from the process rather than the amount. Why to fix the process first, where flat and voluntary differ, and what to keep after the money is handed over.
The first time the collection lands on your desk, you discover that setting the amount is the easy half. Explaining how you set it is the hard half.
Ten dollars a head, or twenty. What about the person who started last week. Do you approach someone who’s on leave. None of these has a right answer, and all of them need one immediately.
Fix the process before the amount
Collections are awkward because the amount is the first thing anyone thinks about, and only after the news has broken. Starting the discussion after an engagement is announced or a death is passed along means working against the clock — and it makes the number look like a verdict on how much that person is worth to the team.
What needs deciding in advance isn’t the figure. It’s who asks, by when, and what happens to whatever is left over. Amounts change with the occasion. A process gets reused.
Having one also takes weight off whoever is collecting. There’s no case to make each time, because “same as last time” is available as an answer.
Flat or voluntary
Collections split into two shapes: a fixed amount from everyone, or whatever people choose to give.
Flat has the advantage of removing the decision. Its cost is that opting out effectively disappears. Someone with a reason not to contribute — money, belief, distance from the person — has no sentence available to them.
Voluntary is the mirror image. The room to decline survives, but the total becomes unpredictable. Organisers end up quietly covering the gap, and once that happens, nobody wants the job next time.
| Approach | Suits | Watch out for |
|---|---|---|
| Flat | Small teams, people who know each other | No room to decline |
| Voluntary | Larger teams, high turnover | Total is unpredictable |
| Flat with opt-out | The middle path | Needs a private route to decline |
The third is the one that survives contact with reality. State a flat figure, and say that anyone can opt out by messaging you. Route the opt-out through the organiser personally so that declining stays invisible to everyone else.
Scaling contributions by seniority is a live idea in some offices. For collections it tends to create more friction than it removes, and if you want tiering at all, it goes down better in everyday settings first. The mechanics of tiering are covered in the organiser’s guide to splitting a group dinner.
Assume bereavements give you no time
Celebrations and bereavements behave nothing alike, even though they sit in the same budget line. A wedding or a new baby is weeks of notice. A death is hours.
What that needs is a standing rule, not a discussion. Unless you have already decided who fronts the money and when it gets collected, the person who fronted it never raises it. Condolences are needed the same day, so in practice one person pays the lot and recovers it afterwards.
That shape — pay first, collect later — is the one where recovery fails most often. The weight of the occasion is exactly what makes the follow-up conversation hard to start. Writing down the amount and who it covers at the moment of paying turns the recovery into clerical work.
Keep the record past the handover
A collection record isn’t finished when the envelope is handed over. Someone will ask later whether they were counted, and whether you can answer decides how easy the next collection is.
Create one project in Evere and everything tied to that occasion sits together. Who gave what, what it was spent on, and what was left over all live in one place, which is also where the write-up comes from.
Say what happens to the remainder up front. Carry it forward, or give it back on the spot. If you carry it forward, you need to be able to state the current balance on request. A float nobody can put a number on becomes unexplainable the moment the organiser changes.
For the wording of the ask itself, the sequence in collecting for a group gift transfers almost directly.
Common questions
Q. Should I ask someone who joined last week? Ask, and attach an easy way out. Leaving them off means they get excluded from a team custom without ever knowing it existed. Handing them the decision is the fair version.
Q. What about people on extended leave? There’s no need to avoid contacting them, but don’t attach urgency. Send it without a deadline and proceed if nothing comes back.
Q. People ask me what the going rate is. Show them what was collected last time if you have it. A figure you give verbally becomes your opinion. What was collected previously belongs to nobody.
Q. Can I claim back what I topped up myself? Yes, but raise it when you discover the shortfall, not after the handover. Asking once it’s done reads as an announcement rather than a question.