> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/pro-system/reviewing-matches-in-the-dashboard/reviewing-match-points.md).

# Reviewing Match Points in App

{% hint style="info" %}
The match and game points can only be reviewed on the iOS and Android apps. Reviewing match points on Web App is in development.
{% endhint %}

To review the points captured on a Scoreboard during a Match or Game, the Customer can:

1. Navigate in their App
2. Click on the `Reservations` or `My Bookings` tab
3. Click on the `History / Replay` tab at the top
4. Select the Reservation or Event where they used the Scoreboard
5. Scroll to the bottom of the Reservation or Event, past any Replays captured (or the Event description)
6. View the points scored during a match

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FWLQLtqm3Oz4GBOfPljvj%2Fimage.png?alt=media&amp;token=a65fbb91-9f34-4875-8502-a21fd3f22056" alt=""><figcaption></figcaption></figure>

### Related

* [DUPR Ratings](/pro-system/rating-systems/dupr-ratings.md)
* [DUPR Challenge Match](/pro-system/dupr-challenge-match.md)
* [Match Replays](/replays/overview-of-replays/match-replays.md)


---

# 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.podplay.app/pro-system/reviewing-matches-in-the-dashboard/reviewing-match-points.md?ask=<question>&goal=<user_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.