# Approval-to-delivery missing context | SourceX

Canonical: https://refer.sourcex.si/guides/approval-to-delivery-missing-context
Last updated: 2026-11-04

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.

This page belongs to the [approval-to-delivery records guide](/guides/chain-approval-to-delivery). 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](/guides/approval-to-delivery-record-linkage).

## 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 export | Value |
|---|---|
| Where | Group chat of three: project architect, associate, technician |
| Sent by | Project architect |
| Time | Tuesday, 18:12 |
| Message type | Chat reply |
| Content summary | Fine to issue |
| Attachments or links | None |

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:

| When | Source | What it adds |
|---|---|---|
| Tuesday, 16:30 | SharePoint | Drawing set PDF saved as version 4.0 by the technician |
| Tuesday, 18:12 | Teams | The "fine to issue" chat reply above |
| Wednesday, 08:50 | Planner | "Planning submission" task closed by the associate, PDF attached |
| Thursday, 14:05 | SharePoint | Version 5.0 saved after the associate moved a boundary dimension |
| Friday | Outside the three tools | Submission 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 needs | In the Teams export? | Where it is kept | Usual owner |
|---|---|---|---|
| Who approved, and when | Yes | Teams channel or chat | Teams or Microsoft 365 admin |
| Which file the approval referred to | Only if a link was pasted | Inferred from SharePoint version times | Site owner |
| Whether the work item closed | No | Planner task status and completion date | Plan owner, often a project lead |
| Which file the task delivered | No | Planner attachment pointing to the library | Plan owner |
| What changed after approval | No | SharePoint version history | Site owner or records manager |
| What the client accepted | No | Transmittal, portal or email outside the tools | Project 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.

| Event | What it can remove | Why |
|---|---|---|
| A Teams retention policy that deletes messages | The approval posts themselves | Retention policies can delete chat and channel messages after a set period |
| Approvals given by reaction | The sign-off record | Microsoft lists reactions among items Teams retention does not keep |
| A low version limit on a library | Version 4.0, the one that was approved | Library settings can cap how many versions are kept |
| Deleting completed plans after a project | Task status and the task-to-file link | The task record goes with the plan |
| A tenant migration or subscription end | Whatever the migration scope leaves out | Scope 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](/systems/microsoft-365-data-after-subscription-ends) covers the timeline, and the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) 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](/questions/why-ai-agents-fail) and [what data is missing from AI training](/questions/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](/resources/approval-to-delivery-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](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the sponsor.

## Sources

- https://learn.microsoft.com/en-us/purview/edisc-search-teams
- https://learn.microsoft.com/en-us/purview/retention-policies-teams
- https://support.microsoft.com/office/enable-and-configure-versioning-for-a-list-or-library-1555d642-23ee-446a-990a-bcab618c7a37
- https://support.microsoft.com/en-us/planner/attach-files-photos-or-links-to-a-task
- https://refer.sourcex.si/terms
