Skip to content
Astera Technology

Give overlapping rules an explicit priority

Record an ordered decision table for overlapping conditions.

Compare the rule with concrete cases

Fictional routing has two rules: restricted records go to hold; urgent records go to fast review. Both can be true. The owner explicitly makes restricted take priority. Without this precedence, different readers could route a restricted urgent record differently.

Filled synthetic modelling cases
RecordRestricted / urgentFirst matching ruleRoute
P1Yes / yesRestrictedHold
P2No / yesUrgentFast review
P3No / noDefaultNormal review
Download editable CSV ↓

Work through the distinction

Priority must be part of the rule, not inferred from the order someone happened to type the sentences. The default covers the remaining combination.

P1 remains urgent but its restriction is removed. Where does it go?

Show the worked answer

Fast review. It no longer matches the higher-priority restricted rule and now matches urgent.

Acceptance wording to adapt

Evaluate restricted first: if true, return hold. Otherwise evaluate urgent: if true, return fast-review. Otherwise return normal-review. Return exactly one route for each record.

Related resources