Reading Your Schedule Builder Results

Modified on Sun, 21 Jun at 1:18 AM

After Schedule Builder finishes, review the result before you share the schedule. The result page is meant to help you spot anything that deserves a second look.

Where to find results

Right after you click Create schedule plan, Bravara shows the latest result on the Schedule Builder page.

To review an older result:

  1. Open Schedule in the left navigation.
  2. Click Schedule Builder.
  3. Click View History near the top of the page.
  4. Find the schedule result you want and click View.

Start with warnings

If the result shows warnings, read those first. Warnings do not always mean the schedule is unusable. They mean Bravara had to make a choice you may want to review, such as using a backup field or putting some games closer together than preferred.

Check field and court use

Look for spaces that are used too much, not used at all, or used at unexpected times. If a field or court is missing, go back to Venues & Spaces and confirm it is available for the right divisions.

Check team experience

Review whether teams are getting a fair mix of start times, opponents, and home or away labels. A small league may need repeat opponents, but the pattern should still make sense.

Check backup choices

If the result used any choices from the Overflow step, review those games closely. Make sure your league is comfortable with the backup field, weekday, or later start time that was used.

What to do next

If the schedule looks good, continue with your normal publishing or communication process. If it does not, click Back to builder, adjust the setup, and create another schedule plan. You can compare the new result with prior results from View History.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article