A procurement team running Ironclad CLM and Coupa already has a workflow engine and a spend system. What they lack is a structured record of why an agent proposed a particular redline, which clause it fell back to, and which counsel approved the deviation. Dock holds that interpretive layer.
Where the data lives
Ironclad and Coupa stay the system of record for the raw data: workflow states, executed PDFs, requisitions, POs, supplier records. Dock is the system of record for what the agent interprets from that data. Each Dock row carries a pointer back to the platform record (ironclad_workflow_id, coupa_requisition_id), the agent identity that drafted the redline, the counsel reviewer who signed off, the decision, and the timestamp. The agent re-fetches Ironclad and Coupa data via fresh API reads when it needs current state.
One Dock table: Redline Decisions
| ironclad_workflow_id | clause | proposed_redline | playbook_fallback | agent | counsel_reviewer | decision | coupa_requisition_id |
|---|---|---|---|---|---|---|---|
| WF-44218 | Limitation of Liability | Cap at 2x fees, 12-month lookback | 1x fees, 12-month | clm-agent-3 | jane.okafor@ | approved | REQ-9981 |
| WF-44231 | Data Processing Addendum | Add EU SCCs module 2 | reject if no SCCs | clm-agent-3 | rahul.menon@ | approved | REQ-9994 |
| WF-44247 | Auto-renewal | Strike auto-renew, 60-day notice | strike auto-renew | clm-agent-3 | jane.okafor@ | escalated-to-CFO | REQ-10012 |
Each row is a durable artifact. At renewal in 24 months, a different agent can read this table, fetch the current Ironclad workflow, and know exactly which terms were negotiated, which were waived, and who owned the call.
A worked workflow
A supplier MSA lands in Ironclad. The redline agent reads the document, compares it to the procurement playbook in Dock, and proposes seven redlines. For each, it writes a row to the Redline Decisions table with the rationale, the fallback, and a pointer to the Ironclad workflow. Counsel opens Dock, approves five, rewords one, and escalates the liability cap to the CFO. The agent pushes approved redlines back into Ironclad as comments. Ironclad routes the draft to the supplier. When the contract executes, Dock writes the final clause language back to the row and emits a consent gate before the agent triggers PO creation in Coupa. No PO moves without the executed-contract pointer and the counsel approval ID both present. See /blog/dock-for-legal for the counsel-side workflow.
Why it matters
Ironclad describes its Redlining Agent as identifying "missing clauses, risky terms, or compliance gaps within a document based on playbooks" (Ironclad). That is the right job for a CLM. Dock sits one layer up: capturing the decision the human made when the agent flagged the gap.
World Commerce & Contracting research finds that finance-connected contracts boost margins by 5.4 percent (WorldCC). The connection driving that lift is the structured link between contract terms, the spend system, and human approvals. Dock is where that link lives.
Treat redlines as ephemeral CLM comments and you lose the institutional memory the moment counsel changes roles. Dock keeps that memory addressable and tied to both the Ironclad workflow and the Coupa requisition.
Get started
Read the procurement pillar for the full architecture, then see /blog/dock-for-accounting for how the same pattern handles the resulting invoices.
FAQ
Does Dock replace Ironclad? No. Ironclad runs the workflow, stores the executed PDF, and handles signature. Dock holds the interpretive layer the CLM does not store: redline rationale, counsel approvals, and the pointer back to each Ironclad workflow ID.
How does the agent avoid acting on stale contract data? The agent re-fetches the Ironclad workflow and Coupa requisition on every read. Dock stores decisions and pointers, not platform state. See /blog/agent-audit-and-compliance.
Who approves a redline that deviates from the playbook? The counsel reviewer named on the Dock row. Escalations to the CFO are captured as a separate decision with its own timestamp. The full pattern is documented in /blog/dock-for-legal.
What stops the agent from creating a PO before counsel signs? A consent gate on the Dock row. The Coupa PO call cannot fire until both the executed-contract pointer and the counsel approval ID are present. The audit trail is described in /blog/agent-audit-and-compliance.
