Multi-Stream Conflict Resolution on the Living Roster

Multi-Stream Conflict Resolution

If you assign someone who's also rostered on another Stream you don't manage at the same time, the Conflict Resolution Modal opens automatically.

What the modal shows

• The other shift (Stream, shift pattern, date, time)
• Who manages that other Stream (the other Roster Builder)
• The impact (overlap window, total hours that day, knock-on rest implications)

Your options

Action	Use when
Cancel this assignment	The other Stream's shift takes priority
Pick someone else	Better to find a different person here than negotiate cross-Stream
Request release	You want this person here — ping the other Roster Builder to release them
Keep both (with override note)	Edge case — split shift, partial overlap, agreed split-coverage

Requesting release

• Sends an in-app notification + email to the other Stream's Roster Builder
• They see the same context you see and can Approve (release the staff to you) or Reject
• If approved, their cell clears and yours fills — both rosters update together
• You'll see a status badge until they decide; you can pick someone else in the meantime if you don't want to wait

Tips & common mistakes

• Don't Keep both casually. A real overlap is almost always a fatigue problem and an audit risk.
• Cross-Stream releases are negotiation, not commands. A polite note in the request helps ("Need RN Smith for ED Trauma cover Tue — happy to swap back next week").
• If you frequently fight over the same staff, raise it with your Org Admin — they can re-balance Editable Streams across Roster Builders.