# Brief to client acceptance: missing context | SourceX

Canonical: https://refer.sourcex.si/guides/brief-to-client-acceptance-missing-context
Last updated: 2026-11-04

Almost everything about what was signed off can be lost. A project tool's export of an accepted job shows that the sign-off task was ticked, when, and usually the account lead's note. It does not hold the customer's own words, which arrived by email, the request revision the work answered, or which edition of a linked annex the customer had open at the moment of sign-off. Those sit in the mailbox and the shared file store. Joined, the same task becomes a full case: request, delivered edition, customer wording, a later edit and the question that followed.

This before-and-after reading belongs to the guide on [brief-to-client-acceptance records in Asana, Google Drive and Gmail](/guides/chain-brief-to-client-acceptance). It reuses that hub's fictional 180-person research agency and its positioning study, and reads the sign-off twice.

## Before: the sign-off as the task export tells it

Asana's approval tasks record one of three outcomes, Approve, Request changes or Reject, and Asana's guidance encourages approvers to explain the decision in a comment. So the export holds the verdict and sometimes the reason.

Asana's resource export is richer than a flat task list. By default it includes stories, meaning the comments and other changes made to each task, plus attachment records. A reviewer would see this for the sign-off task:

| Field in the export | Value | What a newcomer would conclude |
|---|---|---|
| Task | Client acceptance: positioning study | The job ended in acceptance |
| Status | Approved, the day after delivery | The customer accepted the report |
| Comment | "Client approved by email, see link" | Sign-off happened somewhere else |
| File record | Report v2.pdf, listed | The report was the thing accepted |
| Stories | Status changes and two earlier comments | A routine close |

Honest but thin. The comment points to an email; it is not the sign-off. The file record is a listing, not the file: Asana's export reference says attachment objects carry no download or view link, so files must be fetched separately. And nothing mentions that the report leaned on a separate annex.

## After: the same sign-off joined to mail and files

Add what the other two places hold for those weeks.

- **The shared file store** holds request revision 3, signed off a month before delivery, and the annex spreadsheet with its revision history: one edition saved on delivery day and a newer one uploaded two days after sign-off, when an analyst corrected sample counts.
- **The mailbox** holds the delivery email with the PDF attached and the annex as a link, the customer's reply ("Approved, thanks"), and a question two weeks later about a figure in the annex.

Read together, the records show work built to revision 3, a report delivered as v2, a sign-off that covered the attached PDF by reply and the annex only by assumption, a correction after sign-off, and a customer query that the correction may have caused. The decision and its consequence, in order.

## What is lost and where that context lives

| Element | Task export alone | Where the context lives | At risk because |
|---|---|---|---|
| Sign-off status and date | Yes | Asana | Low risk |
| Approver's note | Yes, if written | Asana | Depends on habit |
| The files themselves | Listed, without the file | Mail attachments and the file store | Fetched separately |
| The customer's own words | No | Reply thread in Gmail | Mailbox retention and departures |
| Request revision the work answered | Only if someone linked it | Google Drive revision history | Link discipline |
| Annex edition at sign-off | No | Google Drive revision history | Older editions of uploaded files can be deleted |
| Edits after sign-off | No | Revision history, with time and editor | Same as above |
| The later customer query | No | Gmail | Mailbox retention |

Illustrative. Rows describe the example, not a tested export.

## Why the linked annex is the gap that matters

The attached PDF is frozen in the email. The annex was a live link to a spreadsheet that kept changing. When the customer queried a figure, the only way to know which edition they had accepted was the file store's revision history, and only while that edition still existed. Google's documentation says that for files that are not Google Docs, Sheets or Slides, older versions can be deleted after 30 days or once there are 100 newer versions, unless someone marks a version Keep forever.

Gmail can create the same split without anyone choosing it. Above the attachment limit, 25 MB for personal accounts, Gmail removes the attachment and adds it as a Drive link instead. A heavy annex can become a live link on its own.

So when an agency describes its archive, two facts matter more than volume: whether deliverables are mostly native Google files or uploaded PDFs and workbooks, and whether anyone pins file versions at approval. Both are scarce kinds of evidence, which is why records like these are [missing from most AI training data](/questions/what-data-is-missing-from-ai-training).

## Asking about context without opening a file

A partner can learn the shape of this in one conversation with the operations director or head of client services:

1. When a client approves by email, is the reply linked or pasted into the Asana task?
2. Are linked files pinned to a version, or marked Keep forever, at approval?
3. How long are mailboxes of departed account leads kept?

The [warm introduction brief and metadata packet](/resources/a-warm-introduction-brief-for-a-business-owner) and the [client opportunity brief generator](/tools/client-opportunity-brief-generator) help write the answers up. System notes are on the [Asana](/systems/asana), [Google Drive](/systems/google-drive) and [Gmail](/systems/gmail) pages.

Then check authority and fit. The CEO, often the founder, can authorize a licensing discussion, with the COO as a possible sponsor; the Workspace administrator can describe the archive but cannot approve its use. Deliverables often belong to the client, while the agency's own briefs, process notes and approval history may be its own; [how agencies separate their records from client-owned work](/guides/how-agencies-can-distinguish-their-own-operating-records-from-client-owned-work) covers that line. The company needs 50+ full-time employees at peak (contractors excluded, so freelancers do not count), 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: client contract limits, de-identification, which export fields exist and any offer. Partners never ask for or handle raw client records, and this page does not imply SourceX connects to Asana, Drive or Gmail.

## 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 an agency keeps its approval emails and Drive version history alongside Asana and can say for which years, [register as a partner](/register), check it against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its founder or COO.

## Sources

- https://help.asana.com/s/article/approvals?language=en_US
- https://developers.asana.com/reference/createresourceexport
- https://support.google.com/drive/answer/2409045?hl=en&co=GENIE.Platform%3DDesktop
- https://support.google.com/mail/answer/6584?hl=en&co=GENIE.Platform%3DDesktop
- https://refer.sourcex.si/terms
