Who owns documents employees create? Work made for hire explained

Under the work made for hire rule in the Copyright Act, an employer generally owns documents an employee prepares within the scope of employment. That is why a company can usually license most internal documents itself. Founders, side projects, contractors and client material are the edge cases a rights review checks.

Who owns documents employees create?

In general, the employer owns copyright in documents an employee prepares within the scope of employment, because the law treats them as works made for hire and names the employer as author. That is why most internal documents, such as reports, memos, procedures and code written by staff on the job, can be licensed by the company itself. The edges are founders, side projects and anything created outside the job.

The Copyright Office's Circular 30 on works made for hire explains that for a work made for hire the employer, not the individual creator, is the author and owner. Section 201 of the Copyright Act says the employer owns all rights in such a work unless the parties agree otherwise in a signed writing.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

How does the scope-of-employment test work?

Courts look at facts, not job titles. The questions below are a practical way to sort documents, not a legal test.

FactorPoints to company ownershipPoints the other way
Kind of workThe task is the kind the person was hired to doThe task is unrelated to the role
Time and placeCreated during working hours, at work or on company systemsCreated on personal time with personal tools
PurposeDone to serve the employerDone for the employee's own purposes
DirectionAssigned or approved by the companySelf-initiated side project

A sales operations manager who writes a pricing playbook for the team almost certainly creates it within the scope of employment. The same person's novel, written at home, almost certainly is not. The hard cases sit between those poles, and counsel resolves them.

What does the statute say?

The definition of a work made for hire is in section 101 of the Copyright Act. It has two prongs. The first covers a work prepared by an employee within the scope of employment. The second covers certain commissioned works created by independent parties, which is the contractor path discussed in does a company own work created by independent contractors. This page is about the first prong.

Ownership of copyright is also not the whole picture. Copyright protects expression, not facts. A company may own a document yet face limits on licensing it because of privacy law, confidentiality duties to clients or privilege. Rights review looks at all of these.

Edge cases to check

  • Founders and early staff: work created before the company existed or before an employment relationship began may not be covered without an assignment.
  • Side projects: a developer's personal repository is not company property just because the developer works for the company.
  • Remote and personal devices: location does not decide ownership; the relationship and scope do.
  • Former employees: documents they created during employment generally remain company works, but check that agreements do not say otherwise.
  • Acquired businesses: ownership depends on the purchase agreement and on how the seller's staff were engaged.
  • Employee-written documents containing client material: the company may own the writing but not the client's confidential facts inside it. See the confidentiality clause guide.

What does a rights review check?

SourceX qualification asks whether the company has rights to license the data. For employee-created documents that review typically looks at:

  1. Whether the author was an employee, and whether the document was within the scope of the job.
  2. Whether any employment, consulting or IP agreement changes the default result.
  3. Whether the document embeds third-party content, such as licensed templates, client data or stock material.
  4. Whether privilege applies. See does sharing privileged documents waive attorney-client privilege.
  5. Whether privacy or employee-notice issues limit use, covered in do you need employee consent to license workplace data.

Red flags for a partner

Flag, do not diagnose, when you hear any of these:

  • The valuable records were mostly written by outside contractors rather than staff.
  • The company is a small founder-led business whose key materials were produced before incorporation.
  • The sponsor says employees "own what they write".
  • The documents mainly belong to clients, as at an agency or outsourcer.

Companies introduced through SourceX still need 50+ full-time employees at peak (contractors excluded). Ask who actually wrote the valuable records, because staff-authored material is the easiest to clear. The company fit checker is a preliminary, non-binding screen.

What to say

Next step

If you know an operator with years of internal documents written by its own staff, register as a partner and make the introduction. The how it works page covers the later stages. No reward is guaranteed; it is paid only after the buyer pays and SourceX receives its fee.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Does an employer automatically own everything an employee writes?

No. The employer owns works prepared within the scope of employment, not everything an employee creates. A personal project made on the employee's own time and unrelated to the job may belong to the employee. Agreements can also change the default, so the facts and the paperwork both matter.

Does ownership of a document mean the company can license it?

Ownership is the starting point, not the end. The company may still face limits from privacy law, client confidentiality duties, privilege or embedded third-party material. A rights review checks these alongside copyright, and the company's counsel makes the final determination.

Do founders own what they created before incorporating?

Not necessarily. Work created before the company existed or outside an employment relationship may need a written assignment to belong to the company. Early-stage records are a common place for gaps, so a rights review asks how and when the founding team documented transfers.

What if an employee leaves the company?

Documents created within the scope of employment generally stay with the company after the employee leaves. Check whether any agreement or separation terms say otherwise. Departure does not usually change ownership of work made for hire, though personal information in the documents is a separate matter.

Is employee-created code treated the same as documents?

The same work-made-for-hire rules generally apply to software written by employees within the scope of employment. Open-source components, contractor-written modules and third-party libraries are different, so engineering records need their own rights check before they are included in a scope.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment