> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/evaluation/how-can-we-evaluate-our-efforts-to-be-more-diverse-and-inclusive/evaluation-hints-and-tips.md).
# Evaluation Hints & Tips
It is important to take a moment mid-way through our journey, or at the completion of key milestones or events, to take the time to reflect on how things went, and to evaluate whether our objectives have been met, or are being met. This process should be more than a check-box exercise, and not done simply to make a funder, investor, or outside party happy. It is rather an opportunity to check-in with your progress in comparison with your aims, and to make adjustments along the way where needed. And ultimately, it is a good way to hold a leadership team or partnership accountable to those who have a stake in the issue.
It is therefore important to include key stakeholders in your evaluation process, to gather crucial feedback and insights, but also to ensure that we are being inclusive and equitable in our actions.
The Association for Science and Discovery Centres in the UK advises its members and partners to take a strategic, long-term approach to setting up evaluation frameworks, and to assist them in this has developed handy list of hints and tips. These aim to help ensure that the expectations of stakeholders and participants are be adequately explored and met.
"*Enabling all stakeholders to take part in the evaluation process in an open and transparent way is the key to embedding the learning process for all participants. It reduces the risk that participants become subjects of someone else’s observation and research or are ‘left hanging’ at the end of a project without suitable feedback or understanding of their participation*."
1. The first step is to think about who should be involved in the reflection and evaluation process,
2. Make sure that you have clearly stated your aims and objectives as a project or initiative,
3. Discuss these with key partners and stakeholders from the very beginning, to ensure that their aims and objectives are also accounted for, and that your activity planning is well aligned with these aims,
4. It can be helpful to lay out a logical series of steps that describe how to achieve the impacts or outcomes you are aiming for, both the aims and those steps can thus form the basis for evaluation of whether things are on track
SOURCE:
**The UK Association for Science & Discover Centres Evaluation Hints & Tips**
* [Programme Evaluation leaflet (PDF, 1.6MB)](https://inclusion.sciencecentres.org.uk/documents/33/ASDC_Evaluation_leaflet_final.pdf)
---
# 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://inclusivity.toolkit.citiobs.eu/evaluation/how-can-we-evaluate-our-efforts-to-be-more-diverse-and-inclusive/evaluation-hints-and-tips.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.
