# Post updates and content

Updates turn profile visitors into long-term supporters by showing momentum and credibility.

## What to post

Focus on content that proves progression:

* Race prep and race-week updates
* Results and debriefs
* Testing and development progress
* Sponsor mentions and supporter thank-yous
* Clear next milestones

## Posting rhythm

A simple rhythm that works for most competitors:

* 2 to 3 short posts per week
* One race-focused update around each event
* One gratitude or supporter-impact post each week

## Structure for high-performing updates

Use this format:

1. What happened
2. Why it matters
3. What is next
4. How supporters can help

## Content quality tips

* Use real photos from events and paddock life
* Keep tone clear and specific
* Avoid posting only asks for funding without progress context

## Troubleshooting

### My updates are getting low engagement

* Use clearer headlines in first sentence
* Add stronger visuals
* Tie every post to a concrete milestone

### I struggle to post consistently

* Batch draft 3 short updates at once
* Reuse a simple template per race weekend

## FAQ

### Should every update include a funding ask?

No. Most updates should show progress, with occasional clear calls to action.

### Can I reuse updates from social channels?

Yes, but adapt them for Sponsor Driven with context around your season and support goals.

## Next steps

* [Promotion tips](/reference-guides/promotion-tips.md)
* [Create sponsorship tiers and deals](/reference-guides/sponsorship-tiers-and-deals.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/updates-and-content.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.