> For the complete documentation index, see [llms.txt](https://docs.monitool.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monitool.org/readme.md). # What Is It?

Monitool is a platform to host, organize and share logical frameworks for humanitarian organizations. Instead of being "Yet Another Form Builder v2.0 ®", it heavily focuses on helping projects get their monitoring and data management planning right. * Which indicators will you use? * Do you have access to data-sources that will enable you to measure them? How often? At which level of detail? * Once you start measuring them, which figures do you expect to find? * How much of your operative staff time are you willing to allocate to data collection? Who is responsible for what? * Will the effects of your project be able to change those indicators in a reasonable timeframe? * Which corrective actions on your project did you plan in advance for each indicator? Those are the questions that we hope using Monitool will help you answer, write down in a tidy manner, and share with your team and staff. Oh, and also, we did make a form builder. --- # 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.monitool.org/readme.md?ask=&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.