Two staff tools keep the standings honest: the review queue decides which sessions count, and adjustments correct points the engine cannot know about. Both leave a trail.
The review queue
Manage → Review Queue holds every session automatic import was not certain about. This happens when more than one session could be your league's race: a rescheduled launch inside the tolerance window, or two sessions in the same hour. Nothing ambiguous is ever scored automatically.
For each item you see the candidate sessions with enough context to tell them apart (start time, field, splits). Pick the right one and it imports and scores immediately; dismiss the others. If the real race never appeared at all, import it directly by subsession ID from Manage → Events (see How races get into your league).
Stewards and above can work the queue.
Adjustments
Adjustments are manual points entries scoped to a driver and a week: stewards' penalties (points deducted after an incident review) or awards the rulebook does not cover.
Open the championship's Adjustments page from Manage → Scoring. Each adjustment records who entered it, the amount, the scope and the reason, and the standings recompute immediately. The reason is kept on record, so a mid-season penalty is still explainable at the finale.
Use adjustments, not rulebook edits, for one-off corrections: editing the rulebook rescores the whole season, while an adjustment touches exactly one driver-week and nothing else.
The audit log
Staff actions in Manage (invite redemptions, scoring publishes, adjustments and more) are recorded in the league's audit log, so an argument about "who changed what" has a factual answer.