You are the reason the numbers tie. Say it once.
Every close, someone asks you the same question about the same account. The answer lives in your head and nowhere else.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Month-end close depends on steps that live in one controller’s head. Nobody else can run it.
You post the entry the way you were shown, without knowing why, and hope the auditor doesn’t ask.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in a jar that’s yours.
At the next close, a new analyst asks why the rebate sits in the prior period. Kept answers and cites the words from your call.
You know why the entry is posted that way, and can say so. Kept. Keep the knowledge behind the work.
Kept has a conversation with you about how your part of the work actually runs, and keeps what you share in your words. The next time the question comes, the asker gets your answer, cited to you, instead of your afternoon. Your expertise stops being an interrupt line.
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.
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
Read personal and workspace controls. The overview above is available as text; explore the guided text walkthrough for a step-by-step example.