Procurement teams running agent contract redlining need a record of which clauses an agent touched, which playbook rule it cited, who in procurement reviewed the redline, and which counsel signed off. Ironclad holds the contract. Coupa holds the supplier and PO. Spellbook produced the redline. Dock holds the attributed decision trail that ties those three together and makes the sign-off defensible.
Ironclad, Coupa, and Spellbook stay the system of record for the raw artifacts: the contract version, the supplier master, the redline diff. Dock is the system of record for what the agent interprets from those artifacts. Each Dock row carries a pointer back to the platform record (ironclad_workflow_id, coupa_supplier_id, spellbook_session_id), the agent identity that proposed the redline, the procurement reviewer, the counsel approver, and timestamps for each step. When the agent needs the current clause text or supplier risk tier, it re-fetches from the platform API rather than trusting a cached copy.
The Dock surface
A single redline table keyed by contract workflow.
| ironclad_workflow_id | coupa_supplier_id | clause | playbook_rule | agent_redline | agent | procurement_reviewer | counsel | status |
|---|---|---|---|---|---|---|---|---|
| IC-44021 | SUP-8812 | Limitation of liability | LOL cap >= 2x fees | Raised cap from 1x to 2x annual fees | spellbook-agent | priya.r | sam.k (GC) | counsel_signed |
| IC-44021 | SUP-8812 | Auto-renewal | No evergreen >12mo | Struck evergreen; inserted 60-day opt-out | spellbook-agent | priya.r | sam.k (GC) | counsel_signed |
| IC-44087 | SUP-9104 | Data processing addendum | EU SCCs required | Attached SCC module 2; flagged subprocessor list | spellbook-agent | priya.r | pending | procurement_approved |
Each row is a clause decision, not a contract. A 12-clause redline produces 12 rows, each independently reviewable.
The worked workflow
A new MSA from supplier SUP-8812 lands in Ironclad. The Spellbook agent pulls the draft, runs it against the procurement clause library, and writes one Dock row per deviation. For each row, the agent cites the playbook rule it applied and links the Spellbook session that produced the redline. Priya in procurement opens the queue, reviews each row, and approves or escalates. Approved rows route to counsel; Sam (GC) signs off on the liability cap and renewal terms. Once every row reads counsel_signed, the agent posts the consolidated redline back to Ironclad as a new contract version. The publish step is a consent gate: the agent cannot push to Ironclad until every clause row has both procurement and counsel approval recorded.
Why this matters
World Commerce & Contracting estimates the average business loses about 9% of annual value to poor contract management, with leakage concentrated in unmanaged clauses, missed entitlements, and unauthorized changes (WorldCC, 2023). Agent-led redlining accelerates throughput, but only if every change is traceable to a playbook rule and a named approver. A Dock row per clause makes that traceability the default, not an afterthought.
Counsel time is the bottleneck. The ACC 2024 Chief Legal Officers Survey found that contract review remains one of the largest workload categories for in-house legal teams. Routing only the clauses that genuinely require legal judgment, with the playbook citation already attached, lets counsel approve a redline in minutes instead of re-reading the whole MSA.
The architectural payoff is symmetry with adjacent functions: the same row-per-decision pattern powers Dock for accounting and the broader Dock for legal pattern. One audit shape, many workflows.
Read the full pillar: Dock for procurement.
FAQ
Does Dock replace Ironclad or Spellbook? No. Ironclad remains the contract repository. Spellbook remains the redline engine. Dock holds the attributed decision per clause, with pointers back to both.
What does the agent actually write to Dock? One row per clause it touched. Each row records the playbook rule, the proposed redline text, the Spellbook session ID, and the Ironclad workflow ID. Reviewer and counsel fields are filled by humans.
How does counsel sign off? Counsel reviews the row, not the whole contract. The row links to the Ironclad clause view and the Spellbook diff. Approval writes a timestamped, identity-bound signature to the row.
What happens if the playbook changes mid-negotiation? The agent re-fetches the current playbook before each redline pass and records the playbook version in the row. Prior rows remain immutable against their original rule version.