> For the complete documentation index, see [llms.txt](https://docs.stawishadada.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stawishadada.org/policies/accountability.md).

# Accountability and use of funds

How Stawisha Dada Women Group manages donations, equipment and spending: bank account, receipts, inventory and reporting to funders.

{% hint style="warning" %}
**Draft awaiting committee approval.** Approved on: \_\_\_\_\_\_\_\_\_\_\_\_ · Next review: \_\_\_\_\_\_\_\_\_\_\_\_
{% endhint %}

Stawisha Dada Women Group is a registered community organisation (Reg. No. DSD/26/137/01/258934, Directorate of Social Development, Endebess Sub-County). We exist for our community purposes, not for the private profit of any member.

## How we manage money

* Funds are kept in the **organisation's bank account**, not in any member's personal account.
* Spending is approved by the committee and recorded. Payments need more than one official to authorise them.
* We keep a **receipt** for every purchase.
* Donations are used for the **purpose the donor gave them for**. If that is not possible, we ask the donor first.
* The Treasurer reports on income and spending at committee meetings, and accounts are shared with members.

## How we manage equipment

* Machines, computers and tools belong to the **organisation**, not to any member.
* All equipment is recorded in an **inventory** and kept in a lockable workshop.
* Equipment is not lent, sold or taken home without committee approval.

## Avoiding double funding

When we ask more than one funder for the same item, we tell every funder as soon as one agrees, so that nothing is paid for twice.

## Reporting

We report to funders and members on what was bought, how many people were trained and how many trainees are earning, using totals that protect individuals' privacy.

## Conflicts of interest

Any official, staff member or volunteer who could benefit personally from a decision (for example, if a supplier is a relative) must say so and take no part in that decision.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stawishadada.org/policies/accountability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
