Seller intent

How to license internal documents for AI

Last updated October 31, 2026/Seller intent

How to license internal documents for AI is a question about authorship and use, not about how many files sit in a shared drive. The documents that can matter are the ones the company actually wrote to run the work: a standard operating procedure that people follow, a playbook for a recurring job, a knowledge-base article that captures a local exception, a postmortem that says what broke and what changed. A drive that also holds vendor manuals, stock templates, and three years of untitled drafts is mostly storage. Storage is not a dataset.

Even a procedure the company wrote is not automatically available for a training use. It may quote a customer's confidential exhibit. It may include employee performance notes. It may be a joint work with a partner who did not agree to this. It may simply be wrong, abandoned, and dangerous to present as how the company operates. Commercial fit asks whether the writing shows real practice. The right to permit a use asks whether this company can offer that writing. This page answers neither question for you, and it is not legal advice.

The wider map of shelves is the kinds of operating records AI teams ask about. Why practice beats a public description is why operating history can matter to a training team. The logs of people actually doing the steps, as opposed to the document that tells them to, are how workflow and process records can be licensed. A license remains permission for a defined use, as what AI data licensing means for a company explains. Your company's data could be worth up to $5M+. A page count is not the way that ceiling is reached.

Why a lived procedure is different from a published one

Public documentation tells a reader the official path. Internal writing, when it is honest, tells the reader where the official path fails: the step everyone skips, the check a senior person adds, the workaround for a supplier who is always late. How business data trains AI agents to do real work is about that kind of judgment. A document helps an agent only when it is tied to a practice someone still recognizes. A handbook that no one has opened since onboarding is a pamphlet with a version number.

Knowledge-base articles written for customers are a mixed case. They are already public, or they are one approval away from being public. A license discussion is more serious for the internal article that was never meant for the outside, and that article is also the one more likely to contain material the company cannot offer. We do not treat internal as a synonym for valuable, or public as a synonym for free to repackage.

Which documents are even worth describing

• Procedures the company authored and still uses. The test is whether a new hire could do the job from the page and a veteran would agree the page is roughly true.
• Playbooks for a repeated motion: onboarding an account, closing a field job, reviewing a design, handling a known failure.
• Exception notes attached to the procedure. The bend in the rule is often the part a generic manual does not have.
• Postmortems and decision logs that record what was tried and what was kept. A slide with no aftermath is weaker.
• A maintainer. Someone who can say which folders are current and which are archaeology.

Documents that look internal and still fail the shelf

• Manuals the company downloaded from a vendor and stored for convenience.
• Templates bought from a third party, or copied from a blog, and never adapted.
• Customer deliverables, contracts, and exhibits filed next to the procedure that produced them.
• Drafts with no owner and no sign that anyone worked from them.

What makes a large knowledge base a bad candidate

Size is the easiest boast and a poor guide. A company can hold tens of thousands of pages and still have little it both uses and may offer. Neighboring shelves are not this one: how support tickets and chat logs can be licensed, how sales call transcripts can be licensed, and how CRM and pipeline records can be licensed.

• The writing describes a process the company abandoned. Presenting it as current practice would mislead a later reader, which is a reason to leave it out even before rights are discussed.
• Authorship is shared or unclear. A contractor, a franchisor, or a joint venture may own or restrict the text.
• The pages are full of customer names, employee reviews, or credentials pasted into a how-to for speed.
• The only copies live in a tool whose terms limit export. Being able to download a page is not a license from the tool provider, and it is not a license you can pass on.
• No one will narrow the folder. A request to take the whole drive is a request to skip the review.

How written know-how is profiled

Unlockt, LLC operates Big Data/Little Guy, including the free check and the profile review. We do not take ownership of your procedures. The check asks whether you keep written practices and how long they have been maintained. It does not ask for a zip file of the drive.

A Data Partnership Profile can name the kinds of documents, the rough age, and the limits you already see. It should not claim that every page in a folder is current or permitted. Buyers read that description. They do not receive the playbook at that stage. If you later approve a slice, preparation removes personal details and drops pages that do not belong. If counsel says a folder must stay inside the company, the folder stays.

There is no price per SOP and no promise that a knowledge base will interest anyone. The marketplace is aimed at established companies, often about 50 or more employees, where written practice has had time to accumulate. A thinner library can still be described honestly, and an honest thin description is allowed to end the conversation. You keep the documents either way.