List the values that build the total
Record the actions that add points and the conditions that deduct them. Include category limits, round weighting, multipliers, and any action counted only once. These details explain more than the headline total alone.
Use this event's rules rather than an older example. Choose priorities only after you know which actions contribute and how penalties apply. Otherwise, a plan may emphasize something that has little effect on the actual scoring system.
Treat the live table as unfinished information
A displayed total may not yet include a completed round, later credit, or reviewed penalty. Other participants' results can also settle while your own number stays unchanged, moving the relative ranking.
Inspect category details at round breaks. Note any pending label and keep a record of a significant change if needed. Repeatedly refreshing during active play adds little when the missing information has not yet settled.
Compare tied scores in the published order
Find the first criterion used when totals match, then the next only if the tie remains. The event may use direct results, a secondary score, completion time, a best round, or another stated measure.
Do not select whichever criterion seems most favorable. The published sequence determines which comparison applies. Save the final table and the relevant tie detail if you need to explain why equal scores received different positions.
Recalculate a disputed final category
Wait for all required rounds and reviews to finish and confirm that the event is marked final. Separate base values, additional factors, and deductions rather than comparing only two overall totals.
If one category still differs, give support the event identifier, rule value, relevant result screen, and your expected calculation. A report focused on that line is easier to verify than a general claim that the whole table is incorrect.
Apply caps and rounding at the right stage
Check whether a multiplier is applied before or after a cap and where decimal values are rounded. The same ingredients can produce different results if the operations are performed in a different order.
Use the event's worked example where one is available. Follow its sequence for the base value, multiplier, limit, and rounding rather than importing an assumed formula.
Show intermediate values when reporting a difference. That lets the reviewer identify whether the disagreement concerns the input, the ordering of operations, or the rounding step instead of guessing from a single final number.
