Memory for Legal

Legal's guidance, with an owner, a deadline and a source.

Templates, clauses, policies and opinions become a reviewed knowledge base. The company asks and gets the current guidance with its source document, and Legal decides what AI may publish.

Product screen, with sample data

The problem

Legal answers the same question every week.

And still runs the risk of someone using the wrong version.

Scattered versions

The current contract template sits next to three old versions in different folders, and nobody knows which one applies.

A queue of simple questions

Questions that already have a written answer arrive by email and message, and take the time that should go to what is new.

AI that does not know the house guidance

Anyone using a generic AI gets a generic answer, without the company's policy and without saying where it came from.

Before and after

What changes in Legal.

From a manager's question to reviewed guidance.

Without the company's memoryEach department keeps its own copy of the templateWith KlucoThe current template is in the knowledge base, with an owner and the date of its last verification
Without the company's memoryOld guidance keeps circulatingWith KlucoWhen the review deadline passes, the article is flagged as overdue
Without the company's memoryAI writes and nobody reviewsWith KlucoWhat AI writes or updates can wait for Legal's approval
Without the company's memoryThe same question arrives by email every weekWith KlucoThe company asks the knowledge base and gets the guidance with its source document
Without the company's memoryAny agent reads any documentWith KlucoEach agent queries only the documents Legal chooses

What goes into memory

What Legal has already written, in one place.

Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and every article keeps its version history.

  • Contract templates and approved clauses
  • Internal policies and codes of conduct
  • Recurring opinions and guidance
  • Powers of attorney and signing authority
  • Privacy and personal data policies
  • Litigation procedures
  • Due diligence checklists
  • Internal purchasing and contracting rules

Use cases

Where Legal starts.

The most common use cases in Legal, with the part of the platform that does each one.

  • Approved templates and guidance

    Templates, clauses and guidance sit in the knowledge base with an owner and a review deadline. AI uses the current version and shows where it came from.

    Brain
  • AI proposes, a person approves

    When AI writes or updates an article, the change can wait for the approval of whoever owns the topic.

    Brain
  • One agent per area, with only its documents

    Each agent queries only the documents you choose, and the access profile sets who can use each agent.

    Agents
  • A policy assistant in the team's channel

    People ask in Slack, Teams or Google Chat and get the answer with the source article.

    Agents
  • Personal data masked

    When the company turns it on, the agent masks personal data in its logs and answers.

    Agents
  • The same memory for any AI

    ChatGPT, Claude, Gemini and other MCP-compatible tools query the same knowledge base, each person with their own access.

    Brain

Brain · the memory

Every piece of guidance with an owner, a deadline and a source.

The Brain turns Legal's documents into articles with an owner, a review deadline and a version history. Every answer shows the passage and its verification date.

  • Human approval before publishing what AI writes
  • Audience per article: all agents or internal assistants only
  • Contradictions between documents become review suggestions
See the Brain
Product screen, with sample data

Agents · AI agents

Agents that only read what you choose.

Create one agent for contract questions and another for internal policies, each limited to the documents Legal selects.

  • Agent knowledge limited to chosen documents
  • Human approval for sensitive actions
  • Personal data masking, when turned on
See the Agents
Product screen, with sample data

LLM Management and Chat

AI for Legal, with defined access.

The team uses the models the company allows, in the Chat, which draws on the memory, with an audit log of the configuration and the conversations.

  • Access profiles by model, agent, skill and memory
  • A limit per person and a budget per team
  • Audit log for configuration and chat
See LLM Management
Product screen, with sample data

Control

What Legal controls.

The company sets up each control below in the console.

See security and LGPD
  • An owner and a review deadline on every article, with a record of who verified it and when
  • A person's approval before publishing what AI writes
  • The audience of each article: all agents or internal assistants only
  • The documents each agent may query
  • Personal data masking in logs and answers, when turned on

FAQ

What Legal teams ask.

Can AI publish guidance without going through Legal?

Only if the company wants it to. Human approval is an option: when it is on, everything AI writes or updates waits for a person's approval before it enters the knowledge base.

How do I stop people using an old version of a template?

The current template sits in the knowledge base with an owner and a review deadline. When the deadline passes, the article is flagged as overdue, and every answer shows the passage used and its verification date.

Can I limit what each agent queries?

Yes. Each agent can query only the documents you choose, and the access profile sets who can use each agent.

Does Kluco replace a lawyer's review?

No. It organises what Legal has already decided and delivers that guidance to whoever asks. New matters, non-standard contracts and decisions stay with Legal.

Next step

See Legal's guidance reaching whoever asks.

In the demo, we show the knowledge base, approval of what AI writes and an agent limited to chosen documents.