Approval-to-delivery completeness scorecard: checking Teams, Planner and SharePoint records at metadata level before an introduction

Short answer

An approval-to-delivery trail breaks when an approval names no task or file, when messages or old versions have been deleted, when a file changes after sign-off without a new approval, when client acceptance is never recorded, or when no one owns the chain across all three tools. This scorecard turns those failures into nine questions grouped under coverage, linkage and outcome. Each is answered by the company, marked pass, partial or fail, and none requires anyone to open a message, task or file.

Visual briefFull-size diagram
A ring meter fills to 11 of 18 as nine checks grouped under coverage, linkage and outcome tick pass, partial or fail; the post-approval edit check is marked fail.
Illustrative score for a fictional consultancy. The ring shows completeness, not eligibility.

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:

  1. Mark a fail when nobody knows, and write down who could find out.
  2. Note the year each pass or partial started. Coverage from 2019 and from 2024 describe very different histories.
  3. 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?

CheckQuestion to askPassPartialFail
C1. Message retentionIs a Teams retention policy deleting chat or channel messages, and after how long?Messages retained for the years in scopeRetained for some teams or a short periodDeleted after projects, or unknown
C2. Version depthHow many versions does the delivery library keep?Enough that approved versions survive on busy filesLimit set low on some librariesVersioning trimmed hard or switched off
C3. Plan retentionAre completed plans kept after a project closes?KeptKept for recent years onlyDeleted 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?

CheckQuestion to askPassPartialFail
L1. Approval names the workDo approval posts usually name the task or link the file?Standard practiceSome teams or project typesApprovals say "looks good" with no reference
L2. Approval locationAre approvals given in the project channel rather than private chats?Mostly in channelsMixedMostly private chats or calls
L3. Task points at the fileDo completed tasks carry a link or attachment to the library file?Usual practiceSometimesRarely
L4. Post-approval editsCan a file change after approval without a new sign-off, and is that recorded?Re-approval required or edits flaggedRequired for some deliverablesEdits 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?

CheckQuestion to askPassPartialFail
O1. Client acceptanceWhere is client acceptance recorded, and does it name the version?A system record naming the versionA system record without the versionPersonal inboxes only
O2. Chain ownershipDoes one person or team understand all three systems for delivery work?Yes, namedShared between two people who talkEach 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:

CheckMarkPointsNote
C1. Message retentionPass2No deletion policy on project channels since 2019
C2. Version depthPass2Default limits; approved versions survive
C3. Plan retentionPartial1Plans before 2022 deleted at close
L1. Approval names the workPartial1Engineering links files; advisory does not
L2. Approval locationPass2Mostly in channels
L3. Task points at the filePass2Attachments standard since 2021
L4. Post-approval editsFail0Edits after sign-off are common and unrecorded
O1. Client acceptancePartial1Transmittal log without version numbers
O2. Chain ownershipFail0Three separate owners
TotalSum of points11 of 18Strong 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.

  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

Should I try to estimate how often files change after approval?

No. Ask whether the company sees the pattern and whether anything records it. Quantifying it requires reading records, which the company and SourceX do during review under an agreement.

What if different teams in the company work differently?

Score the teams or practice areas that hold the most delivery history, and note the others as partial. A scorecard that says 'pass for engineering, fail for advisory' is more useful than an average.

Is a high score a promise that the records will be licensed?

No. The score describes completeness. Demand, the rights review and any offer are decided only after the company applies and SourceX reviews the opportunity.

Sources

  1. learn.microsoft.com/en-us/purview/retention-policies-teams
  2. support.microsoft.com/office/enable-and-configure-versioning-for-a…
  3. support.microsoft.com/en-us/planner/attach-files-photos-or-links-t…
  4. learn.microsoft.com/en-us/purview/edisc-search-teams
  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