A PRACTICAL Audi GUIDE

How Audi Event Scores and Tie Breaks Are Decided guide illustration

How Audi Event Scores and Tie Breaks Are Decided

Read an event score as separate pieces: base points, multipliers, penalties, and tie rules. A live rank alone can mislead.

This walkthrough covers provisional totals, final corrections, and the evidence to save if a settled score still seems wrong.

For live dates and account-specific rules, use the current page in Audi.

THE DETAILS

Work through the key points

Translate the Rules Into a Scoring Map visual guide

Translate the Rules Into a Scoring Map

Turn the rules into a small score map: base points, caps, multipliers, penalties, and categories that count once.

Use the current event rules. A similar event from last month may have changed one value that alters the result.

  • Mark every cap and multiplier.
  • Log penalty triggers.
  • Log how each round is weighted.
  • Write down the base values.
Treat the Live Table as Unfinished visual guide

Treat the Live Table as Unfinished

A live score can omit a pending round or later penalty. Rank can also move when another entrant’s result settles.

Check categories at natural breaks, not after every action. The final marker matters more than repeated live refreshes.

  • Do not treat a live rank as final.
  • Keep key score changes.
  • Look out for pending categories.
  • Read between rounds.

Apply Tie-Break Rules in Sequence

When totals tie, compare the published criteria in order. Head-to-head, completion time, or another measure may decide it.

Stop at the first criterion that separates the entries. Save the settled table showing which rule was applied.

  • Keep the resolved rank.
  • Locate the first tie-break.
  • Work through the criteria in their published order.
  • Double-check whether time is measured.

Investigate a Final Score Difference

Wait until all rounds and reviews are complete. Then compare base points, multipliers, penalties, and tie rules line by line.

If one category still differs, send support the event ID, rule value, expected calculation, and result screen.

  • Double-check final competition status.
  • Recalculate the categories separately.
  • Include the matching rule.
  • Report the one value you dispute.

How Multipliers, Caps and Rounding Interact

A cap can apply before or after a multiplier, and rounding can change the final number. The event rules should state the sequence.

Write out each step of your calculation if you report an issue. A bare final total is much harder to verify.

Show each part of the math in a report. The intermediate figures let support locate a difference faster than a final total alone.

  • Install each category cap in the stated place.
  • Choose the published rounding guideline.
  • Show the values between each step.
  • Look over the order of operations.

PUT IT INTO PRACTICE

Follow these steps in order

1

Create your scoring map

Build a list of base values, multipliers, caps, penalties, and weighted rounds.

2

Choose what to prioritize

Focus on dependable actions that match the event format.

3

Read the score between rounds

Read the category totals at breaks instead of watching rank constantly.

4

Work through tie-breaks in order

Use each tie criterion in the order printed in the rules.

5

Double-check the completed result

Match the final categories and save the first clear difference.

IF YOU GET STUCK

Check these likely causes

The total is below your calculation

Look for a cap, penalty, unfinished round, or category restriction that changed the total.

  • Look over the detailed breakdown.
  • Match the guideline line for that category.

The rank moved but the score did not

Another result, correction, or tie rule can move your place without changing your own points.

  • Go to the tie-break information.
  • Hold off until the table is final.

KEEP READING

Guides connected to this task

QUICK ANSWERS

Questions readers ask about this

Another entrant’s result or a correction may have settled, or a tie rule may now separate the scores.
Give the event ID, final status, disputed line, rule value, expected math, and a readable result image.