One of the first decisions a committee makes is how to collect: a fresh drive for every festival, or one yearly contribution into a shared fund. Both work — the right choice depends on your residents and your committee’s appetite for chasing payments.
Per-festival collection
Each celebration has its own drive, its own minimum contribution and its own books.
- Great for societies that celebrate ad-hoc or vary the scale each year
- Residents pay in line with each festival’s budget
- Lets you compare festival-over-festival performance cleanly
- Downside: more collection drives means more chasing
Annual (pooled) collection
One yearly contribution per unit goes into a shared pool, and every festival draws its budget from it.
- Residents pay once — far less chasing across the year
- A pool view keeps every festival on budget
- Steadier cash flow for the committee
- Downside: you set the yearly amount up front, so estimate well
How to decide
If your residents dislike repeated requests and your committee wants predictable cash, go annual. If your festivals vary a lot in scale or you like clean per-event books, go per-festival. Omkosh supports both, and you can switch models later in Settings as your process matures.
All guides
Share: