> 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/step-by-step-guide.md).
# Step by step guide
## Step 1: Define SMART Objectives against the OA outcomes your use case supports
Create Specific, Measurable, Attainable, Relevant, and Time-Bound (SMART) objectives for your use case that support the three OA strategic outcomes of being an independent initiative, becoming integral national data infrastructure, and reducing inequalities in the sport and physical activity sector. This step should be completed during '[Understand and plan](/understand-and-plan/stage-outline.md)’.
## Step 2: Define measurable KPIs for each objective
Key Performance Indicators (KPIs) will be used to measure whether the objectives you set have been achieved or are on track. Some examples could include:
* increased levels of activity within disproportionately affected demographics
* commitment to inclusive governance
* new metrics demonstrating ambition to reach under-represented groups
* increase opening up access to opportunities data
* participatory case studies
* increased level of engagement with a diverse range of groups across sectors
This step should be completed during '[Understand and plan](/understand-and-plan/stage-outline.md)’.
## Step 3: Measure use case delivery
By measurement, we mean that the KPIs will be assessed continually over the life-cycle of a pilot, with pre-agreed milestones. Monitoring is the systematic measurement of the use case pilot's progress. It often entails the use of KPIs and other measurement activities. The information collected here will generate a useful evidence base to be reviewed regularly, to demonstrate each use case’s contribution to OA's outcomes. This step should be completed during ‘[Develop](/develop/stage-outline.md)’. One suggested way to monitor performance is to use a ‘RAG’ rating (red, amber, green).
Percentage
RAG monitoring
Meaning
0-40%
Blocked or not relevant
We failed to make progress and/or the KPIs are not relevant to us any more.
40-70%
In progress
We made progress, but fell short of completion.
70-100%
Accomplished
We delivered.
## Step 4: Share learning
The key to learning is the application of insights to improve use case work. Learning involves making improvements, either during the use case rollout or for the next time you do similar work. Tools to support learning and reflection include summary reports of KPIs, process evaluations and case studies. This step should be completed during ‘[Learn and publish](/learn-and-publish/stage-outline.md)’.
The intention is to collate the shared learning from use case communities to build an evidence base demonstrating the impact of OA. This will help to improve and grow the initiative. With these efforts, we hope to increase the levels of activity within disproportionately affected demographics, including:
* children and young people
* older people
* women and girls
* people from lower socioeconomic backgrounds
* disabled people
* ethnically diverse communities
## Further reading
* [Improving impact: Our approach to monitoring, evaluation and learning](https://openactiveio.medium.com/improving-impact-our-approach-to-monitoring-evaluation-and-learning-c805f5ba4341)
* [Sport England Evaluation Framework](https://evaluationframework.sportengland.org/)
---
# 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/step-by-step-guide.md?ask=&goal=
```
`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.