🏛️Governance, Transparency and Accountability

What governance is and why it matters

An organisation without governance is like a ship without a rudder — it moves as long as the water is calm, and sinks at the first storm.

Governance is the system of rules, practices, and procedures that determines how an organisation makes decisions and how authority is distributed among its different parties. In voluntary and community work, its importance increases because non-profit organisations operate on the trust of the community, funders, and beneficiaries — and trust erodes quickly when fateful decisions are made without transparency or accountability. Most organisation crises we hear about — corruption, discrimination, resource waste — do not arise from universal bad intent. They arise from the absence of a structure that stops the person before they err, or exposes the error after it occurs. Good governance is that structure.

Core governance policies

Three policies no serious organisation can do without: conflict of interest, data protection, and concern reporting.

Governance policies are not documents written once and forgotten — they are living frameworks that answer difficult questions before they arise. Three policies have proven their importance in most international evidence: **Conflict of interest policy:** defines who is obligated to declare, when, and what procedure applies when a conflict exists. Covers board members, employees, and volunteers in leadership positions. Principle: declaration does not necessarily mean recusal — it means removing the conflicted party from the specific decision. **Data protection policy:** defines what data the organisation collects, why, how it is stored, who accesses it, and how it is securely destroyed when the purpose ends. Protects beneficiaries, employees, and volunteers. **Whistleblowing policy:** gives any person — employee, volunteer, beneficiary — a safe channel to report serious concerns without fear of retaliation. Its absence silences internal witnesses.

Written policies do not apply themselves simply by existing. An organisation that has a conflict of interest policy but where nobody refers to it at the right moment has a document, not a tool. The gap between a written policy and actual application is one of the most common gaps in institutional governance, and bridging it requires a specific skill, not merely possessing the document. Reading and applying a policy involves three practical elements. First, understanding scope: the policy defines who it applies to and in which situations — a conflict of interest policy may cover only board members or extend to employees and volunteers in leadership positions, and knowing this scope precisely is the starting point. Second, identifying the moment of application: the policy is not applied after an error occurs but before — good practice means a responsible person asks themselves before any consequential decision: "Is there a policy that governs this situation?" Third, referring to the designated authority when uncertain: policies do not cover every case precisely, and when a situation falls in a grey area the correct step is not acting on personal interpretation but referring to the board chair or the advisor designated in the policy. The golden rule: a policy is not an obstacle to decision-making — it is a framework that makes the decision safer for the individual, the organisation, and those they serve.

The accountability cycle: from reporting to learning

Accountability that stops at punishment does not prevent recurrence. Complete accountability closes the loop by analysing the root cause and changing the system.

The accountability cycle in good organisations has four sides: Reporting (what happened?), Analysis (why did it happen?), Response (what do we change?), and Verification (did the change have an effect?). Many organisations master the first side and weaken the remaining three. Internal reports written then placed in a drawer improve no performance. Real accountability means: the manager sits with their team to review what happened, asks what could have been done differently, and adjusts processes based on the answer — not documenting the error and then repeating it.

1. Reporting: the responsible person writes an objective report of facts and figures
2. Analysis: the team identifies the root cause — is it human, organisational, or circumstantial?
3. Response: policy, procedure, or training is adjusted based on the root cause
4. Verification: in the next cycle, measurement checks whether the error recurred

Financial transparency is not merely disclosing numbers — it is a system that enables relevant parties to read, understand, and verify those numbers. In small and medium volunteering organisations, this typically means going beyond sending periodic account statements to building practices that embody transparency in daily routine, not just in moments of crisis. Four practical tools reinforce financial transparency in organisations. First, a detailed budget approved by the board: a general annual budget is not sufficient — a categorised budget that shows how each funding source was allocated to each activity enables the board to compare planned against actual. Second, monthly financial report: a financial summary (revenues, expenditures, balance) distributed regularly to board members transforms financial discussion from an annual event into a periodic habit. Third, separation of financial authorities: the person who authorises expenditure differs from the one who executes it, who differs from the one who reviews the accounts — this three-way separation narrows gaps for potential manipulation. Fourth, annual external audit: even in small organisations, an annual review by an independent body adds a layer of trust that internal audit alone cannot provide. The four tools together form a transparency system that protects the organisation from errors and violations and builds lasting trust with its funders and community.

