Are business records protected by copyright?

What does copyright protect in a company's records?#

Copyright in business records covers original expression fixed in some lasting form: the wording of an email, the structure of an SOP, the code in a repository, the lines of a drawing. It does not cover the facts, ideas, methods or systems that the expression describes, and it generally requires a human author.

Ownership follows authorship, adjusted by employment and contract. Text an employee writes as part of the job is a work made for hire: the company counts as its author and holds the copyright, and only a signed written agreement can change that. Material written by independent contractors usually stays with the contractor unless a written agreement assigns it, and messages written by customers belong to the customers even though the company holds copies.

So a single support ticket can hold three positions at once: the agent's reply is company expression, the customer's message is the customer's expression, and the timestamps, product codes and resolution status are facts that nobody owns.

Facts, compilations and thin protection#

Facts are not copyrightable, however much effort it took to collect them. US courts have long rejected the idea that hard work alone earns copyright, so a carefully maintained parts catalog or dispatch log does not become protected just because it was expensive to build.

A compilation of facts can be protected, but only for the original way the facts were selected, coordinated or arranged. That protection is described as thin: it stops someone copying the creative arrangement, not someone extracting the facts and arranging them differently.

Short text can still clear the originality bar. In February 2025 a federal court held that 2,243 Westlaw headnotes, the short summaries of legal points attached to court opinions, were original enough for copyright protection, and in September 2026 the Third Circuit affirmed. Carefully written resolution summaries or playbook entries may therefore carry more protection than their length suggests, while terse status notes usually carry little.

Databases follow the same rule. The European Union gives database makers a separate right that protects substantial investment, but the United States has no equivalent, so a US company's database is protected mainly through contracts, confidentiality and access controls rather than copyright.

Record types: protected, thin or unprotected#

Sorting records by copyright position helps counsel see where the company has strong rights, where it relies on contract, and where someone else's rights must be cleared. The table gives the usual position; the actual answer depends on who wrote each record and under what agreement.

Why unprotected records can still be licensed#

Unprotected records can still be licensed because a data license is a contract, not only a copyright permission. The contract defines what the buyer receives, what it may do, how long it may keep the records and what happens at the end, and those promises bind the buyer whether or not copyright applies.

Trade secret law can add protection where records derive independent economic value from not being generally known and the owner takes reasonable measures to keep them secret. Access control does the rest: a buyer that cannot obtain your dispatch history or quality logs anywhere else has a reason to license them from you.

Buyers also pay for things copyright never covered: documented provenance, cleared rights, removal of personal and confidential details, consistent structure and a counterparty that stands behind the package. Those are the reasons licensed business records stay valuable even where training on public material is argued to be fair use.

Where copyright limits what you can license#

Copyright works against the licensor where records contain expression the company does not own. These items are easy to miss in an archive and are usually removed or cleared during the rights review.

A practical test for each record family is to ask who typed the words, under what agreement, and whether anything was pasted in from outside. Ticket systems, shared drives and project folders collect outside material over the years, so the answer is often mixed, and the outside material is easier to remove before preparation than to explain after delivery.

• 1Attachments written by others: manufacturer manuals, vendor PDFs, published standards and articles saved into tickets or project folders.
• 2Client deliverables and drawings where the client owns copyright or holds an assignment.
• 3Code or documents written by contractors without a written assignment to the company.
• 4Open-source code carrying license terms that travel with it.
• 5Licensed content libraries, stock images and templates whose terms bar redistribution.
• 6Customer-authored messages, which need a basis in terms, notices or contracts rather than ownership.

Illustrative: a mechanical contractor sorts its records#

Illustrative: a fictional mechanical contractor runs on ServiceTitan, with years of job histories, technician notes, estimates and invoices, plus a shared drive of in-house training SOPs and saved manufacturer installation manuals. Its general counsel wants to know what the company actually owns before any licensing conversation.

Counsel sorts the archive into three groups. Technician notes and SOPs are company-authored and move forward. Job times, equipment models and invoice lines are facts, so they move forward on the strength of the license contract and confidentiality terms. Manufacturer manuals are excluded entirely, and customer-written messages in the booking portal are reviewed against the company's terms of service before any decision.

The result is a package where every record family has a stated basis: owned expression, contract and confidentiality, or excluded. That map later becomes the core of the rights documentation the buyer asks for.

How SourceX approaches copyright in a rights review#

Authorship is one of the first questions SourceX asks once a supplier has described its systems. In the SourceX five-step transaction it is settled during Rights, after Supply identifies the record families and before Preparation touches any file. Third-party attachments, client-owned material and contractor work without an assignment are flagged for the supplier and its counsel to clear or exclude.

The SourceX Evidence Packet then states, record family by record family, whether the basis is owned expression, contract and confidentiality, or a cleared outside permission. The records are licensed, not sold, and the supplier keeps ownership of everything it owned before the deal.