Branch precedence and conflict handling

Conflicting sequence rules need a declared winner. A reply, status, or signal can make several paths eligible, but eligibility alone does not choose the next action. The safest precedence rule is one others can inspect: expose the overlap, name the competing outputs, rank the collision, then apply an explicit winner or send the decision to someone with authority.

Run the precedence pass

Start with the collision and ask the same questions each time. Otherwise, the sequence can inherit priority from whichever branch happened to run first.

Stage	What you are trying to learn	Example question
Detect overlap	which paths can affect the same contact window	Do these paths overlap in timeline, audience, or channel?
Define the collision	which outputs cannot all happen together	What outputs are competing?
Set authority	who can change the order or remove a condition	Who can decide what should change?
Rank the collision	which path has the greater impact, time pressure, or ownership constraint	How should these options be ranked?
Choose precedence	which path controls the next action	Which path gets control?
Set a limit	how much communication the profile can receive	How often can this profile be contacted?

Detect the collision

Treat a collision as a decision point before adding another branch. Identify every path that can act on the same person, timing window, or channel.

Check whether the paths overlap in timeline, audience, or channel before comparing their priorities.¹ A reply branch and a signal branch may point to different actions while sharing the same send window. A status branch may call for a pause while another condition still qualifies the person for an outbound touch. Put those conditions side by side and write the action each one would produce.

Continue until you can describe the collision in operational terms: one path wants to continue, another wants to stop, or several paths want to send different messages. If you only have project names or general goals, keep working on the outputs.

Define the outputs and authority

Priority decisions get easier when the competing actions are visible. Write what the sequence would do under each condition, then identify who can change the decision when the rules point in different directions.

Name the two requested outputs.² Use the actual actions, such as continue, pause, exit, re-enter, or send a particular message. This gives the decision maker something concrete to accept, remove, or reorder.

Make the conflict specific enough for the person with authority to decide what should change.³ Show the conditions that fired, the outputs they request, and the consequence of choosing each path. Ask for a decision on the order or the rule itself. Do not leave the sequence owner to infer the tradeoff from a crowded automation map.

The person making the call should be able to answer which output takes control and what happens to the other output. If nobody can make that call, the sequence has an authority problem alongside its precedence problem.

Rank the collision

Rank competing paths by impact, time pressure, and ownership constraints. These tests keep the decision tied to the work and its consequences.

Ask, "How important is this? Does this have significant implications for customers or financial performance? How much is at stake?".⁴ That answer tells you whether a path deserves priority because its outcome carries greater consequences.

Then ask, "How urgent is it?".⁵ A task can require immediate completion when it is time-sensitive or will become irrelevant. Give that condition weight even when the underlying outcome has lower overall importance.

Ask, "How unique is it? Is this something that only you can do, or could someone else do it while you work on a priority that needs your unique expertise?".⁶ Keep the path that depends on scarce ownership visible in the decision. Reassign or defer work that another person can complete when doing so resolves the collision cleanly.

Use the answers to produce a clear order. If importance, urgency, and ownership point in different directions, send the tradeoff to the person with authority instead of hiding it inside branch logic.

Choose the precedence rule

A sequence needs an explicit conflict behavior when several conditions remain true. Decide the behavior before judging whether the branches worked correctly.

Test whether conflict resolution applies the intended latest-wins or other precedence behavior.⁷ A latest-wins rule can be appropriate for a changing status, while a fixed precedence order can be safer for a stop or exit condition. Choose the behavior that matches the consequence of being wrong, then make it visible in the rule definition.

Decide which message wins when a profile qualifies for several messages.⁸ Treat this as a separate choice from whether the profile qualifies at all. Qualification answers whether a path is eligible. Precedence answers which eligible path controls the next action.

Use conflict detection, priority scores, and rule sets to avoid overlaps and balance frequency across channels.⁹ Keep the score or rule set tied to the ranking tests, so a high score has a reason that another rep can inspect.

Set limits on how often or how many messages a profile receives.¹⁰ A winning branch still has to pass the communication limit before it sends. When a limit blocks the winner, define the fallback explicitly: hold, suppress, or move to the next permitted action.

Apply the decision and recheck the map

Precedence changes can reach beyond the rule you edited. Recheck the surrounding paths after every priority change instead of assuming the rest of the sequence stayed intact.

Changing an existing rule's priority can alter the priorities of other rules.¹¹ After changing an order, rerun the collision pass for every path that shares its audience, timing, or channel. Check the winner, the blocked paths, the exit behavior, and the contact limit.

Test a case where several conditions qualify at once. Confirm that the intended path controls the action, that a stop condition does not leave another send active, and that a blocked message has a defined next state. Record the decision in the rule description so the next edit starts from the same precedence logic.

Move on when the sequence produces one clear next action for each collision and the fallback is known when that action cannot run.

What not to do

• Do not let the most recent email in the inbox dictate the order while earlier emails are ignored.¹²
• Do not prioritize a path because its requester is more demanding or intimidating.¹³
• Do not choose the easiest work or the work for people you personally prefer.¹⁴
• Do not accept competing paths silently, because that leaves the tradeoff unresolved.¹⁵
• Do not wait for perfect clarity before prioritizing important work.¹⁶