Find and resolve conflicts

Outcome

You will create a deliberate scheduling overlap, see it surface in all three places conflicts appear, resolve it on the board, and confirm the list returns to “No conflicts detected. All scheduled requests meet their requirements.”

Before you begin

• A workspace with at least one space and two schedulable requests (Create your first schedule gets you there).
• The Editor or Admin role.
• Background reading: Understanding conflicts.

Step 1 — Manufacture a collision

1. On Utilization → Spaces, schedule request A onto a space for tomorrow.
2. Schedule request B onto the same space at the same time.

Orkyo warns during placement — overbooking is one of the validations — but proceed: real schedules acquire conflicts through later edits all the time, and that is exactly what detection exists for.

Step 2 — See where it surfaces

The same conflict now shows in three places:

• On the board — a conflict indicator marks the affected placements.
• On the request — opening A or B shows a banner counting the conflicts on it, with each conflict’s message.
• In Insights → Conflicts — a card labeled Scheduling Overlap, showing the schedule and a “View other request” link to the counterpart. The summary line now reads “1 conflict found in scheduled requests.”

Step 3 — Resolve it

On Utilization → Spaces, drag request B to a free slot — a different time or a different suitable space. The conflict indicator disappears as detection re-evaluates.

Alternatives, depending on what the conflict actually tells you:

• The other request should move — use the card’s “View other request” link to decide which placement is wrong.
• The capacity is wrong — if the space genuinely hosts both, raise its Capacity (Spaces and floorplans) instead of moving work; the conflict kind would then be Capacity Exceeded, and the fix is data, not schedule.

Step 4 — Confirm zero

Back on Insights → Conflicts, the list is empty: “No conflicts detected. All scheduled requests meet their requirements.”

Step 5 — Make it a habit

• Scan Insights → Conflicts at a fixed rhythm — start of shift, start of week. The filters on Insights also chart the Conflict trend, which tells you whether the schedule is getting healthier.
• Treat recurring conflict kinds as model feedback: chronic Capacity Exceeded is a capacity problem; chronic Capability Mismatch after edits means capabilities are being changed without checking dependent schedules.
• Conflicts can be exported (CSV) from the Conflicts page for review meetings — see Import and export.