> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/your-project-guides/step-by-step-tutorials/how-to-be-transparent-about-project-progress.md).

# How to Be Transparent About Project Progress

Here are the key components of a strong transparency practice:

#### 1. Honesty

Things won’t always go as planned — and that’s okay. Be upfront about setbacks, delays, or changes in direction. Your community will respect honesty far more than silence or spin.

#### 2. Regularity

Consistency builds trust. Share weekly or monthly updates, even if progress feels small. A steady rhythm of communication shows you’re active and accountable.

#### 3. Visual Storytelling

Words are good, but visuals make it real. Share photos, short videos, or even interviews with the people you’re impacting. Faces and voices are powerful proof of progress.

#### 4. Metrics

Numbers speak louder than words. Track and share concrete metrics — funds raised vs. funds spent, number of beneficiaries reached, milestones achieved. Even simple stats go a long way in proving impact.

#### 5. Right Channels

Make sure your updates reach the people who care most. Post on Geyser so contributors get updates directly by email, and amplify through social media for broader reach.

#### 6. Verification

Where possible, back up your claims. Link to receipts, spreadsheets, or external references. Transparency isn’t just telling, it’s showing.

#### 7. Gratitude

Always close the loop by thanking your supporters. People don’t just fund projects; they want to feel part of the journey. Recognition reinforces connection.

***

{% hint style="success" %}
**In short:** Honesty, consistency, proof, and gratitude are the cornerstones of transparency. If you share openly, regularly, and with evidence, your supporters will not only trust you — they’ll be more likely to keep supporting you.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.geyser.fund/geyser-docs/your-project-guides/step-by-step-tutorials/how-to-be-transparent-about-project-progress.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.