escalation-flagger

Contract approval routing matches your issue against an escalation matrix to identify the correct approver based on thresholds, deviations, or automatic triggers, then drafts a decision-ready request without sending it.

Contract escalation for GC sign-off is needed when an issue hits a dollar threshold, deviates from standard terms, triggers an automatic flag, or requires a business decision beyond standard authority limits.

Drafting an approval request involves summarizing the issue, quoting relevant contract sections, applying playbook rationale, listing options, and setting a decision-by date to give the approver everything needed to act.

No, the workflow only drafts the escalation message for review. It characterizes the issue and selects the approver, but does not automatically send the request to the general counsel or any other approver.

Yes, contract escalation routing requires loading a practice-level escalation section from a configured CLAUDE profile to map issues to the correct approver using the defined escalation matrix and playbook rules.

Contract review gets delayed without escalation routing because issues are misrouted to the wrong approver or lack a structured approval request, preventing the decision-maker from acting quickly on the out-of-bounds term.