Signs of weak governance and how to address them

Weak governance rarely comes suddenly — it sends signals before the crisis with enough time for those who know where to look.

Governance failure does not mean the collapse of the organisation — but it does mean a fundamental problem requiring an organised response, not emotional escalation or denial. Recognising the moment of failure and having a response protocol is itself part of good governance, because organisations that think in advance about what to do when they err make less destructive mistakes. Governance failure has graduated levels requiring graduated responses. Isolated failure is a wrong decision made outside the defined authority or a procedure that was not followed — the response: acknowledge what happened, correct immediately, document in the official record, and review what led to this slip. A recurring pattern is a procedure consistently breached or a policy consistently ignored — the response requires root cause analysis: is the policy impractical? Was the team insufficiently trained? Is there cultural pressure to ignore it? Then address the cause, not the symptom. Structural failure is the actual absence of board roles or one individual dominating collective decisions without oversight — here the response goes beyond the executive team and requires full board intervention or an emergency general assembly. The shared lesson across all levels: failure that is acknowledged and addressed transparently causes less long-term harm than failure that is concealed and accumulates until it brings the organisation down.

External accountability: funders, beneficiaries, and community

Internal accountability alone is not enough — the organisation is also accountable to those it serves, those who fund it, and the community in which it operates.

External accountability in non-profit work covers three circles: funders (who want to know their money was used as promised), beneficiaries (who deserve to know what service they receive and have the right to complain), and the wider community (which is positively or negatively affected by the organisation's activities). Beneficiaries especially are often neglected in the accountability chain — reports are written about them, not for them. Good practice involves beneficiaries in service evaluation, complaint channels, and sometimes strategic decisions.

The board's accountability over executive management is necessary but not sufficient on its own. The community the organisation serves — beneficiaries, families, surrounding residents — is the party most affected by its decisions and at the same time the least heard in its traditional processes. Modern governance redefines accountability to include this marginalised party rather than confining itself to internal formal circles. Accountability to the community manifests at four ascending levels. First, reporting: informing the community what the organisation does and what it has accomplished — a periodic bulletin or annual community gathering suffices. Second, listening: providing a regular channel to learn what the community sees in the organisation and what concerns it — questionnaires and community dialogue sessions are common and useful tools. Third, responding: having a public mechanism that shows how the organisation acted on feedback — "we heard your concern about this matter and here is what we did" is a simple sentence with a large impact on building trust. Fourth, participation in decision-making: at the highest level of accountability, beneficiaries are represented in committees or consultative bodies that genuinely influence the organisation's decisions rather than merely having their opinions heard. The organisation accountable only to its board is managed top-down. The organisation also accountable to its community builds a genuine partnership that amplifies its impact and grants its work a social legitimacy that protects it in difficult times.

The separation of powers within the organisation — between those who plan, execute, and review — is not an administrative luxury but a structural safeguard against errors and violations. When one person holds the authority to approve spending, sign off, and conduct review simultaneously, there is effectively no oversight system — even if that person is completely trustworthy. Systems are not built on trust in individuals but on procedures that make violations difficult and their detection easy. The principle of dual signatures on major financial transactions, separating who authorises spending from who executes it, and periodic oversight reporting mechanisms — these are all practical applications of this principle. The organisation that says "we trust each other and do not need all these procedures" confuses personal trust with governance requirements: trust is built in relationships, and procedures protect the institution from unintentional errors before intentional violations.

Building complaints and accountability mechanisms in the organisation is not a crisis response — but a preventive investment that averts larger crises. An organisation with a clear, activated complaints mechanism sends an implicit message to its beneficiaries and volunteers: "your voice is heard and we will act on what you report." This trust cannot be purchased with announcements. An effective mechanism answers four questions clearly: how do I submit a complaint? Who will process it? In how much time will it be processed? And how will I know the outcome? The absence of any of these answers reduces the mechanism's effectiveness and entrenches a feeling that complaints are filed in a drawer that is never opened.