> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-budget-committee/archive/2024-updates/september-monthly-update/weekly-catchup-17-09-2024.md).

# Weekly Catchup \[17/09/2024]

## Agenda

1. Update from Process Workshop Florida
2. Comms Update
3. Committee Proposal Tracking Updates

## Notes

The budget committee met to discuss streamlining their process and setting financial parameters for the upcoming year. The key points discussed were:

* A proposal to hold half-day sessions to cover multiple topics more efficiently.
* Suggestion of a net change limit of 300 million for the year to prevent Treasury depletion.
* Consideration of forming a working group to gain approval for the proposed limit.
* Discussion on adopting a rolling forecast approach to budgeting.
* Proposal for quarterly financial reviews with core services and hubs.
* Emphasis on the need for a detailed budget proposal, including contingency plans.
* Importance of involving all stakeholders, particularly mentioning Catalyst and the MCC.
* Consideration of travel plans and potential scheduling conflicts with other events.
* Discussion on the budget committee's responsibilities, including managing funds and ensuring transparency.
* Debate on the necessity and amount of contingency funds for unexpected expenses.
* Presentation of a proposed budget covering various areas such as core maintenance, research, and marketing.
* Plans to coordinate with other stakeholders and communicate the budget process effectively.

The meeting concluded with plans to schedule further discussions, finalize the budget timeline, and continue coordination with all relevant parties.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://committees.docs.intersectmbo.org/intersect-budget-committee/archive/2024-updates/september-monthly-update/weekly-catchup-17-09-2024.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.