Grant Readiness Checklist for Australian Community Groups

Prepare the project, evidence and committee handover before a grant round opens. Leave application-specific answers and decisions until you have checked the current guidelines.

For Australian community groups preparing for grants, our recommendation is to build a reusable working folder—not a finished application. Use the OpenCommunities workflow below to organise preparation, assign responsibility and identify what still needs checking. These are practical recommendations, not grant eligibility rules or a promise of funding.

Key takeaways

Write a clear project brief before drafting application answers.
Keep evidence, supporting documents and unresolved questions together.
Give each preparation task an owner and a backup.
Ask potential supporters early, with a specific project outline.
Recheck every reused document against the current grant guidelines.

Clarify the project and community need

Start with a short project brief that another committee member can understand without a verbal explanation. We recommend answering these questions:

Purpose: What do you want to do, and for whom?
Need: What information supports the need for this project?
Activities: What work are you proposing?
Outcome: What change would you look for, and how would you assess it?
Capacity: Who could coordinate the work, and what remains unconfirmed?

Keep the distinction between evidence and intention visible. Label a proposed activity as a proposal; do not describe a hoped-for outcome as an achieved result.

Community Grants Hub guidance says strong applications should be supported by evidence such as quantitative data and evaluation findings, and information about an organisation’s financial capability.

Our recommendation: beside each statement about community need, record the supporting document, who supplied it and any limitations. If you cannot support a statement yet, mark it as a question to investigate rather than filling the gap with an assumption.

Build a reusable grant-readiness folder

Use these suggested sections as a working checklist. Do not treat them as documents every grant requires.

Project brief: The purpose, intended participants, proposed activities and intended outcomes.
Organisation background: A committee-reviewed description of your group, its activities and relevant experience.
Evidence: Relevant feedback, activity records, evaluation findings and quantitative information you already hold.
Project delivery: A draft task list, proposed schedule, volunteer responsibilities and dependencies.
Cost working notes: Proposed items, estimate sources, supplier information and assumptions requiring confirmation.
Support: Potential supporters, correspondence and draft or confirmed letters.
Current-round checks: Questions to resolve when guidelines become available.
Committee decisions: Agreed responsibilities, unresolved issues and the next review point.

Keep draft material separate from committee-approved material. For each document, record its owner, review date and status, such as draft, checked or awaiting confirmation. Restrict access to sensitive material to the people who need it.

If you are reviewing your wider administration setup, use the community management platform overview as a discussion starting point. Keep the grant checklist focused on what your committee needs, rather than assuming software will resolve every preparation task.

Assign owners and backups

We recommend giving every outstanding task a named owner and a backup. Ask the owner to record what is complete, what is missing and what the backup should do if they become unavailable.

Project lead: Maintain the brief and proposed delivery plan.
Evidence coordinator: Match supporting material to project statements.
Cost coordinator: Gather estimates and flag assumptions for committee review.
Support contact: Coordinate requests for letters and record responses.
Application coordinator: Maintain the checklist and check the current guidelines when available.

Combine roles if that suits your group, but explicitly agree who will review the application before submission. For an administration review alongside this work, explore membership and committee permissions and consider who should have access to which records.

Request meaningful letters of support

The City of Sydney says strong letters of support are more persuasive when requested early and when they are specific, dated, signed, and explain the supporter’s connection to the project and the benefit it will bring. Treat this as local guidance, not a universal requirement for every grant.

Our recommendation is to send potential supporters a clear brief and ask whether they are willing to support the proposed project. Invite them to describe their own connection and perspective rather than simply sign a generic endorsement.

Distinguish an expression of support from a commitment to provide a venue, equipment or volunteer time. Ask supporters to confirm any proposed contribution, and leave unconfirmed contributions clearly marked. Before using a letter, check that it still describes the project you intend to submit.

Consider your member and community communications approach when deciding who will send requests and keep the committee informed.

Prepare cost notes and unresolved permissions

For project planning, list proposed activities and the resources you would need to deliver them. Record the source of each cost estimate and flag anything that needs refreshing. Keep confirmed resources separate from hoped-for contributions.

Create a separate list of questions about venues, equipment, partner involvement and any permissions to investigate. Assign someone to check each question with the relevant contact. Do not mark an arrangement as confirmed until you have confirmation.

When a grant opens, compare these working notes with its current conditions before turning them into an application budget or delivery commitment.

A hypothetical committee handover

Hypothetical example—not an OpenCommunities customer story: A volunteer-led community garden group is considering a shared-tools project.

In this example, the project lead prepares a brief but leaves the purchase list marked as draft. The evidence coordinator gathers existing participant feedback. Another volunteer requests equipment estimates, while the support contact asks a potential venue partner whether it would support the proposal.

The committee leaves the application status as “not yet assessed”. The handover note asks the backup coordinator to check eligibility, project fit, current estimates and the venue response when guidelines become available—not to submit the draft unchanged.

Run a readiness review before deciding to apply

Use this recommended checklist at a committee review:

Can someone outside the project team understand the brief?
Does each statement about need or past activity have supporting evidence?
Are estimates, assumptions and unconfirmed contributions clearly labelled?
Have volunteers agreed to their proposed responsibilities?
Can a backup find the latest checked documents?
Are support letters consistent with the proposed project?
Have unresolved questions been assigned to someone?

Recheck the current conditions when applications open

Before drafting final answers, check eligibility, assessment criteria, required attachments, permitted project activities, timing and submission instructions against the current guidelines. Use the funder’s contact channel for unresolved questions.

Then make an explicit apply, clarify or pause decision. We recommend proceeding only when the project fits the opportunity, the committee is comfortable with the proposed resource commitments and volunteers have agreed to the delivery workload. Do not reshape the group’s purpose simply to match an available grant.

If you want to review the administration behind this preparation, explore the relevant platform pages above, then start a conversation about your community group’s needs.

Get grant-ready before applications open: a community committee checklist