Approval routing fails when the approver opens the contract and asks "why is this in my queue?" The workflow that holds: an agent routes the contract by value, risk score, and clause deviation; the approver sees the rationale inline; a dual-keyed handshake gates the signature; and the routing decision persists for the renewal. The CLM (Ironclad or DocuSign CLM) stays the system of record. The reasoning that justified the routing lives next to it.
The workflow
1. Define routing rules in the CLM, not in someone's head. In Ironclad, set workflow branches on contract value, counterparty tier, and clause flags. DocuSign CLM exposes the same conditional logic for non-standard terms. Encode the thresholds your legal ops team uses: above $250K to the GC, uncapped indemnity to the deputy, data processing to privacy counsel.
2. Let the agent score the contract before it routes. ChatGPT or Claude reads the draft against your playbook and produces three outputs: contract value, a risk score, and a list of clause deviations. The agent attaches that to the workflow record. The approver opens the queue and sees the why.
3. Pull approver context from the systems of record. The agent reads opportunity value from Salesforce, signing authority from Workday, and prior approval history from the CLM. A $400K renewal from a strategic account routes differently from a $400K new logo.
4. Gate the signature with a dual-keyed handshake. The agent prepares the envelope. A named human approver confirms. Only then does the e-signature fire. Signature is irreversible, so it belongs in the dangerous-ops contract tier with explicit consent.
5. Persist the routing decision for the renewal. When this contract comes back in 11 months, the next agent should see who approved, what deviations were accepted, and what the rationale was. Otherwise renewal becomes a re-review.
Worked example: a $180K vendor renewal
The vendor raises the liability cap from 1x fees to 2x and adds a 30-day termination-for-convenience clause. Claude reads the redline against the playbook, scores the liability change as medium risk (precedent exists for this vendor tier) and the termination change as low risk. Ironclad routes to the deputy GC because value is below the $250K threshold and no clause hits the auto-escalate set. The approval card shows: prior contract had 1.5x cap, three peer vendors hold 2x, deputy approved 2x for this vendor in 2024. Deputy approves, the dual-key gate fires, DocuSign sends the envelope, and the rationale gets pinned to the record for next year.
The persistent-state pain
CLM platforms hold the contract, the metadata, and the audit trail. What they do not hold well is the reasoning the agent produced between draft and signature: why the routing landed on the deputy, which peer vendors set the precedent, what the approver's note actually said. That reasoning evaporates between renewals. One way to solve this is a workspace like Dock that holds what the agent interpreted around the contract, with an ironclad_workflow_id or docusign_envelope_id pointer back to the CLM record. The contract artifact stays where it belongs. The rationale travels with the renewal.
Why it matters
World Commerce & Contracting research consistently shows approval bottlenecks among the top sources of contract cycle delay. The fix is not faster approvers. It is approvers who arrive with context already loaded.
Read the full legal-review-with-AI playbook to see how routing fits the rest of the cycle, including redlining inside Ironclad.
FAQ
Q: Should the agent ever auto-approve low-value contracts? A: No. Even a $5K SaaS renewal can carry a perpetual license grant. Route everything; let the agent compress review time instead.
Q: How do I route by risk score when my playbook is fuzzy? A: Start with three tiers and three triggers per tier. Tighten over a quarter. You do not need precision to start.
Q: What if Ironclad and DocuSign CLM disagree on workflow state? A: Pick one as primary. Most teams run Ironclad for routing and DocuSign CLM for signature, with the envelope ID on the Ironclad workflow.
Q: Does the dual-key gate slow approvals down? A: No. The gate fires after approval, in seconds, and only stops an envelope the human did not see.