This page is available in Swedish and English for easy sharing with your entire coaching staff.

Last updated: 2026-05-01

Guide: Base Rules

This guide explains what you can control in Base Rules and when each setting is appropriate.

When to use Base Rules

Use Base Rules when the default solver result is good but you want to fine-tune behavior around substitutions, role balancing, or how strictly rules are enforced.

Typical scenarios:

• You want smoother, more consistent substitution patterns.
• You need stronger control over role stability across periods.
• You want to adjust penalties without rebuilding the plan manually.

What you can control

1. Soft penalties

Soft penalties influence solver preferences without making a rule absolutely required. Use these when you want to guide behavior rather than enforce it rigidly.

Examples:

• Within-period swap tolerance
• Boundary swap tolerance

Higher penalty values make the solver avoid that deviation more strongly.

2. Relaxed penalties

Relaxed penalties are useful when strict behavior makes the problem hard to solve. Use them to keep the solver flexible while still preferring good structure.

3. Hard rules

Hard rules are mandatory requirements. If a hard rule cannot be satisfied alongside your other settings, the solver may fail or require adjustments. Use hard rules only for genuinely non-negotiable constraints.

Practical tuning workflow

1. Start with the default values.
2. Change one setting at a time.
3. Generate and review the result.
4. Check substitution flow and fairness in Review and Match Day.
5. Save only when the behavior is consistently better.

Rule of thumb

• Start with soft penalties.
• Use relaxed penalties when feasibility is fragile.
• Keep hard rules minimal and intentional.

Related pages

• User Guide
• Tutorials