The scorecard is part of the approval-to-delivery records guide. The record chain page explains the joins it tests, and the missing context page shows what a broken trail looks like from one export.
How to run the scorecard in one call
Book 30 minutes with a Microsoft 365 administrator and a project lead from the practice area with the most delivery history. Read each question aloud and write down the answer in their words before marking it. Score 2 for a pass, 1 for a partial and 0 for a fail, for a maximum of 18.
Three rules keep the card reliable:
- Mark a fail when nobody knows, and write down who could find out.
- Note the year each pass or partial started. Coverage from 2019 and from 2024 describe very different histories.
- Never verify an answer by looking. If the sponsor offers to show you a channel or a library, decline; the answer in words is the metadata.
Coverage checks: does the history still exist?
| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| C1. Message retention | Is a Teams retention policy deleting chat or channel messages, and after how long? | Messages retained for the years in scope | Retained for some teams or a short period | Deleted after projects, or unknown |
| C2. Version depth | How many versions does the delivery library keep? | Enough that approved versions survive on busy files | Limit set low on some libraries | Versioning trimmed hard or switched off |
| C3. Plan retention | Are completed plans kept after a project closes? | Kept | Kept for recent years only | Deleted at project close |
Microsoft's documentation says Teams retention policies can retain or delete chat, channel and private channel messages, with the clock starting when a message is created, and files used with Teams follow their own SharePoint and OneDrive policies. So C1 and C2 can have different answers for the same project, and both matter. SharePoint versioning is on by default, but library settings can cap how many versions are kept, which is what C2 asks about.
Linkage checks: can one step find the next?
| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| L1. Approval names the work | Do approval posts usually name the task or link the file? | Standard practice | Some teams or project types | Approvals say "looks good" with no reference |
| L2. Approval location | Are approvals given in the project channel rather than private chats? | Mostly in channels | Mixed | Mostly private chats or calls |
| L3. Task points at the file | Do completed tasks carry a link or attachment to the library file? | Usual practice | Sometimes | Rarely |
| L4. Post-approval edits | Can a file change after approval without a new sign-off, and is that recorded? | Re-approval required or edits flagged | Required for some deliverables | Edits happen unrecorded |
L2 matters because of where messages are stored: one-on-one and group chats sit in participants' Exchange Online mailboxes, while channel messages sit with the team. Approvals scattered across private chats are harder for the company to gather, even under an agreement. For L3, Planner attachments can be links or uploaded files, and uploaded files land in the plan's SharePoint library, so a pass here is the strongest join in the chain.
Outcome checks: is the end of the chain recorded and owned?
| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| O1. Client acceptance | Where is client acceptance recorded, and does it name the version? | A system record naming the version | A system record without the version | Personal inboxes only |
| O2. Chain ownership | Does one person or team understand all three systems for delivery work? | Yes, named | Shared between two people who talk | Each tool has a separate owner and none sees the chain |
The post-approval edit test, and an Illustrative result
L4 deserves the most care, because it is the case an AI system trained on these records would most need to see labeled. Illustrative: a fictional 260-person engineering consultancy approves a site 14 report at version 2.0, closes the task, and issues version 3.0 the next day after a junior engineer corrects a table. The approval is real, the task closure is real and the delivered file is real, but the approval does not cover the delivered file.
A company that can say "we see this, and roughly how often" is describing a known gap. That is far better than an unknown one. Do not try to count it yourself. The consultancy's full card looked like this:
| Check | Mark | Points | Note |
|---|---|---|---|
| C1. Message retention | Pass | 2 | No deletion policy on project channels since 2019 |
| C2. Version depth | Pass | 2 | Default limits; approved versions survive |
| C3. Plan retention | Partial | 1 | Plans before 2022 deleted at close |
| L1. Approval names the work | Partial | 1 | Engineering links files; advisory does not |
| L2. Approval location | Pass | 2 | Mostly in channels |
| L3. Task points at the file | Pass | 2 | Attachments standard since 2021 |
| L4. Post-approval edits | Fail | 0 | Edits after sign-off are common and unrecorded |
| O1. Client acceptance | Partial | 1 | Transmittal log without version numbers |
| O2. Chain ownership | Fail | 0 | Three separate owners |
| Total | Sum of points | 11 of 18 | Strong coverage, weak version-to-approval link |
The sentence for a reviewer: "Approvals and versions retained since 2019, tasks since 2022; files often change after informal approval and nothing records it; acceptance logged without versions." The data quality due diligence page explains how buyers read gaps like these, and what happens after data delivery covers the stages that follow a license.
What the score tells SourceX, and what it does not
It tells a reviewer which parts of the chain exist and how far back. It does not settle eligibility, rights, demand or price. The person who can authorize a licensing discussion is the CEO, or the managing partner in a partnership, and client contracts may restrict what deliverables can be licensed. The audit considerations page covers how a new revenue line like this is usually reviewed internally.
The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, 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. Partners never ask for or handle raw messages, tasks or files, and SourceX does not claim a connector for Teams, Planner or SharePoint.
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 the company can describe honestly, post-approval edits included, and an officer will take the first call, register as a partner, check who qualifies, and read the terms before you introduce them.