What does a real escalation look like when the trigger sits in a related record?

At Aster Financial, a credit officer opens APP-2187, a working-capital loan request from a small manufacturer. The requested amount is within the officer's delegated limit on its own. But the applicant already holds facility LIM-0931, and the authority matrix applies the limit to combined exposure. Together the two exceed what the officer can approve.

An agent supporting the officer reads the application, the existing facility, the matrix row for the officer's grade and the product policy. It concludes that a senior credit manager must decide. Instead of proposing approval, it drafts an escalation note covering the combined exposure, the debt service calculation, one open policy exception on inventory valuation, and two questions the senior reviewer is likely to ask.

**State change:** APP-2187 moves from `IN_REVIEW` to `ESCALATED`. The assignee changes from the officer's queue to the senior manager's queue. A new record, ESC-0319, links the case, the reason code `AGGREGATE_EXPOSURE` and the attached documents.

**Consequence:** the senior manager can approve with a condition in one sitting, because nothing has to be requested again. Had the agent approved at the officer's level, the approval would have breached delegated authority and needed to be reversed.

**What it teaches:** the trigger lived in a related record, not in the application. Evaluation should check that the agent looked past the single case, escalated rather than decided, and left a handover the next reviewer could act on.