Kept for Legal & Compliance.
Positions, precedents, and the reasons behind the redlines. Three films on institutional legal memory.
All industriesFor executives
Your precedents are people. Keep the positions anyway.
The most dangerous phrase in a legal team is a confident answer to a question that was settled differently three counsels ago.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The policy is approved. The reasoning behind the exception you granted last year is in an email thread.
When the reasoning behind reviews and exceptions can’t be traced, consistency suffers, and so does your position when asked.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new counsel gets the same redline and asks Kept. They get the threshold and the condition, cited to your review call.
Review reasoning is traceable, so decisions stay consistent. Kept. Keep the knowledge behind the work.
Legal teams accumulate positions: the clause you always strike and why, the regulator conversation that shaped a policy, the risk you accepted deliberately in 2023. That judgment leaves in resignation letters, and successors either re-derive it expensively or contradict it accidentally.
Kept captures institutional positions from the lawyers who hold them and links knowledge to available sources, behind access control your team defines. When the question returns, so does the reasoning. AI can still make mistakes. Inspect available sources and review important answers.
For managers
The matter file has everything except the judgment.
Handing over a matter means handing over documents. The strategy stays in the previous owner's head.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The policy is approved. The reasoning behind the exception you granted last year is in an email thread.
You re-review the same vendor clause because last year’s decision wasn’t recorded with its why.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new counsel gets the same redline and asks Kept. They get the threshold and the condition, cited to your review call.
Last year’s decision is on record with its why. Kept. Keep the knowledge behind the work.
Playbooks say what to do. Your senior people know when not to: which counterparty always trades that clause away, what the business will actually accept, why the standard position bends for this vendor class. Coverage and transitions keep losing exactly that layer.
Kept interviews your team about how the work really goes and keeps the judgment in their words, cited and current. Handoffs carry strategy, not just files. You see what is covered across the team, and no one is measured by it, because Kept does not measure people.
For partners
Every redline has a reason. Keep yours attached.
You have negotiated this clause forty times. The forty-first person to ask should get your answer, not your calendar.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The policy is approved. The reasoning behind the exception you granted last year is in an email thread.
You’re asked whether something was allowed before, and the only way to know is to ask the person who left.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
A new counsel gets the same redline and asks Kept. They get the threshold and the condition, cited to your review call.
You can answer “was this allowed before” without a search party. Kept. Keep the knowledge behind the work.
Kept talks with you about how you work: the fallback positions, the reading of that regulation, the argument that actually wins. It keeps your reasoning in your words, and when a colleague hits the question you have already answered, they get your analysis, cited to you.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in legal & compliance.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a legal & compliance team:
- Knowledge kept per departing partner before their last day, by topic
- Questions the replacement asks in their first 60 days that are answered with a source
- Control and exception questions answered with a source, against honest unknowns
- Decisions in scope with a kept rationale cited to the person who made it
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance