# Approval-to-delivery record chain | SourceX

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

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.

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

## Four records, three keys: the chain table

| Step | Record | Key that joins it to the next step | System | Join type |
|---|---|---|---|---|
| 1. Sign-off requested and given | Channel post or chat reply | Task title or link pasted into the post | Teams | Habit |
| 2. Work marked done | Task with status, assignee, completion date | Attached link or uploaded file | Planner | Designed |
| 3. File issued | File version with author and save time | Version number in the approval, or nothing | SharePoint | Inferred unless stated |
| 4. Client accepts | Transmittal, portal entry or email | File name and version on the transmittal | Outside the three tools | Habit |

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.

## Where links break

| Hand-off | Common break | How it shows up later | What a sponsor can say about it |
|---|---|---|---|
| Approval to task | Approval given in a private chat, no task named | The task closed with no visible sign-off | Where approvals are usually given, by team |
| Task to file | Attachment points to a copy outside the library | Task links to a file that is not the delivered one | Whether attachments use the library |
| Approval to version | Edits saved after the approval | Approved and delivered versions differ | Whether re-approval is required after edits |
| Version to acceptance | Acceptance recorded only in inboxes | No system record of what the client took | Which system holds acceptance, if any |
| Any hand-off | Library version limit trims old versions | The approved version no longer exists | The 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.

| Time | System | Event | Joined by | Join type |
|---|---|---|---|---|
| Day 1, 10:02 | SharePoint | Version 2.0 saved by the author | File path | Designed |
| Day 1, 15:40 | Teams | "Approved" posted in the project channel | Time after version 2.0 | Inferred |
| Day 1, 16:05 | Planner | Task marked complete, link to the file attached | Task attachment | Designed |
| Day 2, 09:15 | SharePoint | Version 3.0 saved by a second engineer | File path | Designed |
| Day 3, 11:30 | Email | Client accepts the issued report | File name, no version | Habit |

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](/systems/microsoft-sharepoint) and [Teams](/systems/microsoft-teams) pages, and the guide for [implementation partners on SharePoint projects](/guides/how-microsoft-implementation-partners-spot-referral-opportunities-during-microsoft-sharepoint-projects) covers where these conversations arise. The [completeness checklist](/resources/approval-to-delivery-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](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you make the introduction.

## Sources

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