A grants officer at the Department of Social Services will read hundreds of submissions in a funding round. They have a shortlist meeting on a Friday. By the time they get to your submission, they have read another forty that day. The submissions that survive that meeting all have one thing in common - the first three paragraphs did the work.
Everything that follows is just evidence that the opening promise can be kept.
What the first three paragraphs need to do
- 01Name the problem in the funder's own framing - not yours
- 02State the outcome you will produce, in numbers, in time, for a defined population
- 03Show why your organisation is the right one to do it - in one sentence
If your opening does not do those three things, you are asking a busy reader to keep reading on faith. Most do not.
Speak the funder's language
Every DSS round comes with guidelines that include the priorities, the outcomes framework, and the eligibility criteria in plain text. The language in those documents is the language your submission should use. Not because you are gaming it - because that is how the panel scores.
If the guideline talks about community resilience, your submission should not be calling it community capacity. Match the phrasing. Mirror the structure of their priorities. Make the marker's job easy.
The outcomes paragraph is everything
A vague outcomes paragraph kills a submission faster than a weak budget. Specifics matter. Who, how many, by when, measured how.
The budget that reads like the program
Panels can tell when a budget has been built bottom-up from the actual work, versus when it has been reverse-engineered to hit a number. Show your assumptions. Tie line items to activities described in the proposal. If your program description talks about a part-time outreach worker, the budget had better show one - at a believable rate.
Most submissions are not rejected for being wrong. They are rejected for being unreadable on the third skim of the day.
Evidence beats adjectives
Words like innovative, transformative and best-practice are background noise. Evidence does the work. A previous program with measured outcomes, a letter of support from a referring agency, a partnership MOU, a needs analysis from the LGA. Anything you can point to that is not just your own assertion.
Submit early. Re-read out loud.
Final test before you hit submit - read it aloud, in your office, to the operations manager who will actually run the program. If they do not recognise the program in the words, you have written for the funder but not for the work. Rewrite. Submit a day early.
