Resolving Schedule Conflicts

Conflicts occur when a scheduled event violates one or more constraints. This guide walks you through identifying and fixing the most common conflicts.

Finding Conflicts

In the Schedule View

Conflicts are highlighted on events:

• Red badge: Hard conflict (must resolve)
• Yellow badge: Soft conflict (warning)

In the Conflicts Panel

1. Navigate to Constraints in the sidebar
2. View all conflicts grouped by type
3. Filter by team, date, or severity

[!TIP] Start with hard conflicts—they block publishing. Soft conflicts can be addressed later or acknowledged.

Resolving by Conflict Type

Team Double-Book

Problem: A team is scheduled for two events at the same time.

Solutions:

1. Move one event to a different time
2. Delete one of the events
3. Verify the correct team is assigned

Steps:

1. Click the conflict warning
2. See both conflicting events
3. Open the one to move
4. Change date/time
5. Conflict clears automatically

Court Double-Book

Problem: Same court has overlapping events.

Solutions:

1. Move one event to a different court
2. Change one event’s time
3. Move one event to a different venue

Blackout Violation

Problem: Event is during a blackout period.

Solutions:

1. Move the event to a non-blackout time
2. Remove the blackout (if no longer applicable)
3. Change the blackout to SOFT if override is acceptable

Travel Exceeded

Problem: Away team’s travel distance exceeds their limit.

Solutions:

1. Swap home/away teams
2. Find a closer neutral venue
3. Increase team’s travel limit
4. Override with justification

[!WARNING] Before increasing travel limits, confirm with the affected team that additional travel is acceptable.

Max Games Per Day/Week

Problem: Team exceeds maximum games allowed.

Solutions:

1. Move a game to a different day
2. Spread games across more weeks
3. Adjust the max setting in scheduler config

The Resolution Workflow

Step 1: Identify

• Check the conflicts panel for all issues
• Note which are hard vs soft
• Prioritize by severity

Step 2: Analyze

For each conflict, understand:

• What constraint is violated?
• Which teams/locations are affected?
• What are the options for resolution?

Step 3: Fix

Apply the appropriate fix:

• Edit the event directly
• Use swap home/away
• Delete and reschedule
• Adjust constraints (last resort)

Step 4: Verify

After fixing:

• Confirm conflict cleared
• Check you didn’t create new conflicts
• Review related events

Using Override/Exemptions

Some conflicts can be overridden rather than fixed:

When to Override

• ✅ Team confirmed the exception is acceptable
• ✅ One-time situation (not ongoing)
• ✅ No better alternative exists
• ✅ Documented reason provided

When NOT to Override

• ❌ Hard constraints (double-booking)
• ❌ Safety concerns (excessive travel for youth)
• ❌ Unknown if affected parties agree

How to Override

1. Open the conflicting event
2. Click Override Conflict
3. Enter a justification reason
4. Save the override

[!INFO] Overrides are logged with the user and timestamp. Auditors can see who approved each exception.

Preventing Future Conflicts

1. Set up blackouts first: Before scheduling, enter all known unavailability
2. Configure limits early: Set travel and game limits before auto-scheduling
3. Use pre-flight check: Run the scheduler’s readiness check
4. Review as you go: Don’t wait until the end to check conflicts