Skip to content
Back to UMA

Post-Race Routine

This page is the normal post-race verification sequence.

After the event, the system starts connecting the race result to the rest of the platform.

That can affect:

  • purse money
  • sponsor income
  • sponsor bonus income
  • damage and tire costs
  • travel and staff expenses
  • contract salary and winnings share
  • sponsor relationship history

If something is wrong after the event, the correct response is not to scan everything at once.

The correct response is to verify the systems in a sensible order.

Step 1: Confirm the Basic Event Outcome

Before doing anything else, make sure the event outcome passes a basic sanity check.

You are looking for obvious mismatches such as:

  • the wrong driver
  • the wrong car context
  • an obviously incorrect finish result
  • an event that clearly did not process the way you expected

If the core event outcome is wrong, stop there.

Do not try to interpret finances or sponsorship effects until the event itself makes sense.

Step 2: Review the Car Account

Once the event outcome looks reasonable, open Finances and review the car account for the affected entry.

This is usually where the most important post-race movement will appear.

Typical categories to review include:

  • league purse
  • media revenue
  • sponsor income
  • sponsor bonus income
  • tire cost
  • damage cost
  • travel cost
  • team travel and lodging
  • staff cost
  • salary
  • winnings share

You are not looking for a perfect profit result here.

You are checking whether the categories that should have posted actually posted to the correct account.

Step 3: Review the Organization Account if Needed

If your question is about team-level money, move to the organization account.

That is where you should review things like:

  • manufacturer support
  • organization overhead
  • transfer activity

Do not expect those rows to be sitting in the car account.

If you check the wrong account, the page will look wrong even when the system is working correctly.

Step 4: Review Sponsorship Outcome

Open Sponsorships and confirm the sponsor side of the event makes sense.

Check for:

  • the sponsor commitment that was actually used
  • whether the base sponsor payout posted
  • whether any bonus was achieved
  • whether relationship history now reflects the completed race

If a sponsor bonus was expected and it did not appear, this is one of the first places to inspect.

Step 5: Review Contract Expectations if Costs Look Wrong

If salary or winnings-share behavior looks incorrect, go back to Contracts.

Check whether:

  • the contract was active on the event date
  • the correct driver and series were attached
  • the contract type actually allowed the event to count
  • the deal had already expired or become completed

This is the right time to verify the contract. Not before the event outcome and account scope checks.

Step 6: Confirm Next-Week Readiness

Once the post-race review looks clean, use the same pass to prepare for the next week.

That usually means checking:

  • whether the next race assignments still make sense
  • whether sponsorship coverage for the next event is already visible
  • whether the car account balance still looks workable
  • whether the contract state still matches your plan going forward

This keeps one race weekend from creating confusion in the next one.

When to Stop and Investigate

Stop the post-race review as soon as the first foundational layer looks wrong.

That usually means:

  • the event outcome itself is wrong
  • the wrong car account is being reviewed
  • the contract clearly does not apply
  • the sponsorship state does not match what was accepted

Do not keep chasing downstream finance rows if the upstream state is already broken.

Common Post-Race Mistakes

Starting with sponsor relationship questions before checking payouts

The payout layer should make sense first. Relationship history is downstream from actual sponsored race completion.

Assuming a missing line means the system failed

First verify:

  • the right account
  • the right event
  • the right contract state
  • the right sponsor state

Most missing-row reports are actually context mistakes.

Looking only at totals

Totals are useful, but the grouped ledger rows usually explain more than the headline numbers do.

Forgetting that results rebuilds can reset finance rows

If results were deleted or repaired, event-close rows may also have been cleared and rebuilt. That is expected behavior.

Final Reminder

A good post-race routine is mainly about verification order.

Check the event outcome first. Then check the account scope. Then check sponsorship and contract context only if the financial result still looks wrong.

That is the shortest path to the real issue.

Customer-facing documentation for Racing League Manager.