# Product changelog data referral checklist | SourceX

Canonical: https://refer.sourcex.si/guides/product-change-logs-useful-context-without-a-dataset-promise
Last updated: 2026-11-04

A product change log shows that a company has shipped software in versions and explained each change in its own words. It does not show that a licensable dataset exists, who owns every entry, or whether any AI developer wants it. Use it to open a metadata conversation the CEO knows about: who wrote the entries, what each one links to, and which parts came from vendors, open-source projects or contractors. Rights, fit and demand are settled only in SourceX's review.

For a specialist advisor, whether a product consultant, a fractional CTO or an implementation partner, the change log is often the most visible trace of a client's operating history, because it is public or nearly so. That visibility is what makes it misleading. The page you can read is a summary; the records that give it weight sit behind it in ticket systems, code review and incident reports, and you should never open those.

## What a change log records, and what it leaves out

A change log is a release-by-release list of the changes a product team chose to tell users about. The Keep a Changelog convention describes it, in paraphrase, as a curated and chronological list of notable changes for each version, with the newest version first and a release date on each, sorted into six types: Added, Changed, Deprecated, Removed, Fixed and Security. The same convention says a commit log is not a changelog, because it is full of noise such as merge commits.

Curated is the word to hold on to. Every entry is a decision, made after the work, about what users should hear. Behind a line such as "Fixed: duplicate invoices when a sync retries" there usually sit the records that carry real operating history: the customer report, the ticket, the code review discussion, the failing test and the rollout. The change log is an index. The history lives in the systems it points to.

| The change log shows | It does not show |
|---|---|
| That a release happened, and roughly when | Whether the dated entry matches what customers actually received |
| How the team categorized a change | Why the change was made, or who asked for it |
| The product's age and release rhythm | How many tickets, reviews or incidents sit underneath, or in which system |
| The team's public wording | Who wrote that wording, and whether the company owns it |

SourceX's supplier guide on [release note provenance](https://sourcex.si/insights/software-release-note-provenance) covers the technical side: how notes are tested against what shipped, and what has to be removed before a release history leaves a company. This page stays with the advisor's decision: whether a change log justifies a conversation, with whom, and which questions to bring.

## Three kinds of authorship inside one release history

One product's release notes can mix text the company created, text it copied in and text nobody can yet attribute. Each changes what you can honestly say in an introduction.

**Written by the company's own staff.** The U.S. Copyright Office's Circular 30 explains that a work made for hire arises in two situations: an employee creates it as part of regular duties, or a work in one of nine listed categories is specially commissioned under an express written agreement. For an employee-written work, the employer is the author and initial owner unless a signed agreement says otherwise. Notes drafted by the product team as part of their jobs are the cleanest case, and still only a starting point for review.

**Text that came from somewhere else.** Three sources turn up often:

- Generated notes. GitHub documents that its automatically generated release notes list the merged pull requests, the contributors to the release and a link to a full changelog. In a project that accepts outside contributions, that list can credit people who never worked for the company.
- Upstream text pasted in. When a library or platform the product depends on ships a change, teams often copy its wording into their own notes. SourceX's provenance guide reminds suppliers that third-party dependencies keep their own licenses, which do not move with the company's repository.
- Customer-specific lines. The same guide warns that release notes and pull requests can name the customers who requested fixes. Material that belongs to a client is listed on the screening page as usually not a fit.

**Written by an outsider on contract.** Circular 30 sets four conditions for a commissioned work to count as made for hire: it falls in a listed category, a written agreement exists, that agreement expressly calls it a work made for hire, and every party signs. Miss one and it does not qualify. Launch-era notes written by a marketing agency or a contract technical writer therefore sit in an uncertain row until someone reads the contract and any assignment. That reading belongs to the company and SourceX's rights review, not to the advisor.

## The product-history metadata checklist

Fourteen lines, each answerable in conversation with the person the CEO names, usually a product or engineering lead. None needs a file, a sample, a screenshot or a login.

| # | Line | What to ask | Why it matters |
|---|---|---|---|
| 1 | Product and span | Which products, and the first and latest release dates | A two-year log and a twelve-year log are different conversations |
| 2 | Scale | Roughly how many releases and entries, kept in which tool | Gives size without anyone counting records for you |
| 3 | Format | Hand-written file, generated notes, a help-center page or a mix, and since when | Each format drifts from the shipped product in its own way |
| 4 | Linked systems | Whether entries cite tickets, pull requests or incident records, and whether those systems still run | The linked records carry the history; an unlinked entry is only a summary |
| 5 | Staff authorship | Roughly what share employees wrote as part of their work | The cleanest ownership case |
| 6 | Contract authorship | Whether an agency, freelancer or outsourced team wrote any era, and under what contract | Commissioned text belongs to the company only on specific terms |
| 7 | Outside contributors | Whether the repository accepts contributions from outside the company | Generated notes credit those people by name |
| 8 | Pasted upstream text | Whether vendor or open-source release wording is copied in | Third-party licenses stay with the third party |
| 9 | Customer references | Whether entries name customers or describe one client's setup | Client material is usually not a fit |
| 10 | Security lines | Whether notes describe vulnerabilities, and whether any are recent or embargoed | Some security detail has to be held back |
| 11 | Earlier licensing | Whether any of this history has been licensed for AI training before | The company must be able to confirm it has not |
| 12 | Ownership changes | Whether the product or the company was acquired or carved out | After an acquisition, the acquirer's CEO decides |
| 13 | Dated change | Whether the release tool, ticket system or repository host is being replaced or switched off, and when | Genuine timing comes only from a dated event like this |
| 14 | Who answers | The person who answered lines 1 to 13, and confirmation that the CEO knows | Nothing gathered behind the decision-maker's back |

