The workflow continuity test: can a ticket be traced to its final resolution?

Short answer

An operational workflow has a complete evidence trail when every step can be reached from the one before it by a shared identifier, from the first request to a confirmed resolution. An introducer can check this without seeing any record: ask the company to trace a few closed cases hop by hop and report how many links carry an ID, how many rely on dates or memory, and where the chain breaks. That count says more than any promise about dataset value.

Visual briefFull-size diagram
A chain of six records from support ticket to closed ticket, joined by five links; four links carry a shared ID and turn green, one link between the fix and the release relies on dates only and stays orange.
Illustrative trace of one ticket. Four of five hops are linked by ID; one is inferred from dates.

How can an introducer check whether an operational workflow has a complete evidence trail?

Ask for a continuity count, not a sample. The company picks a handful of finished cases, follows each from start to finish in its own systems, and tells you which links held. You learn the shape of the trail without handling data.

Why this matters: buyers in this market describe their target as workflow data, meaning records of how work moved, not isolated documents. Mercor, for example, says it licenses, packages and pays for business workflow data. A pile of tickets with no link to the engineering fix, or invoices with no link to the approval, describes moments of work rather than a workflow. The workflow data explainer covers the general idea; this page gives you a test.

The five-hop trace: a field-level linkage sample

Illustrative. A fictional 350-person B2B software company traces one support case from first contact to confirmed fix. All IDs and dates are invented.

HopFrom recordTo recordLinking keyWhere the key livesLinked by ID?
1Support ticket 48211 openedEscalation to tier 2Same ticket ID; assignee and group changeTicket change historyYes
2Tier 2 escalationEngineering bug ENG-3307Ticket ID stored on the bug; bug key stored on the ticketBoth recordsYes
3Bug ENG-3307Code change mergedBug key in the change descriptionSource controlYes
4Code changeRelease 7.4.2None; release notes describe the fix in wordsRelease notes documentNo: matched by date and wording
5Release 7.4.2Ticket 48211 solvedBug key in the closing note; ticket not reopened in 30 daysTicket change historyYes

Result: four of five hops linked by ID, one inferred. That is a strong but not perfect trail, and the weak hop is a common one: engineering and release management often keep separate records.

The keys in this table are ordinary system features, not special projects. Helpdesks typically keep a change history; Zendesk, for instance, records each ticket update as an audit containing events that show the field changed, its new value and its previous value. Engineering trackers support explicit links between items; Jira's link types include blocks, duplicates and relates to, and admins can add their own. Whether a given company used those features consistently is exactly what the trace reveals.

How to run the count without touching data

Give the company's operations or support lead this script. It takes an hour, and all of it happens inside the company.

  1. Pick twenty cases closed at least three months ago, chosen at random rather than hand-picked.
  2. For each, name the first record (the request) and the last (the confirmed resolution).
  3. Follow each hop and note whether the next record is reached by a stored ID, by date and wording, or not at all.
  4. Report three numbers: cases traced end to end by ID, cases traced with at least one inferred hop, and cases that broke.
  5. Name the hop that breaks most often, and the systems on either side of it.

Ask for the counts and the weak hop, nothing else. Do not ask for ticket numbers, screenshots or exports. SourceX publishes no benchmark for what a "good" count is; the point is to give SourceX an honest starting picture, not to pass a threshold.

What you hearWhat it suggestsNext move
Most cases trace end to end by IDA continuous trail across systemsIntroduce the decision-maker
Most trace with one inferred hopStrong core, one weak seamIntroduce, and mention the weak hop
Most break at the same hopTwo separate archivesIntroduce if each side is deep; scope may narrow
The team cannot find closed cases from three years agoRetention or migration gapAsk what was migrated, and when

Large companies with several overlapping tools need extra care at step 3; the guide on assessing companies with fragmented business systems covers that case. For support specifically, identifying tickets with useful resolution context and the ITSM ticket history page describe what a rich ticket looks like, and the software workflow example pack shows sample chains in other software functions.

Company qualification questions

Beyond the trace, the usual qualification questions apply, all at metadata level.

AskStrong answerWhy it matters
Which systems sit on each side of the weak hop?Named tools with dates in useShows where linking might be reconstructed
Were any systems migrated, and was history carried over?Yes, with full historyMigrations are the most common cause of breaks
How many years does the trail cover?Five or moreDepth
Do customer contracts restrict use of support records?Not known yet, or a short listA rights question SourceX reviews
Who can authorize a licensing discussion?CEO, or the owner in an owner-run companyThe sponsor to introduce

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. 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.

What stays unknown until SourceX reviews it: buyer interest in this workflow, redaction of customer and employee details, the rights review result and any offer.

Limits and unanswered questions

A continuity count measures linkage, not value. A perfectly linked workflow can still be one buyers do not currently want, and a trail with a weak hop can still be useful. This page makes no claim about what any trail is worth, and SourceX has not published continuity benchmarks.

Company compensation and referral rewards are separate. The company is paid under its own agreement with SourceX. The partner's reward is calculated on what SourceX actually pays the company, is funded separately and never reduces that payment. Illustrative only: on a USD 800,000 first qualifying transaction, the reward would be USD 120,000, since 15% of the payout exceeds USD 50,000 plus 5%; there is no cap, and the USD 50,000 floor applies once per company. See how rewards work.

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 a client's trace shows most cases reaching resolution by ID, register as a partner, check the company against who qualifies and read the program terms before introducing its decision-maker. More evidence-trail topics are in the guides hub.

  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 broken hop disqualify a company?

No. Most real workflows have at least one weak link, often between engineering and release. A broken hop lowers confidence and narrows scope; SourceX decides during review whether the trail is complete enough for a buyer's purpose.

Who runs the sample trace?

The company's own staff, on their own systems. The partner only hears the counts, such as how many of twenty sampled tickets traced end to end. Partners never see or receive the records.

Is this test only for support tickets?

No. The same hop-by-hop check works for purchase requests to payment, claims to settlement, or change requests to deployment. Name the first and last record, then count the links between them.

Sources

  1. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  2. support.atlassian.com/jira-software-cloud/docs/link-issues
  3. mercor.com/data
  4. refer.sourcex.si/terms

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