# Manage motorsport data (schedule, championships, results)

Accurate motorsport data is one of the strongest trust signals on your profile.

## Why this matters

Sponsors and supporters use this information to understand:

* What you are racing
* Where your season is headed
* How performance is progressing

## What to maintain

Keep these sections updated:

* Motorsport profile (discipline, class, series)
* Race schedule (upcoming events)
* Championships and standings context
* Race results and notable milestones

## Best-practice cadence

* Update schedule when dates are confirmed
* Post results shortly after race weekends
* Add short context for key outcomes (for example: mechanical issue, weather conditions, strategy)

## What good data looks like

* Event names are consistent
* Dates are accurate
* Results are complete and easy to scan
* Major milestones include context, not just a finishing position

## Troubleshooting

### My data is incomplete across sections

* Start with upcoming schedule and latest result first
* Fill older data after core season timeline is complete

### Supporters do not understand progress

* Add short narrative context to results
* Link to a related update post for each important event

## FAQ

### Do I need every historical result?

No. Prioritise current season and recent momentum first.

### How detailed should race notes be?

Keep notes short and useful. Explain what happened and what it means for next events.

## Next steps

* [Post updates and content](/reference-guides/updates-and-content.md)
* [Understand analytics and transactions](/reference-guides/analytics-and-transactions.md)


---

# Agent Instructions: 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:

```
GET https://docs.sponsordriven.com/reference-guides/motorsport-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.