Local Decision Making: Turning Policy Into Practice

What Local Decision Making means

Local Decision Making is based on a straightforward principle: Aboriginal communities should have a genuine say in decisions that affect them. Regional Alliances and local Assemblies provide structured ways for priorities to be identified and carried forward.

IRAAC works within this system while remaining an Aboriginal community organisation. Its responsibility is to stay connected to community rather than assume it already knows what people need.

The principle becomes meaningful only when participation can influence what happens next. A meeting, survey or consultation may collect views, but Local Decision Making requires a pathway from those views to a recorded priority, a responsible decision-maker and a response that comes back to community.

Different organisations hold different responsibilities. Community members identify experiences and priorities. Aboriginal organisations may deliver programs, represent issues or coordinate local action. Alliances and Assemblies can bring shared priorities together. Government agencies retain responsibility for the decisions, services and resources within their authority. Clear reporting helps readers see where each matter currently sits.

From a community issue to a shared priority

An issue may first be raised in a conversation, program, meeting, survey or request for assistance. IRAAC should record the issue in a way that protects the person while preserving the practical detail needed to understand it. Similar issues can then be grouped carefully, without assuming that every person experienced the same thing.

Before calling something a shared priority, IRAAC should check the evidence. It should ask who has been heard, who may be missing, whether the issue affects one place or several and whether people had a genuine opportunity to disagree or add context. An urgent individual matter can require action even when it is not yet a community-wide pattern.

When a priority is carried forward, community should know what wording is being used and what outcome is being sought. A broad phrase such as access to services may hide different needs involving transport, opening hours, cultural safety, eligibility or communication. Specific language makes it easier to identify who can act and whether the response addresses the issue that was actually raised.

What good participation requires

Participation should be accessible, voluntary and connected to a clear purpose. People need to know why IRAAC is asking, how their input may be used and whether the conversation is about service support, community reporting, program design or formal representation. Agreement to one purpose should not be treated as permission for every later use.

Several participation options are needed because a single meeting or online form will not reach everyone. Face-to-face conversations, community visits, program feedback and Have Your Say can complement one another. Each source should remain identifiable in the evidence so that a handful of responses is not presented as a complete community mandate.

IRAAC should make room for people who are less confident speaking in groups, need communication support or prefer to involve a trusted person. It should also report who was not reached when that gap affects the strength of a conclusion. Good participation is not measured only by attendance; it is measured by whether people could understand the question and contribute safely.

How reporting supports accountability

Community participation is more meaningful when people can see what followed. Reports should show what community said, what IRAAC raised, who responded, what changed and what remains unresolved.

A report should preserve the chain between the original issue and the action taken. If the wording changes as the matter moves through meetings or agencies, IRAAC should explain why. If a request is declined, delayed or redirected, the status should remain visible rather than disappearing from the next update.

Reporting also helps separate advocacy from delivery. IRAAC may be able to change its own program or referral process directly. Other matters require a decision from government or another organisation. Readers should be able to see which action belongs to IRAAC, which action has been requested from someone else and what evidence supports any claim of progress.

• State the community issue without identifying contributors.
• Record the action IRAAC took.
• Explain the response received.
• Give the current status in plain language.
• Provide a date for the next update.

A practical pathway for action

This pathway should be simple enough to use consistently. A complicated system can create its own barrier if staff cannot tell which matters are active or when an update is due. A clear issue register can support accountability, provided access is protected and public reports contain de-identified information only.

Not every issue will follow a straight line. New evidence may change the proposed response, responsibility may be shared or a community priority may need to be considered alongside another one. The record should show these changes rather than rewriting the history as though the final pathway was obvious from the beginning.

• Record the issue, source, date and consent boundaries in the protected system.
• Check whether immediate individual support is required before treating the matter as a policy issue.
• Test the wording with further community listening where a broader priority is being claimed.
• Identify the organisation or decision-maker with authority to act.
• Agree the action requested, the owner and the next review date.
• Return to community with the response, evidence of change or an honest explanation of delay.

The role of Alliances, Assemblies and organisations

Regional and local structures can help bring priorities together, test whether concerns are shared and coordinate engagement with government. Aboriginal community organisations contribute direct program and service experience. Community members bring the lived knowledge that gives a priority its meaning. Each role adds something different and should not be collapsed into a single organisational voice.

Representation requires a clear mandate. A person attending a meeting should know which matters they are authorised to speak on and how they will report back. Meeting participation alone does not prove that community endorsed every position discussed. Records should distinguish information shared, decisions made, actions accepted and matters requiring further consultation.

IRAAC can support this system by presenting issues in plain language, carrying evidence with care and maintaining an update pathway. It should not imply that it represents every Aboriginal person or organisation. Its authority comes from its role, its governance and the specific participation behind each matter.

How progress can be measured

Process measures can show whether the accountability pathway is functioning. These may include whether an issue has an owner, whether the responsible organisation acknowledged it, whether a next action and review date were recorded and whether community received an update. Such measures do not prove that the underlying issue has been solved.

Outcome evidence should relate to the change community asked for. Depending on the issue, that may involve improved access, a changed procedure, a funded activity, a service delivered differently or a barrier removed. The evidence and decision-maker will vary, so IRAAC should not use one generic success measure for every priority.

Community judgement remains essential. A change can be completed administratively and still fail to address the practical experience that led to the request. Follow-up should ask whether the response made a difference and what remains unresolved, while making clear that feedback is voluntary and will not affect access to support.

The standard IRAAC is working towards

The test is not how many meetings took place or how many documents were produced. The test is whether decisions and services reflect what community identified as important, and whether IRAAC returns with an honest account of progress.

That standard requires IRAAC to keep evidence, decisions and responsibilities connected. It should be possible to trace a public update back to a protected source record and an authorised organisational action without exposing the people who contributed. Claims should be reviewed before publication, especially where another organisation’s response is described.

The standard also includes reporting when progress is limited. Community trust is not served by removing unresolved matters from view or turning routine activity into an outcome. A concise explanation of what is delayed, who holds the next action and when it will be reviewed gives people more useful information than a general statement that work is continuing.

Future reports should include worked examples only where the underlying information is verified and safe to publish. Until then, IRAAC can report the framework it is building, the issues community chooses to raise and the actions that have been formally confirmed.

Questions for the next accountability update

Answering these questions consistently would allow later reports to show a genuine history of action. The aim is not to create more paperwork. It is to prevent community input from becoming disconnected from the decisions made in its name and to make responsibility visible when progress depends on several organisations.

• Which priorities currently have a recorded owner, action and review date?
• What evidence shows that the wording reflects the community issue originally raised?
• Which matters require wider listening before IRAAC presents them as shared priorities?
• What responses have government or partner organisations formally confirmed?
• Where has an action changed a service, program or practical barrier?
• Which matters remain unresolved, and when will community hear about them again?