Understanding Conflicts

Conflicts occur when a scheduled event violates one or more constraints. MatchGrid detects conflicts automatically and helps you resolve them before publishing your schedule.

Conflict Severity

Hard Conflicts (Blocking)

These must be resolved before publishing:

• Court Double-Book: Same court scheduled for overlapping events
• Team Double-Book: Team scheduled for multiple events at the same time
• Hard Blackout Violation: Event during an unavailable period
• Venue Unavailable: Location marked as closed

[!WARNING] Hard conflicts are shown with a red indicator. You cannot publish a schedule with unresolved hard conflicts.

Soft Conflicts (Warnings)

These are flagged but don’t block publishing:

• Soft Blackout: Preference to avoid but not required
• Travel Exceeded: Trip distance over the team’s limit
• Late Slot: Event starts after the late threshold
• Max Games Exceeded: Team has too many games in a period

Conflict Types Explained

Double-Booking Conflicts

Court Double-Book Two events scheduled on the same court at overlapping times. Resolution: Move one event to a different court or time.

Team Double-Book A team is scheduled for two events at the same time. Resolution: Reschedule one of the events.

Constraint Violations

Max Per Day Team exceeds the maximum games allowed in a single day. Resolution: Move games to different days.

Max Per Week Team exceeds the weekly game limit. Resolution: Spread games across additional weeks.

Rest Window Insufficient recovery time between games. Resolution: Add more time between the team’s events.

Blackout Violations

Hard Blackout Event scheduled during a mandatory blackout (holiday, facility closure). Resolution: Move the event to an available date.

Soft Blackout Event scheduled during a “prefer to avoid” window. Resolution: Consider moving, but can proceed if necessary.

Travel Conflicts

Travel Exceeded The away team’s travel distance exceeds their configured limit. Resolution: Swap home/away, find a closer venue, or override with justification.

[!TIP] Travel conflicts consider both weekday and weekend limits separately. Teams often have higher tolerance for weekend travel.

Viewing Conflicts

In the Schedule View

• Red event badges indicate hard conflicts
• Yellow badges indicate soft conflicts
• Click an event to see conflict details

In the Conflicts Panel

• Navigate to Constraints in the sidebar
• View all conflicts grouped by type
• Filter by team, location, or severity

Resolving Conflicts

Method 1: Edit the Event

1. Click the conflicting event
2. Change time, date, or location
3. Conflicts update automatically

Method 2: Swap Teams

For home/away conflicts:

1. Open the event
2. Click Swap Home/Away
3. Verify the swap resolves the issue

Method 3: Override (with justification)

For soft conflicts you’ve decided to accept:

1. Click the conflict warning
2. Enter a justification reason
3. The conflict is marked as “acknowledged”

Method 4: Delete and Reschedule

For complex conflicts:

1. Delete the problematic event
2. Create a new event at a better time
3. Use the auto-scheduler for suggestions

Preventing Conflicts

Set up your data to minimize conflicts:

• Configure accurate blackouts before scheduling
• Set realistic travel limits per team
• Ensure venues have correct court counts
• Use the pre-flight check before auto-scheduling