The feasibility check

Run feasibility check computes through the whole scope you pick — season or production — and returns a verdict with counters: events and people checked, and findings in three severities: breach, warning, and info.

What gets checked

1. Room conflicts — overlap is a breach; a too-short changeover buffer is a warning.
2. Role staffing — per role requirement, available primary-tier candidates are counted: zero available is a breach, fewer than required is a warning. See Staffing and departments.
3. Availability — called people with colliding commitments.
4. Working time — per-person working-time rule violations, including overtime.
5. Lead times — rehearsal weeks before press night, call-notice windows, production overlap with shared crew, changeover days between productions in the same room, and department prep/breakdown buffers.

The verdict is cached. If a relevant event changes afterwards, it’s marked stale — re-run the check for fresh numbers. A stale report can’t be used to make changes.

The report and the suggestions

The Report tab groups findings by severity, and every finding gets one suggestion:

• Trivial suggestions — typically “shift the event a little later to clear the clash” — have an Apply button and can be written directly, or Request approval when the approval matrix demands sign-off. The card shows up front who has to approve.
• Advisory suggestions — change the room, reassign the person, qualify another — are resolved in the scenario’s diff, not with one click.

Apply all greens

When the report has several trivial fixes, Apply all greens takes them in one batch and summarises: how many were applied, and how many turned into approval requests.