Difference between revisions of "Budget Timeline"
Jump to navigation
Jump to search
m (→Timeline) |
m (→Timeline) |
||
Line 16: | Line 16: | ||
** Produce actuals for previous several months | ** Produce actuals for previous several months | ||
** Estimate future income and expenses, '''record assumptions''' | ** Estimate future income and expenses, '''record assumptions''' | ||
− | ** Present to staff for feedback at staff meeting | + | ** Present to staff for feedback at staff meeting - early Sept. |
* Budgeting team meet with Treasurer to ID bugs - Sept. 13-20 | * Budgeting team meet with Treasurer to ID bugs - Sept. 13-20 | ||
** Be prepared to submit emergency schedule requests if unexpected tasks come up. | ** Be prepared to submit emergency schedule requests if unexpected tasks come up. | ||
Line 24: | Line 24: | ||
* Attempt to close out month for September in case any last minute things come to light. | * Attempt to close out month for September in case any last minute things come to light. | ||
* Board Meeting - Oct. 8th (2nd Wednesday of Quarter) | * Board Meeting - Oct. 8th (2nd Wednesday of Quarter) | ||
− | * Report back to each committee | + | * Report back to each committee post-approval of Board |
** Plug approved budget numbers into tables per committee, and/OR | ** Plug approved budget numbers into tables per committee, and/OR | ||
** Email to staff with numbers | ** Email to staff with numbers |
Revision as of 12:40, 16 July 2008
Ongoing
Tie these things up before starting the process for peace of mind:
- Reorganize any line items in the books due to committee changes, etc.
- Keep up on all tasks listed in Closing out the month
- Solicit input from all staff members
- Keep a list of upcoming changes that may affect the budget
Timeline
- Identify budgeting team of 2 (two) Beancounters
- File schedule requests (schedule at freegeek dot org) in late August (at the latest).
- Budgeting team works for 4 hours per day for entire week - Sept. 6-12, 2008
- Close out the middle month of the previous quarter (in this case) August. See Closing out the month.
- Create working spreadsheet.
- Produce actuals for previous several months
- Estimate future income and expenses, record assumptions
- Present to staff for feedback at staff meeting - early Sept.
- Budgeting team meet with Treasurer to ID bugs - Sept. 13-20
- Be prepared to submit emergency schedule requests if unexpected tasks come up.
- Present to staff for feedback again
- Budgeting team iron out bugs & review with Treasurer - Sept. 13-20
- Send budget to board - Sept. 24th = ideal; Oct. 1st = latest! (one to two weeks prior)
- Attempt to close out month for September in case any last minute things come to light.
- Board Meeting - Oct. 8th (2nd Wednesday of Quarter)
- Report back to each committee post-approval of Board
- Plug approved budget numbers into tables per committee, and/OR
- Email to staff with numbers
Generic Timeline
- Identify budgeting team of 2 (two) Beancounters
- File schedule requests (schedule at freegeek dot org) one month prior to week needed
- Schedule 4 hours per day for entire week for both Beancounters
- Budget team meets with Board Treasurer