Approval-to-delivery record chain: joining a Teams approval, a Planner task and a SharePoint file version end to end

Short answer

A company connects approval-to-delivery records by finding the shared key at each hand-off: a link or file reference from the Teams approval to the Planner task, the task's attachment pointing at the SharePoint file, a version number tying the approval to the exact file version, and a transmittal or acceptance record tying that version to the client. Only the task-to-file key is a built-in feature. The rest depend on habit or on matching timestamps, and the record should say which.

Visual briefFull-size diagram
Four records step down a staircase, Teams approval, Planner task, SharePoint version and client acceptance, joined by keys; the approval-to-version join is dashed and marked inferred until a version number in the approval post makes it solid.
Illustrative chain. Only the task-to-file join is a feature of the tools; the approval-to-version join is inferred from time.

This page is part of the approval-to-delivery records guide and does one job: map the keys. For what one tool's export loses on its own, see the missing context page.

Four records, three keys: the chain table

StepRecordKey that joins it to the next stepSystemJoin type
1. Sign-off requested and givenChannel post or chat replyTask title or link pasted into the postTeamsHabit
2. Work marked doneTask with status, assignee, completion dateAttached link or uploaded filePlannerDesigned
3. File issuedFile version with author and save timeVersion number in the approval, or nothingSharePointInferred unless stated
4. Client acceptsTransmittal, portal entry or emailFile name and version on the transmittalOutside the three toolsHabit

Three join types are enough to describe any chain like this. Designed joins are created by the tool when people use it normally. Habit joins exist only when people paste references. Inferred joins are reconstructed from time order and can be wrong. A company that can label each hand-off this way has already done the most useful part of the description.

Key by key: how strong each join is

Approval to task. Teams stores messages in different places depending on where they were posted: Microsoft's documentation says one-on-one and group chats sit in participants' Exchange Online mailboxes, channel messages in the mailbox associated with the team, and channel files in the team's SharePoint site. An approval given in a private chat is therefore held apart from the project channel, and neither carries a task ID unless someone typed it. Ask where approvals are normally given and whether they name the task.

Task to file. This is the strongest link. Microsoft Support says a Planner task can carry files, photos or links as attachments, and uploaded files are stored in the SharePoint library associated with the plan. A completed task with an attachment points at a specific file. The weak spot is whether the attachment points at the library copy or at a stray copy somewhere else.

Approval to file version. The link that matters most is usually the weakest. SharePoint versioning is on by default and version history shows who changed a file and when, so the version dates exist. But the approval post rarely names a version. The join is then made by comparing the post's time with the version save times, which works until someone saves a new version after the approval.

File to acceptance. Acceptance often happens outside all three tools. A transmittal that names the file and version is a habit join; an email saying "received, thanks" is barely a join at all.

Hand-offCommon breakHow it shows up laterWhat a sponsor can say about it
Approval to taskApproval given in a private chat, no task namedThe task closed with no visible sign-offWhere approvals are usually given, by team
Task to fileAttachment points to a copy outside the libraryTask links to a file that is not the delivered oneWhether attachments use the library
Approval to versionEdits saved after the approvalApproved and delivered versions differWhether re-approval is required after edits
Version to acceptanceAcceptance recorded only in inboxesNo system record of what the client tookWhich system holds acceptance, if any
Any hand-offLibrary version limit trims old versionsThe approved version no longer existsThe library's version limit and since when

The last row is a setting, not a habit. Library settings can cap how many versions are kept, so on a busy file the version someone approved may already have been trimmed. Ask what the limit is.

One report traced (Illustrative)

A fictional 260-person engineering consultancy issues a site 14 inspection report. Every value is Illustrative.

TimeSystemEventJoined byJoin type
Day 1, 10:02SharePointVersion 2.0 saved by the authorFile pathDesigned
Day 1, 15:40Teams"Approved" posted in the project channelTime after version 2.0Inferred
Day 1, 16:05PlannerTask marked complete, link to the file attachedTask attachmentDesigned
Day 2, 09:15SharePointVersion 3.0 saved by a second engineerFile pathDesigned
Day 3, 11:30EmailClient accepts the issued reportFile name, no versionHabit

Read the join column. The company can tell a reviewer that task-to-file is complete, approval-to-version is inferred, and the client accepted a report whose version is not stated, which on day 3 was most likely version 3.0, saved after the approval. That is an honest, specific description, and it required nobody to open the report.

Reading the chain with the sponsor, and what stays open

Walk the sponsor through the join-type column for their own projects: which hand-offs are designed, which depend on habit, which are inferred, and since what year. A Microsoft 365 administrator and a project lead can usually answer between them. The person who can authorize a licensing discussion is the CEO, who in many professional firms is the managing partner, often with a COO or CIO as sponsor. Background on the platforms is on the SharePoint and Teams pages, and the guide for implementation partners on SharePoint projects covers where these conversations arise. The completeness checklist scores the result.

Confirm the company baseline: 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.

Open until SourceX reviews the opportunity: whether client contracts allow licensing of deliverables, how personal data and client names would be handled, whether a buyer wants this kind of history, and what the company would be paid. The company joins its own records under an agreement if a discussion goes ahead; the partner never handles messages, tasks or files, and SourceX does not claim a connector for any of the three tools.

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 sponsor can label each hand-off as designed, habitual or inferred and an officer will take the call, register as a partner, check who qualifies, and read the 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 join inferred from timestamps worthless?

No, but it must be labeled. A post made a few hours after version 2.0 was saved probably approved version 2.0, and usually that is right. Marking the join as inferred tells a reviewer where it could be wrong, which is more useful than presenting a guess as a fact.

Does the partner need to check whether links were pasted into posts?

No. Ask the project lead whether the team habitually links tasks or files in approval posts, and since when. The answer is the metadata; nobody needs to scroll a channel.

What if client acceptance is recorded in email?

Then the last step sits outside Teams, Planner and SharePoint. Note which system holds it and who owns it. If acceptance lives only in personal inboxes, record that as a gap.

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