The decision trail is the dataset: approvals, reversals and final outcomes across company systems

Short answer

A business decision is explained by a chain of records, not one document: the request that started it, the analysis and its revisions, the approval with the approver's authority at the time, any reversal and its reason, the revised decision, and the review that measured what happened. Those records usually sit in four or five systems. A trail is complete when one identifier or reliable cross-reference links all of them, and when version and approval history were kept rather than overwritten.

Visual briefFull-size diagram
A swimlane timeline of one illustrative decision across a ticket system, document versions, an approval tool and email: request, memo versions, approval, reversal, revised approval and outcome review, all linked by one decision ID.
Illustrative decision DEC-117. One shared ID ties seven records in four systems into a single trail.

Which records explain a business decision, its approval, its reversal and its final outcome?

Six record types, linked (seven records in the example below, because the analysis has two versions): request, analysis versions, approval, reversal, revised approval and outcome review. Each answers a different question, and losing any one breaks the story.

RecordQuestion it answersTypical systemWhat makes it usable
RequestWho asked for what, and why then?Ticketing or project toolCreation date, requester, problem statement
Analysis versionsWhat options were weighed, and how did the case change?Document libraryVersion history kept, not overwritten
ApprovalWho said yes, under what authority?Approval workflow or emailApprover, timestamp, authority limit in force
ReversalWhat changed, and who withdrew the approval?Ticket, email, meeting minutesReason recorded, link to the original approval
Revised approvalWhat was approved the second time?Approval workflowNew version referenced, same decision ID
Outcome reviewDid it work, measured against the forecast?Review document, ERP or BI reportPlanned versus actual figures, review date

Public text rarely shows the middle of this chain. Company announcements report a final decision; they almost never show the rejected option, the approval that was withdrawn or the review that found the forecast was wrong. That middle is what makes a trail useful for training and evaluating AI systems that must recommend, approve or check business decisions. See what AI training data is for the broader picture, and the decision records data type for the categories of records involved.

One illustrative decision, fully linked

Illustrative. A fictional 240-person regional distributor decides to close one of its two warehouses. Every record below carries the identifier DEC-117 or links to a record that does.

StepDateRecordSystemAuthority shown
1. Request2023-02-06Ticket: consolidate Site B into Site AJiraOperations director as requester
2. Analysis v12023-02-20Memo with three options and a savings forecastSharePoint libraryFinance analyst as author
3. Analysis v22023-03-03Revised memo after freight quotes changed the forecastSharePoint librarySame author, version 2.0
4. Approval2023-03-10Approval of option B, citing memo v2Approvals appCFO, within the authority limit in the policy version then in force
5. Reversal2023-05-22Approval withdrawn after a lease exit clause was found; memo v3Email thread and ticket commentCEO, as the only person able to override the CFO
6. Revised approval2023-06-14Partial consolidation approved, citing memo v4Approvals appCEO and CFO jointly
7. Outcome review2024-03-18Review comparing forecast and actual carrying costSharePoint library, citing ERP figuresOperations director, presented to the leadership team

Three details make this trail strong. The memo kept every version, so the change between v1 and v2 is visible. The approval cites the memo version it approved, so a reader can tell what the CFO actually saw. And the reversal names its reason and links back to step 4, so the withdrawal is not mistaken for a new decision.

What each system keeps, and what it quietly drops

The same trail can be complete in one company and broken in another depending on settings nobody remembers choosing.

  • Document versions. Microsoft's documentation says SharePoint can store, track and restore files whenever they change, with versioning on by default in libraries but off by default in lists. A decision register kept as a list with versioning off holds only the latest state.
  • Approval history. Microsoft also notes that the approval columns on a SharePoint list item show only the latest approval activity; the full history is in the Approvals app. A trail that relies on the column alone will show "approved" and hide the withdrawal.
  • Ticket history. Atlassian documents that Jira records who changed a field and when, visible in the issue's History tab. Status changes such as "approved" to "on hold" survive there even when the ticket's current status says nothing about them.
  • Email. Reversals often happen in a thread, not a system. If former executives' mailboxes were deleted, step 5 may be gone even when every other record survives.

For engineering choices, architecture decision records provide a similar chain inside a code repository, and capex requests with post-implementation reviews are a common finance-side example. The guide on assessing operational decision logs covers high-volume, rule-driven decisions rather than one-off ones like DEC-117.

A partner's completeness check, at metadata level

Ask the owner or a senior manager these questions. None requires opening a record.

  • ☐
    Do major decisions get an ID, project code or ticket number that appears in the related documents?
  • ☐
    Is version history switched on where analyses and registers are kept?
  • ☐
    Do approvals happen in a tool that keeps history, or only in email?
  • ☐
    Is the authority policy (who can approve what, up to which limit) itself versioned?
  • ☐
    Are reversals recorded with a reason, or does the old approval simply disappear?
  • ☐
    Do outcome reviews exist for a meaningful share of decisions, and do they cite the original forecast?
  • ☐
    Roughly how many such decisions a year, over how many years?

Partners never ask for the records, samples or screenshots. Discovery stays at the level of what exists, how much, over how long, in which system and who owns it. When an owner is weighing whether to raise a licensing idea internally, who to tell first about a new initiative helps with sequencing.

Does the company qualify, and who can authorize a discussion?

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

Decision trails raise two ownership questions early. Board and investor materials may be subject to confidentiality duties, and records involving customers or suppliers may be limited by contract. The person who can authorize a licensing discussion is the CEO (in an owner-run company, usually the owner), not the operations manager who kept the tickets. What stays unknown until SourceX reviews the opportunity: whether the trails fit current dataset needs, which records the rights review clears, what de-identification is required and whether any offer follows.

What public demand signals show, and what they do not

Demand signals are public but should be read carefully. On 2026-10-09, micro1 announced a commitment to spend $1 billion over 12 months acquiring and licensing enterprise operational data. That is a company announcement of intent; it is not evidence that the money has been spent or that any particular company's decision records will be bought. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout.

Company compensation and the referral reward

If a company licenses its records, SourceX pays the company under its agreement. A referral reward, if one becomes payable, is calculated on what SourceX actually pays that company and is funded separately, so it never reduces the company's payout. Nothing is owed for an introduction or a signed agreement alone.

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 an owner can answer yes to most of the checklist, register as a partner, confirm the company against who qualifies, and read the program terms before you make the introduction.

  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

Is a decision log spreadsheet enough on its own?

Usually not. A log records the final state of each decision. The value sits in the linked records around it: the versions that changed, the approval history, the reversal and the review that measured the outcome.

What if the company never used a shared decision ID?

Trails can often be rebuilt from dates, project codes and ticket numbers, but that is work for the company and SourceX, not the partner. Say in the introduction that no shared ID exists.

Who owns a decision trail that involves a customer or supplier?

The company owns its internal records, but contracts with customers or suppliers may limit reuse of what they sent. That question goes to the company's counsel during SourceX's rights review.

Sources

  1. support.microsoft.com/en-us/sharepoint/data-and-lists/view-the-ver…
  2. support.microsoft.com/en-us/office/approvals-in-lists-document-lib…
  3. support.atlassian.com/jira/kb/how-to-identify-and-list-when-a-fiel…
  4. micro1.ai/blog/micro1-commits-1b-to-enterprise-data-ac…
  5. 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