Greetings everyone.

I'm looking for creative ideas (or something I'm missing) 

I have a process with a few approval steps along the way.

The entire process has an SLA we would like to meet. (The whole process should take 2 business days or less.

I can see where timers events on User tasks are great for that specific task - setting a deadline, and handling things when missed.

I can also see where setting a timer catch event at the beginning of the process can be useful - wait 2 days, then do something.

But now I've found a few challenges to make this useful.

• OK, so a timer catch branching off after the initial form submit is great, but what do you do once that occurs?  You could send an email, but what could that person do?  The task has moved on, and as far as I can tell they can't see its status, etc.  It also seems you can't put much helpful information in that email.  "This task exceeded 2 days.  Here is what the initial form looked like."  You can tell them of the problem, but not give them any way to fix it.
• The user due date field seems to have more flexibility than a timer catch.  Any way around this for the timers?  For example, I can make the due date to be 5:00 pm 2 days after the task start date (or the process start date.)  But, if I want to actually do something at that time I don't seem to be able to.

So - bigger picture - are you handling deadlines that track for the entire process instead of just one step of it?  And if so - how?

Thanks in advance!