Schedule
Detect and resolve conflicts
SceneItAll checks your schedule for conflicts — places where it breaks a production rule such as a turnaround minimum, a daily-hours cap, or an element’s availability — and for missing data such as a day without a date. This article covers running detection, reading and clearing conflicts, and configuring the rules.
Before you start
- You have the Admin or Owner role. Running detection, resolving, ignoring conflicts, and changing the rules all require Admin or Owner.
- A scenario is active and not locked. Detect conflicts is disabled on a locked scenario.
Run conflict detection
To check the scenario currently selected in the scenario bar:
- On the Strip Board tab, choose Detect conflicts in the toolbar.
- SceneItAll scans the scenario and shows a result message: “{n} conflict(s) found, {m} auto-resolved.”
Detection also runs automatically after a relevant schedule or source-data save, including changes to strips, days, scenes, tagged elements, Cast/Character links, availability, Locations, and scheduling rules. The save and its recalculated Conflict rows are committed together. Conflicts that no longer apply are auto-resolved. Each scenario keeps its own findings: switching scenarios never shows or resolves another scenario’s conflicts.
[SCREENSHOT: The strip board toolbar with the Detect conflicts button and a day banner showing a red conflict count pill]
See where conflicts are
- On a day banner — a red pill shows the day’s conflict count (“{n} conflict(s)”). Findings are attached to the exact schedule day, so renumbering days does not move a warning to the wrong banner. Select it to open the conflict.
- On a strip — a strip in a conflict shows a red conflict badge. Select it to open the conflict, or, when a strip has several, to open a Scene {n} warnings list you can pick from.
Read and clear a conflict
Selecting a conflict opens the conflict detail dialog. When a day has several active conflicts, page through them with the chevrons. The counter and pager include only unresolved findings from the selected scenario and current day or strip; resolved history does not inflate the total. The board loads every active conflict page, including projects with more than 100 active findings.
The dialog shows:
- The conflict type as its title and a severity badge — ERROR, WARNING, or INFO.
- The conflict description.
- Metadata: the date, the source (auto or manual), and the detection time.
- The affected elements, when any.
For most conflict types, select the severity badge to expand a What this means and How to resolve explanation.
To act on a conflict, use the dialog’s buttons:
- Mark Resolved — marks it resolved. Add a note in Resolution Notes first if you want to record how.
- Ignore — opens an Ignore Conflict prompt for a Reason for ignoring…, then hides the conflict.
- Go to scene breakdown — jumps to the scene a conflict points at (shown when one applies).
- Close — closes the dialog without changes.
Resolving or ignoring the current conflict advances to the next one; the dialog closes when none remain.
Your decision is remembered for that exact conflict scope. Running detection again does not recreate an ignored or manually resolved finding when the same condition still affects the same scenario, day, strip, location, or element. A matching condition on a different day, scene, person, or other scoped item is a new finding and still appears. Findings that SceneItAll auto-resolved because the condition disappeared can return if the condition later comes back.
Conflict severity
Every active conflict is shown in red on the Schedule page, including its strip chip, overflow icon, list entry, and detail badge. Red therefore has one simple meaning: something needs attention. The severity word still tells you how strict the finding is:
| Severity | Meaning |
|---|---|
| Error | A hard rule violation to resolve. |
| Warning | A soft limit to review. |
| Info | An informational note. |
Conflict types
SceneItAll detects these conflict types. The first group are rule violations; the second are schedule-completeness checks.
| Type | What it flags |
|---|---|
| Turnaround below minimum | Consecutive dated shooting days in one unit have less rest than the configured minimum. |
| Meal break window | A day exceeds the configured time from call without an earlier meal point. A short day does not require a meal. |
| EXT DAY after sunset | A managed exterior DAY scene’s calculated interval runs past sunset. |
| DAWN/DUSK light window | A managed exterior DAWN or DUSK scene’s calculated interval misses the corresponding sunrise or sunset. |
| Location unavailable | A managed Location is marked Unavailable or Travel during use; Hold is a warning. |
| Location double-booked | The same managed Location has genuinely overlapping calculated intervals on different day/unit rows for one date. |
| Element unavailable | An active non-character Element is explicitly Unavailable during its calculated use. |
| Actor unavailable | A linked actor is Unavailable or Traveling during the day’s continuous work span; Hold and Fittings are warnings. |
| Actor double-booked | The same linked actor has overlapping calculated work on different day/unit rows for one date. |
| Scheduled Character has no actor | A scheduled active Character has no linked Cast member. |
| Mini move missing | Consecutive scenes at one managed Location but different Sets lack a mini move or company move banner. |
| Company move missing | Consecutive scenes at different managed Locations lack a company move or travel banner. |
| Move time too short | Movement-banner time between a required transition is below the configured travel buffer. |
| Permit expired | A permit-required Location is used after its permit expiry date. The expiry date itself remains valid. |
| Day length over maximum | The continuous day from call to confirmed or calculated wrap exceeds the daily maximum. |
| Sixth/seventh production workday | Shooting, prep, or travel occurs on a sixth or seventh consecutive calendar date. Multiple units on one date count once. |
| Daily page target exceeded | Operational scene pages exceed the day override or project target. This is always a Warning. |
| Element hours exceeded | An Element with an explicit daily or weekly override exceeds that custom value. No project-wide value is guessed. |
| Missing wrap time | A non-empty shooting day has neither a confirmed wrap nor a shared calculated wrap. |
| Missing call time | A non-empty shooting day has neither crew call nor a usable operational-scene call. |
| Missing date | A shooting, prep, or travel day has no calendar date. |
| Empty shooting day | A shooting day has no operational scene strips; banners and inactive weather cover do not count. |
| Scene has no elements | An operational scheduled scene has no tagged elements and its blank state has not been acknowledged. |
For the aligned rulebook checks, warnings use these message templates:
- Turnaround: “Turnaround below minimum – [X]h [Y]m between Day [N] wrap ([time]) and Day [N+1] call ([time]), minimum is [Z]h.”
- Exterior daylight: “EXT DAY after sunset – Scene [number] at [location] scheduled [time], sunset is [time] on [date].”
- Missing wrap: “Wrap time missing – Day [N] has no wrap time set.”
Configure conflict rules
The rules live on the Scheduling rules page in Global Settings → Schedule. Open Global Settings from the settings cog, select Schedule, then Scheduling rules. The active controls are grouped under these headings:
- Timing Thresholds — Min turnaround (hours) (default 10), Max daily hours (default 12), Meal break after (hours) (default 6), and Travel buffer (minutes) (default 30).
- Day Warnings — 6th day warning and 7th day warning (both on by default).
- Checks — Check element availability and Check permit expiry (both on by default).
Override rules for one element
Some Elements need deliberately different rules. Under Element Overrides, choose Add Element Override, pick the Element, and configure any of all seven supported values: daily maximum, early-warning threshold, weekly maximum, turnaround minimum, meal-break threshold, sixth-day warning, and seventh-day warning.
The daily, early-warning, and weekly values are custom Element-hours checks; leaving one blank disables that custom check. Meal and consecutive-day values inherit the project setting until you change them. Turnaround also inherits the project setting, and an Element can only require the same or more rest—not less—than the project minimum. Reset to Defaults removes every override.
The Element meal threshold uses that Element’s calculated work hours on the day and is satisfied by the day’s meal marker. Sixth- and seventh-day Element warnings count consecutive calendar dates on which the Element appears; multiple units on one date count once.
How conflicts fit the data flow
Detection reads the selected scenario and the structured schedule, availability, Character/Cast, Element, Location, permit, and rule data it depends on; it never guesses from free text. Handled decisions are scoped to the exact scenario and affected days, strips, people, Elements, or Locations.