Weekly Checklist

Use this page as the weekly front door.

The point of this page is not to explain every system in full. The point is to keep you moving in the right order.

That order matters because the plugin is heavily dependent on connected systems.

For example:

• contracts affect assignments and finances
• assignments affect sponsorship behavior
• sponsorships affect post-race income
• results affect financial close

If you start in the wrong place, the rest of the week becomes harder to read.

The Right Weekly Mindset

Do not treat the dashboard like a list of unrelated pages.

Treat the weekly workflow like an operating sequence:

1. make sure required actions are cleared
2. make sure the right driver is attached to the right car
3. make sure sponsor coverage is in place
4. run the race weekend
5. review the financial outcome after the event closes

That sequence keeps the rest of the system understandable.

Before the Race

This is the normal pre-race order for most organizations.

1. Clear any pending actions first

Start by checking whether the week is blocked by a pending action.

In practice, that usually means:

• a contract offer that still needs approval
• a counter offer that still needs review
• another workflow item that has not been accepted or rejected yet

If a required action is still waiting, clear that first before trying to read the rest of the weekly state.

If you skip this, you can end up troubleshooting downstream pages when the real issue is simply that a required approval never happened.

2. Confirm contracts are in the state you expect

Open Contracts and confirm:

• the driver is actually signed
• the contract is active or scheduled the way you expect
• the correct series is attached to the deal
• there are no obvious term issues that would affect the week

This matters because race assignments and salary expectations both depend on the contract being correct.

3. Confirm race assignments

Open Race Assignments and verify:

• the correct driver is attached to the correct car
• the correct contract is selected for the car
• the intended races are selected
• there are no locked, unavailable, or conflict states you overlooked

This is one of the most important weekly checks in the entire plugin.

A signed contract does not automatically mean the car is ready.

4. Review sponsorship coverage

Open Sponsorships and review each car that is racing.

Look for:

• open sponsor slots
• active offers waiting for review
• race rows still showing sponsor alerts
• any emergency sponsor situation that needs attention late in the week

If a race still needs sponsor work, resolve that before assuming the car is fully ready.

5. Check finance context if needed

You usually do not need a full finance review before every race, but it is useful to confirm the account context makes sense when something feels off.

Open Finances if you need to verify:

• the car still has operating cash
• the organization needs to transfer money to a car
• prior-week expenses or sponsor income posted the way you expected

If the car looks financially unstable, address that before race weekend instead of discovering it afterwards.

During the Race Week

During the active week, your goal is to avoid creating confusion for yourself later.

That usually means keeping a clean record of:

• who is in each car
• which sponsor slots are locked
• which contract is active on that entry
• whether anything changed late in the week

If a late change happens, update the system immediately. Do not rely on memory.

After the Event

Once results are in and the event has been processed, the weekly workflow changes from planning to verification.

1. Confirm the race outcome looks broadly correct

You do not need a dedicated results guide to do the first sanity check.

Just confirm the obvious things:

• the right driver appears with the right car
• the finish position looks believable
• there is no obvious mismatch in event context

If the base event outcome looks wrong, stop there and correct that first before reading anything downstream.

2. Review finances after event close

Open Finances and review the correct account scope.

For most race-week review, that means the car account.

Check whether the expected categories posted, such as:

• purse
• sponsor income
• sponsor bonus income if earned
• damage cost
• tire cost
• travel
• team travel and lodging
• staff cost
• salary and winnings share when applicable

If you are checking manufacturer support or overhead, move to the organization account instead.

3. Review sponsor follow-through

Return to Sponsorships and confirm the sponsorship outcome makes sense.

That usually means checking:

• whether the accepted sponsor package settled correctly
• whether any sponsor bonus should have been earned
• whether the relationship history now reflects the completed race

This is especially important if you are tracking sponsor development over time.

4. Review anything that changed because of the event

After an event closes, several systems may have changed at once.

Use a short review pass to confirm:

• the contract still reflects the state you expect
• the next race assignment still makes sense
• the next sponsor openings are visible
• the car account balance still looks healthy

This keeps you from rolling one bad week into the next one.

Recommended Weekly Order

For most organizations, the cleanest recurring sequence is:

1. clear pending actions
2. confirm contracts
3. confirm race assignments
4. confirm sponsorship coverage
5. run the event
6. review car finances
7. review sponsor outcome and next-week readiness

That is the correct operating order more often than not.

Common Weekly Mistakes

Starting with finances before checking setup

If the car setup is wrong, the finance review will only show symptoms.

Setup always comes first.

Assuming a signed contract means the car is ready

It does not.

You still need race assignments.

Assuming one accepted sponsor means the race is fully covered

It does not.

A race can still have open secondary or tertiary slots.

Looking at the wrong account after the event

A large amount of confusion comes from checking the organization account when the race-week activity posted to the car account.

Final Reminder

The weekly workflow is mainly about order.

If you handle the systems in the right sequence, the plugin is much easier to read.

If you handle them out of order, the same plugin can feel far more confusing than it actually is.

Use this page to keep the week structured, then move into the deeper guides only when you need detail.