How we handle GDPR data-subject requests on a deadline
Legal
A new contract in a Drive folder triggers an agent to summarize it, flag non-standard clauses against our playbook, and post the summary to the legal channel, drafting redlines for a lawyer to sign off.
Contracts arrive faster than they can be read closely. A vendor agreement, an NDA, or an order form lands in a shared Drive folder, and someone on the legal team has to open it, read it against what we consider standard, flag the clauses that deviate, and summarize it for whoever's driving the deal. The first pass is mechanical but time-consuming, and it's the step that stands between a contract arriving and a lawyer being able to focus on what actually matters in it.
We handle this by tying the first pass to the event that starts it: a new file in the folder. This writes up how we run that on Kortix — the connections, the steps, and the guardrails — so you can set up the same review.
The common approaches each fall short. A shared inbox where contracts pile up means the first pass waits on whoever has time. A generic AI summarizer produces a readout that doesn't know our positions, so it flags nothing that matters to us. And skipping the first pass entirely puts a lawyer straight into a full read of every contract, including the routine ones.
We wanted each contract summarized and checked against our own playbook the moment it lands, with the summary where the team works and the redlines left for a lawyer to sign off.
On Kortix, a new contract in a Drive folder triggers an agent. Each contract runs in its own isolated session — a cloud sandbox — with scoped access to Drive and Slack. The agent reads the contract, summarizes it, flags clauses that deviate from our playbook, and posts the summary to the legal channel. It drafts redlines on the non-standard clauses, but a lawyer signs off before anything goes back to the counterparty.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the contract playbook skill and the trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a contract review agent in this workspace.
Create the agent agents/contract-review.md. Its job is to give each new contract a first-pass review. It may use the Google Drive, Google Docs and Slack connectors.
Create the skill skills/contract-playbook/SKILL.md with these rules:
Add a cron trigger contract-review-check to kortix.yaml. It runs the contract-review agent every 15 minutes with the prompt "Load the contract-playbook skill and review every new contract in Legal/Contracts."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect the place your contracts live, your document editor and Slack. Credentials are brokered server-side and never enter the agent's machine.

Reads new contracts and adds redlines as suggested edits.

Pulls contracts that arrive through signing envelopes.
Posts each summary with the flagged clauses and links.
Merge the change request, then start a session with the contract-review agent and send this prompt. Check its flags and redlines against your playbook before you let the schedule take over.
Review the oldest unreviewed contract in Legal/Contracts.
The change request added this trigger to kortix.yaml. From now on the agent
checks the folder every 15 minutes, each run in a new session on its own cloud
computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: contract-review-check name: Contract review check on: cron: "0 */15 * * * *" run: agent: contract-review prompt: Load the contract-playbook skill and review every new contract in Legal/Contracts.Redlines land as suggested edits in the contract doc, never as direct edits. The agent never sends a redline and never messages the counterparty. A lawyer reads the flags in #legal and decides what goes back.
Each new contract ends as one message in #legal. This is what a run looks like in the session:
Reviewed 1 new vendor agreement with a 24-month term. Flagged 3 clauses: uncapped liability in §9.2, Net 60 payment terms in §4.1 and auto-renewal with 15 days notice in §12. Drafted 3 redlines as suggested edits, and all of them wait for a lawyer.
Once it works, paste any of these into the same session.
Add a rule to the contract-playbook skill: flag any contract that covers personal data but has no data processing agreement attached.
Every Monday, post to #legal the contracts in Legal/Contracts that renew or end in the next 60 days, with each notice deadline.
When a contract has an earlier version in the same folder, list only the clauses that changed since that version in the summary.
Giving an agent a first pass on contracts is a trust question. The relevant controls on Kortix:
The first pass that used to wait on whoever had time now arrives as a summary and a set of playbook-checked flags the moment a contract lands, with draft redlines attached. The lawyer starts from the flags instead of a cold read, and routine contracts stop consuming the time the tricky ones deserve.