Approval-to-delivery records in Teams, Planner and SharePoint: a metadata packet for an introduction

Short answer

A partner can collect a metadata packet: which Microsoft 365 tools hold each step from approval message to task to accepted document, the date range and rough volume of each, the object types (chat message, channel post, task, file version), who administers each system, and which links between steps are known or unknown. Nothing in the packet requires opening a message, task or file. The open question to flag is a document that changed after someone approved it informally.

Visual briefFull-size diagram
A metadata packet with one card each for Teams, Planner and SharePoint showing object type, owner and the retention question to ask, with the Teams-to-Planner link marked as existing only if a link was pasted and the Planner-to-SharePoint link as a task attachment.
Illustrative packet. The open case, version 3.0 saved after the approval, is flagged for review, not solved by the partner.

The business task this chain records

The chain is a common delivery pattern in professional services: someone asks for a sign-off in a chat, a project lead closes a task, and a final file goes to the client. Each step sits in a different tool, so the decision that connects them is often visible only when the three are read together.

Take an Illustrative case built for this page. A 260-person engineering consultancy issues inspection reports to clients. A senior engineer posts in a Teams channel, "Report for site 14 looks good, approved", while the draft is at version 2.0 in SharePoint. The project coordinator marks the Planner task "Issue site 14 report" complete. The file the client accepts two days later is version 3.0, because a junior engineer corrected a table after the approval. No second approval appears anywhere.

That last step is what makes approval-to-delivery records interesting to AI developers building systems that need to understand how real decisions travel between people and tools, and it is also what makes the chain fragile. Microsoft's own documentation shows why the pieces scatter: one-on-one and group Teams chats are stored in participants' Exchange Online mailboxes, channel messages in the mailbox associated with the team, and channel files in the team's SharePoint site. Planner attachments can be links or uploaded files, and uploaded files land in the SharePoint library tied to the plan.

What metadata can a referral partner collect about approval-to-delivery without reading private content?

Collect descriptions, not records. The packet below is the evidence asset for this page: every row can be filled from a 20-minute conversation with an IT or operations lead, and cells marked "unknown until reviewed" are the ones nobody can answer until SourceX reviews the opportunity.

Packet fieldTeams (approval message)Planner (task)SharePoint (document)
Object typeChannel post or chat replyTask with status and assigneeFile with version history
Date range to ask forFirst and last year of active channelsFirst and last year of active plansFirst and last year of the delivery library
Rough volumeNumber of active project channelsNumber of plans and tasks per yearNumber of delivered files per year
Who administers itMicrosoft 365 or Teams adminPlan owners, often project leadsSite owner or records manager
Retention setting known?Ask whether a retention policy appliesAsk whether completed plans are deletedAsk how many versions the library keeps
Link to the next stepUnknown until reviewed: does the post name a task or file?Known if the task carries a link or attachmentKnown only through version dates
Status at introductionDescribed, not sharedDescribed, not sharedDescribed, not shared

Two notes on filling it in. First, versioning is on by default in SharePoint libraries, and version history shows who changed a file and when, but library settings can cap how many versions are kept, so "do we still have version 2.0?" is a real question to ask. Second, write counts as ranges ("roughly 3,000 reports a year since 2019"), not exact figures you would need records to verify. The Teams inventory template and the business data inventory worksheet give a fuller field list.

Who can authorize a licensing discussion, and what stays unknown?

The records belong to the company, and the person to introduce is the CEO, who can authorize a licensing discussion and in many professional firms is the managing partner, often with a COO or CIO as sponsor and the Microsoft 365 administrator and the records manager as the people who answer the packet questions. Client deliverables can carry confidentiality terms, so the company's own counsel will want to check client contracts; the guide on board approval for a data licensing agreement covers who signs. For how Teams content in particular is assessed, see licensing Teams chat data for AI training.

Before introducing, check the basics: 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.

What stays unknown until SourceX reviews the opportunity: whether there is demand for this kind of record, what the rights review concludes, how personal data and client names would be handled, what the company would be offered, and therefore any reward. Partners never ask for or handle raw client records. If something sensitive is shared with you by mistake, the guide on sensitive data shared with a vendor explains what to do, and the introduction versus delivery explainer sets out where your role ends. More system-level guides are in the systems hub.

Go deeper on approval-to-delivery records

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 can fill in the packet above and name who owns all three systems, 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

Does SourceX connect directly to Teams, Planner or SharePoint?

This page does not claim a connector for any of them. How records would be prepared and delivered is decided after a rights review and agreement, and the company keeps control of what leaves its systems.

Is a thumbs-up reaction in Teams an approval?

Only the company can say. Many teams treat a reply such as 'approved, send it' as the decision, while reactions are ambiguous. Ask how the company records approvals in practice and note the answer as a known gap if it varies by team.

Can a partner forward a sample approval thread to show the pattern?

No. Describe the pattern in words and counts. Partners never collect or forward chat messages, task exports or files; the company decides later, under an agreement, what is shared.

Sources

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