Deadlines and reminders

Model time limits as timer boundary events on the task they affect, not as gateways after it.

Remind, then escalateCopy Anchor Link

A non-interrupting timer (on~) sends a reminder while the review goes on. An interrupting timer (on:) stops the review when the deadline passes, and the escalation rejoins the main flow.

process Contract review
lanes Legal | Legal lead

lane Legal
start Contract received
user Review contract
  on~timer(P2D) Reminder due -> Send reminder
  on:timer(P5D) Review overdue -> Escalate review
xor #reviewed
send Return contract to sales
end Contract reviewed

send Send reminder
end Reminder sent

lane Legal lead
user Escalate review
  -> #reviewed

A deadline over several stepsCopy Anchor Link

When a reminder or deadline covers several steps, such as "remind the handler on day 25 and escalate at day 30", group the steps in a call activity or sub-process and put the timers on it. The timers then stop with the work.

process Claim settlement
lanes Claims handler | Claims manager

lane Claims handler
start Claim approved
call Settle claim
  on~timer(P25D) Settlement due soon -> Remind claims handler
  on:timer(P30D) Settlement overdue -> Escalate settlement
xor #settled
send Notify policyholder
end Claim settled

service Remind claims handler
end Reminder sent

lane Claims manager
user Escalate settlement
  -> #settled

Don't model the deadline as a parallel branch that waits on a timer. That branch never joins the work, keeps the case open, and still fires after the work is done. The checks warn when the branches of a parallel split never meet again.

Wait a fixed timeCopy Anchor Link

A timer catch event on the path waits, then the flow carries on:

process Trial follow-up

start Trial started
catch:timer(P14D) Trial ended
send Send offer
end Offer sent

What to noticeCopy Anchor Link

• Name timers after the condition, such as "Review overdue", not the mechanism.
• The reminder path ends in its own end event, Reminder sent. The review is still running.
• Timer values are ISO 8601: P2D is two days, PT4H four hours. See Events.
• To show an SLA on the diagram without modeling it, add a note such as note: SLA 2 days. A note doesn't replace a timer the process acts on.

To wait for either a reply or a deadline, whichever comes first, see Waiting for a reply.