Assessors read a lot of budgets, and they can tell within a page which kind they're holding: one built bottom-up from real costs, or one reverse-engineered from the funding cap with categories inflated until the numbers fit. A defensible grant budget template is the first kind. The second kind doesn't just score worse. If it wins, it becomes a delivery problem, because you now have to acquit spending against a fiction.
This sits in the non-dilutive funding cluster, downstream of readiness and feeding the application.
The method is unglamorous. List the activities the project narrative commits to. Cost each one from evidence: quotes for purchases, market rates for roles, your actual rates for internal time. Sum it. The total is the total. If it lands under the programme cap, good; you ask for what the project costs, which reads as exactly what it is. If it lands over, the project descopes honestly rather than the unit costs quietly shrinking to fit, because those shrunken costs become your delivery reality.
Every line should answer four questions before an assessor has to ask:
| Field | Example |
|---|---|
| Item and quantity | Workshop facilitation, 8 sessions |
| Unit cost and basis | AUD $1,200 per session, quote attached from provider |
| Link to activity | Delivers milestone 2, community capability workshops |
| Who pays | Programme funds, or co-contribution |
The justification column is where weak budgets die. "Marketing: $15,000" invites questions. "Campaign production and media for participant recruitment, itemised below, based on prior campaign actuals" closes them.
Many programmes expect you to bring something: cash, staff time, facilities, equipment use. Two rules keep this clean. Value in-kind at defensible market rates with the basis written down, and only commit contributions you can evidence later, because co-contributions get acquitted too. A worked example of the trap: committing "200 hours of director time" valued generously, then having no timesheet system to prove a single hour at acquittal. The commitment was free to write and expensive to have written.
The application's narrative and budget are read against each other. Every activity in the narrative should be findable in the budget; every budget line should trace to a narrative commitment. Orphans on either side read as careless, and assessors extrapolate carelessness forward into delivery. Before submission, one person reads only for that cross-match.
Detailed enough that no line invites a question: item, quantity, unit cost, cost basis and the activity it delivers. Attach quotes where they exist.
Usually yes, within the caps set out in programme guidance. Claim them transparently rather than distributing them through other lines.
Non-cash contributions you bring to the project: staff time, facilities, equipment use, valued at defensible market rates. Commit only what you can evidence, because co-contributions are acquitted alongside the funding.
Qwrki runs grant and programme operations as part of the operating layer, so the budget you submit is the same budget you can acquit later. We cost activities from real evidence, keep in-kind commitments tied to systems that can prove them, and hold the budget and narrative in lockstep through delivery. Book a call if you want a read-through of a budget before it goes in.
What non-dilutive funding is, how it compares to equity and debt, who it suits, and what the operating burden really looks like.
A grant readiness checklist covering governance, financials, project definition and delivery capacity, so the application writes itself and the audit holds.
How milestone reporting works on funded programmes: capture evidence as you deliver, report on the funder's rhythm, and never reconstruct from memory.
