Who owns business records — the employee or the organization?

As a general rule, records created or received by employees in the course of their work belong to the organization, not to the individual employee. The employee may have created the document, but it documents the organization’s business, so the organization owns and is responsible for it.

Why this matters

The ownership principle has practical consequences:

• Personal accounts/devices don’t escape it. A business record created on personal email, a personal phone, or a messaging app is still the organization’s record — subject to retention, FOIA/public-records, and litigation. This is the core lesson behind off-channel communications enforcement and BYOD recordkeeping.
• Employees can’t take records when they leave. Business records aren’t personal property to be deleted or carried off at departure; offboarding should capture or return them.
• Custody isn’t ownership. An employee may be the custodian holding a record, but the organization owns it.

Government is explicit

In the public sector this is settled law: federal records are U.S. government property under the Federal Records Act, and the Presidential Records Act made even presidential records public property. Officials can’t treat work records as personal.

Some nuance

There are edges — truly personal messages on a work system generally aren’t business records, and intellectual-property ownership can involve contracts. But for the core question — who owns the records documenting the organization’s work? — the answer is the organization.

The practical upshot

Because the organization owns business records wherever they’re created, it must be able to capture and preserve them — including from personal accounts and devices. That’s why clear policy plus capture of approved channels matters: ownership without the ability to capture is a liability. See the fundamentals hub for more.