University club budgets have two rulebooks. The campus funding office decides what a pot of money can cover and when proof is due. Your club decides how to prioritize eligible projects. Keep those decisions separate.

Start with the fund's source, purpose, and deadline before choosing an equal split. Dues or event revenue may be handled differently from a student-government allocation, and no internal formula can override the university program controlling the money.

Read the funding policy as a checklist

Before anyone commits money, capture the answers in one place.

Policy question Record to keep
What is the approved purpose? The program, project, event, or expense category named in the award or handbook
Who approves spending? The funding office, advisor, treasurer, committee, or other required approver
Is preapproval required? The approval date, request ID, and meeting decision
Which dates control? Application, purchase, event, reimbursement, audit, and closeout dates
Which records are required? Itemized receipts, invoices, proof of payment, and any event record the policy requests

Ask about access, too. If a fund distinguishes campus-facing programs from internal member activities, record that distinction before planning a dinner, award, or social.

Thing is, a balance on a spreadsheet doesn't prove that a purchase is allowed. Eligibility comes first.

What university examples show

At Ohio State's Student Activities Funding page, the Programming Funds application has five deadlines based on the program date. Its audit is due no later than 30 calendar days after the scheduled event date. That is a program rule, not a universal deadline for every Ohio State fund or every university.

Wright State's Student Organization Budget Committee page shows how funding calendars can narrow quickly. For its listed 2026 cycle, the page separates early review, final submission, and final completion and documentation. It also says requests above $5,000 require a virtual hearing under that process.

At La Salle University's financial manual, a check request needed by a specific date should be submitted at least two weeks before the check is required. That is a payment-processing instruction. It isn't general permission to spend.

These examples answer a narrower question: what does one named program require? They don't prove that every university requires an open event, excludes a member-only dinner, or uses a 30-day audit deadline. Check the exact fund page before your club promises reimbursement.

Choose a fair allocation method

Once campus eligibility is clear, choose how your club will divide its approved budget. The right method depends on what the money supports.

Method Works better when Main tradeoff
Equal project shares Projects have similar size and purpose Simple, but it ignores reach and cost differences
Usage or per-person shares Expected attendance drives eligible costs Tracks likely use, but headcounts can change
Reimbursement after proof The club wants documentation before payment Controls spending, but members may have to front cash
Income-based shares An approved access goal calls for different contributions May widen access, but needs consistent private criteria
Room-size or nights-stayed shares A trip or lodging cost depends on occupancy Useful for travel, but awkward for general club programming

Don't confuse usage with permission. A larger audience can change an allocation, but it cannot make a prohibited expense eligible.

Suppose $600 is approved for three eligible programs. An equal allocation gives each program $200. A per-person method based on expected attendance of 20, 30, and 50 gives $120, $180, and $300. Record the inputs, not just the final amounts.

To be honest, the formula matters less than the rule's visibility. Members can challenge a result they understand; they can't audit a private promise.

Put the club rule in writing

A short internal policy can prevent awkward arguments later. It should say what the money is for, who can approve a request, how the club divides it, and what happens when a purchase changes.

Sample internal rule: "The club may use this fund only for expenses approved under [campus program]. Each request must name the event or project, estimated cost, and responsible officer. The treasurer logs actual spending, and a second officer checks the records before reimbursement. No one is promised a personal share of restricted funds."

Add a tie-breaking order for competing requests. Use eligibility first, then deadline, committed costs, expected reach, and convenience. This keeps the club from choosing the easiest request instead of the eligible request with a clear purpose.

If a member pays upfront, get written approval before the purchase. An unapproved purchase is harder to fix later.

Use a five-step setup workflow

  1. Name the pot. Record whether the money comes from dues, an allocation, a grant, or event revenue. Note who can answer policy questions.

  2. List eligible activities. Mark each proposed request as eligible, unclear, or not eligible until the funding office confirms it.

  3. Choose the formula. Use equal shares, usage-based shares, or reimbursement-after-proof. State what happens if attendance, price, or event scope changes.

  4. Assign authority. Give the treasurer responsibility for the ledger. Require a second officer, advisor, or committee to review reimbursements or larger commitments.

  5. Calendar closeout. Add application, purchase, event, audit, reimbursement, and final documentation dates to a shared calendar. Assign a backup owner.

Turns out, a deadline without a named owner belongs to nobody.

Keep a clean record

Your tracker should let a new treasurer reconstruct one dollar without asking five people what happened. Use a spreadsheet, campus form, or another simple record that connects each expense to an approved activity.

At minimum, keep:

  • the approval or award record
  • purchase date, vendor, item, and amount
  • payer and payment evidence
  • event or project name with an eligibility note
  • reimbursement status and applicable deadline

OSU's funding page gives one example of payment evidence. It refers to the last four digits of a payment card and, when needed, supplemental records such as a canceled check or bank statement. Never place full card numbers in a shared club sheet.

Use a predictable file name such as YYYY-MM-DD_event_vendor_amount. Keep approvals, transactions, receipts, and closeout records in separate folders or tabs. Give editing access to the treasurer and a backup, not the entire membership by default.

Tools are optional. A spreadsheet and an organized folder may be enough. If your campus supplies an official form, use it instead of replacing required fields with a prettier sheet.

Handle unclear or missed rules carefully

Pause the purchase and ask the funding office or advisor in writing. Include the program name, event, cost, vendor, expected audience, deadline, and whether someone will pay upfront or request reimbursement.

Save the response with the approval record. Don't rely on a rule copied from another university, another student-government fund, or an older funding cycle.

Access questions deserve a direct answer, especially for member-only meals, awards, socials, or closed meetings. Ask whether the expense is eligible, whether the event must be open to campus, and whether advertising or acknowledgment language is required.

Treat a missed deadline as a funding-office question, not a guaranteed exception. The Ohio State page warns that a Programming Funds reimbursement may be void when the audit is not submitted within 30 calendar days.

Make the next club meeting produce one page

Bring a one-page draft that names the fund source, eligible uses, allocation method, approvers, receipt owner, and closeout dates. Vote on it, save the minutes, and send the draft to the funding office before anyone spends.

Recheck the official policy at the start of each funding cycle. Dates and program requirements can change.