Complaint-to-product-change completeness scorecard: six metadata checks with pass, partial and fail guides

Short answer

A complaint-to-product-change trail breaks when one of five things is missing: a link from the complaint to the product issue, a date on the decision, a version history on the policy page, a version history on the help article, or any record of the outcome. Score each one at metadata level, then run one test that exposes them together: pick a recent policy change and ask for the decision date, the policy page edit date and the help article edit date.

Visual briefFull-size diagram
A six-item scorecard ticks through coverage, conversation links, decision dates, policy versions, outcomes and article versions while a vertical completeness meter rises to four passes and two partials.
Illustrative score for a fictional retailer: four passes, two partials.

This scorecard supports the complaint-to-product-change guide. Use it before telling anyone a company's records are a fit.

How to score

Each check gets one of three marks. Pass means the record exists, is dated and covers most of the period the company would discuss. Partial means it exists for part of the period or only for some records. Fail means it is missing, or nobody can say. Record who gave each answer and how they know. Do not mark a pass because a feature exists in the product; ask whether the company used it, and from when.

A completed scorecard is a page of metadata. It holds systems, dates, counts and owners. It never holds customer names, message text or screenshots.

The six checks

CheckWhat it testsHow to check it at metadata levelPassPartialFail
1. CoverageConversations exist for the periodAsk the support lead which years the Intercom workspace covers and whether older tools were migratedThree or more years in one workspaceGaps, or older years in an unmigrated toolUnder a year, or unknown
2. Conversation-to-issue linksComplaints point to product issuesAsk when the Linear integration was switched on and roughly what share of product-feedback conversations carry a linkLinked since early in the periodLinked only recentlyNo links
3. Decision datesProduct decisions are recorded with datesAsk whether decisions are written as dated issue comments or only in meetingsDecisions dated in the issueOnly completion datesNo record
4. Policy versionsInternal policy pages keep historyAsk which Notion plan holds the policy pages and whether changed pages are exportedEnterprise history, or exported copiesBusiness or Plus history onlyFree plan, no copies
5. OutcomesThe effect of a change is recordedAsk whether anyone tracked complaint volume on the topic after the fixTracked in a report or tagAnecdotal onlyNot tracked
6. Article versionsHelp articles keep dated historyAsk whether the help center is in Intercom and whether articles are edited in placeArticle history keptHistory kept for some collectionsArticles replaced without history

Three of these checks lean on documented product features. Linear's Intercom integration attaches conversations to issues as links, allows several conversations per issue, and posts an internal note to linked conversations when an issue is completed. Intercom keeps public article versions showing which teammate changed what, and the versions do not expire. Notion's page history is the one with a plan-dependent window: 7 days on Free, 30 on Plus, 90 on Business and unlimited on Enterprise. That is why check 4 has an export question.

The stale-article test

The checks score each record. This test scores the joins, and it is the one most likely to separate a strong trail from a weak one.

Ask the support lead for one recent policy change and three dates: when the decision was made, when the internal policy page changed and when the help article changed. Then read the gaps.

ResultWhat it showsMark
All three dates found, article edit within a few days of the policy editProcess is tight and fully recordedPass
All three found, article edit weeks laterProcess lag is recorded; every answer in that window cited a stale sourcePass for completeness, worth noting as a finding
Two of three foundOne step lives in memory, not recordsPartial
One or none foundThe trail cannot be rebuiltFail

The second row is not a failure. A company that can show its own lag across many policy changes holds a useful record of how decisions reach customers. In the Illustrative case on the record chain page, the policy changed on May 2 and the article on May 20, an 18-day window. The missing-context comparison shows what one reply sent inside such a window looks like with and without its context.

A filled scorecard (Illustrative)

A fictional 300-person retailer of home fitness equipment, answered by its CX lead and head of product in one call.

CheckMarkNote
1. CoveragePassIntercom since 2019, single workspace
2. Conversation-to-issue linksPartialLinear integration switched on in 2023
3. Decision datesPassDecisions logged as dated issue comments since 2019
4. Policy versionsPartialNotion Plus plan; no exports before last year
5. OutcomesPassComplaint tags reviewed monthly
6. Article versionsPassIntercom help center, edited in place
Stale-article testPassThree dates found; 18-day lag on the sampled change

Four passes, two partials, and a documented lag. That is enough to describe the trail accurately: complete from 2023, thinner before, with the policy history as the weakest piece.

Before you introduce

Pair the scorecard with the fit check. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact: the CEO, usually the owner in an owner-run company, rather than the CX lead. 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.

Tell the owner that SourceX funds any referral reward separately and never deducts it from the company's payout; the rewards page lists every condition. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Unknown until SourceX reviews it: whether customer terms allow licensing, how conversations would be de-identified, and whether a buyer wants the set. Related reading: former employee complaints and company data, complaint handling records and AI data license change in law.

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.

If the scorecard shows a trail you can describe honestly and an executive will take the call, register as a partner, check who qualifies and read the terms before you introduce the company.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does a fail on one check rule the company out?

No. The scorecard describes the trail; it does not decide eligibility. A company with strong conversations and weak policy history may still be worth introducing, as long as the partner reports the gaps honestly.

Who should answer the checks?

The support or CX lead for conversations and articles, the head of product for issues and decisions, and the operations or policy owner for internal policy pages. Each answers from admin views, not from customer content.

Should I share the scorecard with SourceX?

Yes, as part of the introduction. It tells the review where the trail is complete and where it is not, which saves time on both sides. It holds no customer names or message text.

Sources

  1. linear.app/docs/intercom
  2. intercom.com/help/en/articles/9357931-create-and-manage-p…
  3. notion.com/help/duplicate-delete-and-restore-content
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment