Approval-to-delivery missing context: what a Teams export alone loses, shown before and after the Planner and SharePoint records

Short answer

A single-system export keeps one fact and loses the decision around it. A Teams export shows that someone posted "approved" and when. It does not show which document version was approved, whether the related task closed, or which file the client finally accepted. In the Illustrative case on this page, the context missing from the Teams export is precisely what reveals that the client received a version saved after the approval. Each piece of that context is held in Planner or SharePoint, by a different owner.

Visual briefFull-size diagram
A split panel: on the left a Teams-only record of an approval with three blank fields; on the right the same record with the task status, the approved version 4.0 and the delivered version 5.0 slid into place, exposing the mismatch.
Illustrative. The Teams export shows that someone approved; only the other records show what was delivered.

This page belongs to the approval-to-delivery records guide. It reads one case twice, before and after the surrounding records are added. The keys that join the systems are on the record chain page.

Before: the approval as a Teams export shows it

Illustrative. A fictional 340-person architecture practice exports the Teams messages for one housing project ahead of a records review. For the planning drawing set due to the city on a Friday, the relevant entry is one message in a group chat:

Field in the Teams exportValue
WhereGroup chat of three: project architect, associate, technician
Sent byProject architect
TimeTuesday, 18:12
Message typeChat reply
Content summaryFine to issue
Attachments or linksNone

From this alone, a reader would conclude that the drawing set was signed off on Tuesday evening and issued soon after. The export is accurate. It is silent on everything around the message, including which drawings "fine to issue" meant.

After: the same approval with its task and file history

Add the Planner board and the SharePoint library for the same week, still Illustrative:

WhenSourceWhat it adds
Tuesday, 16:30SharePointDrawing set PDF saved as version 4.0 by the technician
Tuesday, 18:12TeamsThe "fine to issue" chat reply above
Wednesday, 08:50Planner"Planning submission" task closed by the associate, PDF attached
Thursday, 14:05SharePointVersion 5.0 saved after the associate moved a boundary dimension
FridayOutside the three toolsSubmission receipt from the city's portal

The chat reply almost certainly covered version 4.0, the latest when it was sent. The city almost certainly received version 5.0, saved two days later. Nobody signed off version 5.0. None of the three systems is wrong; the gap appears only when they are read in one sequence.

What goes missing, and where it is kept

Context a reader needsIn the Teams export?Where it is keptUsual owner
Who approved, and whenYesTeams channel or chatTeams or Microsoft 365 admin
Which file the approval referred toOnly if a link was pastedInferred from SharePoint version timesSite owner
Whether the work item closedNoPlanner task status and completion datePlan owner, often a project lead
Which file the task deliveredNoPlanner attachment pointing to the libraryPlan owner
What changed after approvalNoSharePoint version historySite owner or records manager
What the client acceptedNoTransmittal, portal or email outside the toolsProject lead or account manager

Where things are kept also depends on where they were said. Microsoft's eDiscovery documentation says one-on-one and group 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. The approval in this case was a group chat reply, so it sits in the three participants' mailboxes, and a channel-only export would not have shown it at all.

Events that remove context quietly

Context is not only lost by exporting one system. It is also removed by ordinary administration, often before anyone thinks about it as evidence.

EventWhat it can removeWhy
A Teams retention policy that deletes messagesThe approval posts themselvesRetention policies can delete chat and channel messages after a set period
Approvals given by reactionThe sign-off recordMicrosoft lists reactions among items Teams retention does not keep
A low version limit on a libraryVersion 4.0, the one that was approvedLibrary settings can cap how many versions are kept
Deleting completed plans after a projectTask status and the task-to-file linkThe task record goes with the plan
A tenant migration or subscription endWhatever the migration scope leaves outScope decisions are made project by project

Microsoft's retention documentation also notes that files shared in Teams are not covered by Teams retention policies; they follow the SharePoint or OneDrive settings instead, so messages and files can age out on different schedules. For the subscription case, the page on Microsoft 365 data after a subscription ends covers the timeline, and the ERP replacement handoff checklist shows the same "what are we about to lose?" questions in another setting.

The before-and-after difference is also why records like these interest AI developers. A system that learns only from approvals, or only from file versions, never sees the step where an approved document changed, which is the kind of gap discussed in why AI agents fail and what data is missing from AI training.

Describing the gap without opening anything

Ask the sponsor three things for each row of the "where it is kept" table: does that system still hold it, for which years, and who owns it. Then ask the question this page is about: "If someone saves a new version after an informal approval, does anything record that?" A plain "no" is a useful answer. The completeness checklist turns the answers into a score.

The answers usually come from a Microsoft 365 administrator, a records manager and a project lead. 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, and client contracts may need counsel's review. 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.

Unknown until SourceX reviews it: whether there is demand for this record type, what the rights review concludes, how personal data and client names would be handled, and what the company would be paid. Partners never ask for or handle messages, tasks or files.

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 company still holds the approvals, tasks and file versions together, and knows which of them a planned clean-up would remove, register as a partner, check who qualifies, and read the terms before you introduce the sponsor.

  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 a thumbs-up reaction count as context that might be lost?

It might. Microsoft's documentation lists reactions among the items Teams retention does not keep, so a team that approves with reactions may have no durable record of its sign-offs. Ask how approvals are usually given.

Is a SharePoint export alone better than a Teams export alone?

It keeps different things. It holds every saved version with author and date, but nothing says whether any version was approved or which one went to the client. Neither export carries the decision on its own.

What should a partner do if a migration is about to delete old plans or channels?

Tell the sponsor that the decision about what to keep is being made now, and suggest the records manager is in that conversation. Do not take or request copies yourself; the company decides what it keeps.

Sources

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