Reactivity and Escalation
Orgo distinguishes reactivity from a simple final deadline.
A deadline answers:
When should this work be finished?
Reactivity asks an earlier question:
How quickly should this work receive attention?
That distinction matters in organizations where silence itself is a problem.
Reactivity
A Task can carry an expected reactivity window derived from its context and the Organization Profile.
Examples of the idea:
- a critical operational incident may require attention very quickly;
- a routine internal request may tolerate a longer response window;
- a volunteer organization may deliberately use slower defaults than an emergency-oriented operation.
The important point is not one universal number. The Organization defines what “responsive” means for its own context.
Escalation
When work is not receiving the expected attention, Orgo can raise its operational visibility or routing level according to explicit rules.
Conceptually:
Task created
→ expected reactivity window
→ no sufficient response
→ escalation rule applies
→ Task remains governed work with a visible escalation state
Escalation does not create a second Task lifecycle. It is part of the common operational model.
Why this is useful
Organizations often discover problems only after a final due date has been missed. Reactivity gives them a way to notice much earlier that work has stalled.
Combined with Cyclic Overview and Insights, this also makes it possible to distinguish an isolated delay from a recurring organizational pattern.