Key takeaway
An invoice or a stored copy does not establish the grant you need. Match each creator and component to actual signed authority for the proposed use.
Ask what the company may grant
A report can be in the company’s archive for years without anyone checking how it may be reused. Procurement may have paid the author and operations may rely on the file every day. The licensing decision still needs evidence for the specific new use: which agreement lets the company provide this component to this recipient for this activity?
This US copyright review agenda is current to 7 October 2026. Copyright Office Circular 30 describes two work-made-for-hire routes. Independent commissioned work requires a specified statutory category and an express signed agreement; contractor status alone does not establish that route. Employee status involves an agency-law inquiry. Do not classify every historical author from a payroll label.
The statutory text separately addresses initial authorship, material-object ownership and signed copyright transfers. Holding a file does not itself transfer copyright. These principles do not decide whether a particular factual field is protected or whether an actual agreement permits the proposed use.
A hypothetical report with several rights paths
Consider a fictional inspection report assembled for a 2021 installation project. The main narrative came from a consultant; a photographer supplied images; a vendor manual extract is attached; company staff added a factual fault log. The business paid all invoices and retains the report. In this illustration, the only located consultant agreement allows internal use for that project.
The intended new use is an external evaluation followed, potentially, by model training. The completed chain-of-authority record treats each component separately. It does not assume that owning the combined PDF resolves its contents.
| Component/creator | Located authority in the illustration | Decision for proposed external use |
|---|---|---|
| Consultant narrative | Signed project-use license; no located broader grant | Hold; ask counsel whether new use is authorized or new permission is needed |
| Photographs by separate contractor | Invoice found, rights agreement missing | Exclude pending evidence; payment is not a substitute |
| Vendor manual extract | Servicing access terms located | Exclude from training proposal; evaluate exact third-party terms separately |
| Company staff fault log | Creator identified; underlying project restrictions unresolved | Candidate only after contract/privacy/confidentiality review |
| Combined report PDF | Company possesses the file | No package-wide rights conclusion; maintain component exclusions |
Build the document chain instead of a confidence score
For each author, record the commissioning entity, creation date, work description and agreement version. Locate signed amendments and schedules rather than relying on the purchase-order title. A generic supplier record can help find the counterparty, but cannot answer what work a particular grant covers.
Ask counsel to distinguish a work-made-for-hire conclusion, an assignment and a limited license. Under the US statute, a transfer generally needs a signed writing from the owner or authorized agent, subject to the stated operation-of-law exception. A nonexclusive permission can have a different legal analysis; this checklist does not turn every missing signature into the same result.
The usable output is a document reference tied to material and intended use, plus an unresolved issue if necessary. In the hypothetical consultant case, the record remains on hold because the located language is project-specific. It should not be marked cleared because someone remembers asking for full rights.
A historical gap requires a narrower decision
The illustration’s procurement lead searches the 2021 project folder and confirms that the photo invoice has no attached rights terms. The completed decision excludes those images, retains a pointer to the missing document and assigns procurement to seek the historical agreement. The lead does not ask engineering to strip metadata and treat the result as company-owned content.
If the company later seeks new permission, it must describe the actual intended recipient, evaluation or training use, relevant scope and any onward access. That is a separate communication requiring business authorization. This public checklist does not authorize outreach to contractors or claim that new permission will be available.
A narrower export is useful only if it removes dependent material. A company-written caption describing an excluded image may need its own review; a text extract may still reproduce the held narrative. Trace the package’s components rather than assuming a new format removes every rights issue.
Release a reviewed component, not an unresolved archive
Before preparing any sample, the approver should see the component list, located grants, exclusions and remaining confidentiality/privacy issues. The agreed evaluation and a later license are distinct decisions. A limited evaluation permission cannot be expanded by an operator merely because a receiving program prefers a training-ready archive.
Use rights review for the creator-agreement-material-use map and inventory for package components. Continue to keep customer confidentiality, trade secrets and personal information in separate review lanes: a copyright grant does not clear them.
VOID’s initial permissioned introduction can use approved company-level metadata while this work remains unresolved. It does not represent the seller in rights negotiations or certify title. The practical outcome is a smaller supported candidate or a recorded hold, with each proposed component backed by the authority actually found.
Use this review agenda with your legal and privacy advisers. Requirements depend on the records, jurisdictions and intended use.