In this lecture
- Read a budget circular for its GSI requirements
- Run a compliance check before submission
- Avoid the most common reasons a submission is returned
The circular already tells you what it wants
Budget circulars increasingly state their gender-responsive requirements directly - a disaggregation requirement, a mandatory statement, a specific annex. Missing a stated requirement is an avoidable rejection, not a technical judgment call, and a checklist against the circular's own text catches most of them.
The three reasons submissions come back
In practice, most GRB submissions are returned for the same three reasons: no baseline data, a claim with no evidence behind it, or a gender budget statement that restates the budget without analysis. Checking a draft against these three before submission clears most of a review cycle.
Materials
Yours to keep, and usable away from the platform.
- Budget circular GSI compliance checklistWorksheet · 90 KB
Design prototype - the attachments are placeholders and nothing downloads yet.
Lecture quiz
4 questions, plus 2 written questions at the end - taken whenever you are ready. This is what unlocks the next lecture.