Mark each line known, unknown or flagged, with the date and the name of whoever answered. Unknown is acceptable. Lines 6 to 11 are the ones most likely to be flagged, and a flagged line is something to describe in the introduction, never something for you to resolve.

**Method note.** The checklist draws on the Keep a Changelog convention, GitHub's documentation of generated release notes, Copyright Office Circular 30, SourceX's screening page and its supplier guidance, all checked on 2026-10-27. It records authorship, links and dated events. It does not measure the quality of the underlying records, demand for them or their value; only SourceX's review assesses those.

## One release history, sorted (Illustrative)

Illustrative. A generic company with invented counts; no outcome is implied.

A 140-person field-service software company has shipped its scheduling product since 2016. Its product lead, asked by the CEO to help, answers the checklist in a half-hour call. Nobody opens the repository.

| Era | Staff-written | Third-party or generated | Owner unknown | Entries |
|---|---|---|---|---|
| 2016 to 2018 | 60 | 10 | 60 | 130 |
| 2019 to 2022 | 170 | 50 | 0 | 220 |
| 2023 to 2026 | 200 | 60 | 0 | 260 |
| All eras | 430 | 120 | 60 | 610 |

The 60 owner-unknown entries are launch-era notes a marketing agency wrote; the product lead remembers a statement of work but not whether it assigned rights. The third-party column holds pasted release wording from a mapping library and, from 2023, generated notes whose contributor lists include two outside developers. Every entry since 2019 links to a ticket and a pull request; the early entries link to nothing.

What the advisor writes for the CEO to approve: ten years of release history, about 610 entries, most written by staff; since 2019 each entry links to tickets and code review in systems that still run; launch-era notes came from an agency under a contract nobody has read yet; some notes reproduce a vendor's wording and credit outside contributors. That is a description, not a promise. Whether the linked tickets and reviews are worth licensing, and on what scope, is for SourceX to decide.

## Finding the owner, and where each entry came from

The CEO decides whether the company discusses licensing and signs for it. Product, engineering and support leads can answer the checklist and sponsor the idea internally, but they do not authorize. Origin questions go to whoever actually knows: the product lead for authorship, whoever manages vendor contracts for the agency agreement, the repository administrator for outside contributions. If the product was bought from another company, the acquirer's CEO now decides, and the seller's old contracts may still govern the early entries.

The company itself has to clear the published fit facts before any of this matters. Its full-time headcount must have reached 50 or more at its peak, with contractors left out; it needs a documented operating history, rights to license its records and a decision-maker who knows about the conversation. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. A popular product, a fast release cadence or a well-written changelog appears nowhere in those tests.

If the strongest links in the change log run from customer complaints to product fixes, the [complaint-to-product-change record chain](/guides/complaint-to-product-change-record-linkage) shows what each hop needs, and the [completeness scorecard](/resources/complaint-to-product-change-completeness-checklist) grades it. Where releases were shipped behind flags and rolled back, the [feature flag rollback records map](/guides/feature-flag-incident-rollback-records-across-systems) is the closer guide.

## Bounded questions to bring, and files to leave where they are

Take three questions to the CEO, or to the person the CEO names, in this order:

1. Who wrote your release notes over the years, and did any of them come from an agency, a vendor or outside contributors?
2. Do the entries link to tickets, code review or incident records, and are those systems still running?
3. Would the company want a conversation about licensing parts of that history, knowing that rights and fit are decided in review?

Then route the company by what you heard:

- **Introduce** when the CEO says yes, staff authorship dominates and the linked systems exist.
- **Describe the flags and let review decide** when agency eras, pasted wording or customer names appear but the core is the company's own.
- **Hold** when the CEO has not been asked, or when the only history is a public changelog page with nothing linked behind it.
- **Do not introduce** when the notes are mostly a reseller's copy of a vendor's releases, when the product effectively belongs to a client, or when the history has already been licensed for AI training.

Leave behind exports of the change log, repository access, ticket screenshots and any attempt to count entries yourself from a public page. Saying that a public changelog exists is fine; compiling it is not your job.

Credit follows the program's dated rules, not the effort you put into the checklist. You sign the SourceX Channel Partner Agreement before submitting. The first valid introduction inside the 90-day attribution window is credited once the company files a verified application, and section 3 of the terms is broad about earlier contact: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." If the company has spoken to SourceX before, your introduction is reviewed as a duplicate. The [record chain guide for complaints and fixes](/guides/chain-complaint-to-product-change) and the wider [guides hub](/guides) cover neighboring record types.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the CEO wants the conversation and your checklist shows a staff-written history with linked records behind it, [register for a partner link](/register), test the company once more against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit anything.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://keepachangelog.com/en/2.0.0/
- https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
- https://www.copyright.gov/circs/circ30.pdf
- https://sourcex.si/insights/software-release-note-provenance
- https://sourcex.si/how-it-works
