> For the complete documentation index, see [llms.txt](https://usecaseframework.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usecaseframework.openactive.io/appendix-three-mel-framework/overview.md).

# Overview

This is a guidance document to help use case communities measure their work against the OA strategic outcomes. The benefit of this is to aggregate impact more simply, widely, confidently and consistently. With the MEL framework below, we are implementing a consistent approach to demonstrating impact across OA.

As part of the initiative’s commitment to [open working](https://www.sportengland.org/unlocking-digital-innovation-power-open-working), use case communities are encouraged to publish the provided template openly, and provide regular updates on progress via the [Adoption and Engagement Forum](https://www.openactive.io/get-involved/) at each of the agreed monitoring milestones (Step 3) and on completion of the project (Step 4).

<figure><img src="/files/bgLvsZVPdg023wx1YX4l" alt="Use case MEL steps: One - define SMART objectives. Two - define measurable KPIs. Three - measure use case delivery. Four - share learning. These steps are designed against the OA outcomes: One - The sport and physical activity sector is serviced by a truly independent initiative capable of meeting the needs of industry, policy and society. Two - OpenActive becomes integral national data infrastructure that is responsibly maintained and governed. Three - Reduce inequalities to entry in the sport and physical activity sector to improve the population’s health and wellbeing, including those historically under-serviced in the sector."><figcaption><p>MEL framework</p></figcaption></figure>


---

# 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://usecaseframework.openactive.io/appendix-three-mel-framework/overview.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.