> For the complete documentation index, see [llms.txt](https://docs.washthru.lol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.washthru.lol/keeping-and-managing-alliances/monthly-check-ins.md).

# Monthly Check Ins

1. Every Month, please send this format into every alliance channel in the WashThru Affiliates Server.

```
# 🤝 | Monthly Evaluation

Greetings,

As a new month approaches, we would like to ask a few questions regarding our partnership:

- How is the **NAME OF THE COMMUNITY** doing currently?
- How would you describe our partnership so far?
- Is there anything we could improve (related to our partnership or otherwise), and why?
- Are there any exciting events or launches coming up soon?

Deadline: **Discord Timestamp**

-# Partner Role
```

2. If they don’t reply in time please let the department director know via <bread@washthru.lol> or via DMs.


---

# 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://docs.washthru.lol/keeping-and-managing-alliances/monthly-check-ins.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.
