Let Claude review a contract against your playbook — inside the matter, and nowhere else.

Business situation

A London law firm acts for ABC Limited, which has received a supplier’s standard terms. The associate on the matter needs to review them against the firm’s commercial contracts playbook — liability caps, indemnities, termination, data protection — and prepare a mark-up for the supervising partner.

Why existing tools alone are insufficient

Uploading a client’s contract to a general AI chat takes it outside the firm’s document management. Connecting the AI to the whole SharePoint estate is worse: the firm runs information barriers between matters, and an AI with broad access can read across them. The firm needs AI to work within one matter at a time.

Systems involved

• SharePoint — the matter’s document library and the firm’s playbook.
• KroyDB — the matter entity, its team, client and instructions.
• Outlook — correspondence with the other side, which stays with the solicitor.

Kroy architecture

Claude connects to Kroy. Microsoft 365 is connected to Kroy by the firm. The Review Contract Skill may read the current matter’s documents and the playbook, create a review note and save a draft mark-up to the matter’s drafts folder. Kroy decides which matter the associate may reach from the matter team in KroyDB, and applies the firm’s information barriers.

Workflow

1. The associate asks Claude: “Review the supplier terms on the ABC Limited matter against our playbook.”
2. Kroy checks the associate, the agent, the matter team and the Skill, then returns the contract and the playbook via sharepoint.file.read.
3. Claude goes clause by clause: the liability cap is below the playbook’s floor, the indemnity is one-sided, and the data protection clause is missing processor terms.
4. Claude saves a review note to the matter with artifact.create and a draft mark-up with sharepoint.file.create.
5. The associate asks: “How did we handle this clause for XYZ Limited last year?” Kroy refuses: the XYZ Limited matter is behind an information barrier from this team.
6. The associate asks: “Send the mark-up to the supplier’s lawyers.” Kroy refuses: outlook.mail.send is not in the Skill, and mark-ups need partner approval before leaving the firm.
7. The associate requests the partner’s approval. The partner reviews the mark-up and sends it personally.

Agent permissions

Claude acts under the associate’s delegation, within the Skill and within one matter. It can read, note and draft. It cannot send, or read across matters.

Human permissions

The associate works on the matters they are staffed on. The supervising partner approves anything leaving the firm. The risk team manages information barriers.

State changes

• A review note Artifact is added to the matter.
• A draft mark-up is saved to the matter’s drafts folder.
• The matter task Review supplier terms moves to Awaiting partner.

Audit outcome

Kroy records each document read, the note and mark-up created, the refused cross-matter request and the refused send — with the associate, the agent and the policy that decided each.

Security considerations

• Information barriers are applied by Kroy on every request, not by asking the AI to respect them.
• Client documents stay in the firm’s SharePoint; Kroy returns only what the request needs.
• Microsoft 365 credentials stay in Kroy.

Setup requirements

• Matters and matter teams modelled in KroyDB, with information barriers.
• Microsoft 365 connected to Kroy.
• Claude connected to Kroy.
• The Review Contract Skill enabled for the commercial team.