Conflicts, warnings and overrides

Every time you assign someone to a shift, Rytmia checks them against that shift before saving. You will see Checking for conflicts… and then one of four answers.

The point of this is not to stop you. It is to make sure that when you do book someone into an awkward slot, you did it knowingly and there is a record of why.

The four answers

No conflicts. Nothing is in the way. Assign and move on.

Warnings. Something is worth knowing but does not stand in the way. The assignment saves, and you are told how many warnings came with it.

Blocking conflicts. The assignment stops unless you give a reason. The button changes to Assign anyway and an override reason is required — you have to write down why this should proceed despite the conflict. There is no way to submit an empty reason.

Cannot be assigned. Some conflicts have no override. Rytmia says so plainly: this cannot be overridden — pick a different resource, or clear the problem on this one first.

What gets checked

The checks cover the ordinary ways a booking goes wrong:

• Availability — the coworker has registered absence covering this time.
• Double-booking — they are already on another shift that overlaps.
• Holidays and non-working dates — the date is one your organization has marked as non-working.
• Access restrictions — something about the site or the client stands in the way.
• Capabilities — the crew does not together cover what the service requires.

Capability gaps read as nobody on this crew has followed by what is missing. That framing is deliberate: the requirement is on the team, not the individual, so adding a different second person can resolve it without removing the first.

Writing an override reason

The reason is free text and it stays on the assignment. Write it for the person who reads it later — the reviewer wondering why someone was booked on a holiday, or you in six weeks.

“Kund godkände lördagspass via telefon 8/9” is useful. “OK” is not.

Overrides on a series

When you assign someone until further notice, the checks run per visit. Visits with blocking conflicts are skipped rather than forced through, and you get a count of both: how many were assigned, and how many were skipped.

Those skipped visits stay in the Needs scheduling rail as incomplete. They have not been silently handled — they are still yours to deal with.

What this does not promise

Rytmia detects and explains conflicts. It does not guarantee that every conflict is caught, and authorized users can override many of them by design.

The system is a check on the plan, not a replacement for knowing your crew. If something looks wrong on the board but Rytmia is quiet about it, trust yourself.

When you cannot get past it

If an assignment cannot be overridden, there are three ways out, in the order worth trying them:

1. Fix the problem on the resource — the absence was entered wrong, or the capability exists but has not been recorded on that coworker.
2. Pick someone else — the rail’s candidate list marks who would work cleanly.
3. Move the shift — if the crew is right and the time is the problem, move the visit rather than forcing the booking. Only that visit moves; the order keeps its schedule.