Brief-to-client-acceptance records in Asana, Google Drive and Gmail: what the client actually approved

Short answer

A company connects brief-to-client-acceptance records by keeping one project reference across the Asana task, the Drive files and the Gmail thread, and by recording which version of each file the client had in front of them when they said yes. The brief version, the delivered work and the acceptance message each sit in a different system. The case that breaks the chain is common: the client approves an attached report, but its linked appendix lives in Drive and keeps changing after approval.

Visual briefFull-size diagram
A three-lane timeline for Drive, Asana and Gmail: brief version 3 links to the kickoff task, report version 2 is sent with a live link to the appendix, the client approves on October 7, the appendix is edited on October 9 and a figure is queried on October 20.
Illustrative. Pasted links join most steps; the appendix stayed a live link and changed after the approval.

The business task: getting a client to accept the work

An agency or consultancy turns a client request into a deliverable and gets it accepted. Along the way the request document is revised, drafts go back and forth, and acceptance arrives as a reply to an email. Each acceptance is a decision with a stated basis, and the misses, such as rework, disputed scope or a figure the client later questions, show where the process went wrong. That is the kind of record that is scarce in public data, as what data is missing from AI training explains.

How can a company connect brief-to-client-acceptance records across systems?

With a joined timeline that names the file version at every step. Below is an Illustrative example built for this page: a 180-person brand research agency delivers a positioning study.

Date and timeSystemEventVersion named
September 2Google DriveClient signs off brief version 3, a Google DocBrief v3
September 2AsanaProject created; brief linked on the kickoff taskBrief v3
October 6, 10:12GmailReport PDF attached to the delivery email; the report's Appendix B is a link to an Excel workbook stored in DriveReport v2; appendix not named
October 7, 14:05GmailClient replies "Approved, thanks"Report v2 by implication
October 7, 14:30AsanaAccount lead marks the acceptance task Approved and comments with a link to the emailReport v2
October 9Google DriveAnalyst corrects sample counts in two appendix tables, uploading a new version of the workbookAppendix, newer version
October 20GmailClient queries a figure in Appendix BUnclear

The first five rows join because people pasted links. The last two expose the gap: the approval covered the attachment, which is frozen in the email, while the appendix was a link to a file that changed afterwards. Which appendix did the client approve? Only Drive's version history can answer, and only while that version still exists. For workbooks, PDFs and other files that are not Google Docs, Sheets or Slides, Drive can delete older versions 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 and set by the administrator for Workspace accounts, Gmail removes the attachment and inserts a Drive link instead, after checking that recipients can open it. A heavy appendix can become a live link on its own.

Reading the joined record

QuestionAnswer from the joined record
What was the work built to?Version 3 of the client request, signed off September 2
What did the client receive?Report v2 as a PDF attachment, plus a link to the appendix workbook
What exactly was approved?The attachment, by reply; the appendix only by implication
Did anything change after approval?Yes, two appendix tables on October 9
Can the approved appendix be recovered?Yes, if its October 6 version still exists in Drive version history

Three questions this case gives a partner to ask

The worked case turns into three plain questions for the operations director or head of client services. None requires opening a file.

  1. When a client approves by email, does anyone record which file versions the approval covered, including linked ones?
  2. Are deliverables mostly Google Docs, Sheets and Slides, or uploaded PDFs and workbooks whose older versions Drive may delete after 30 days?
  3. How often was accepted work later queried or reworked, by the company's own rough estimate?

"Yes, we pin versions at approval", "sometimes" and "we don't know" are all useful answers. The full metadata packet, with systems, years, volumes and admin owners, is laid out in the warm introduction brief and metadata packet; the metadata-only Google Drive inventory template and the client opportunity brief generator help with the rest. System notes are on the Asana, Gmail and Google Drive pages, and more guides are in the systems hub.

Who can authorize a discussion, and does the company qualify?

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. Client ownership is the main rights question for agencies: deliverables often belong to the client, while the agency's own process notes, templates and approval history may be its own. How agencies separate their own records from client-owned work covers that line, and SourceX's rights review settles it with the company. Partners never ask for or handle raw client records.

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. Google Workspace partners have an overview on the Google Workspace partner page.

Go deeper on brief-to-client-acceptance records

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 can say how its clients approve work and whether linked files are pinned to a version, register as a partner, check it against who qualifies, and read the program terms before introducing its founder or COO.

  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 SourceX connect to Asana, Google Drive or Gmail?

This page does not describe a connector for any of them. The records stay in the company's own accounts, and nothing is prepared or moved before a rights review and a signed agreement.

What if clients approve in a portal or by e-signature instead of by email?

Then the portal or signature record replaces the Gmail thread in the chain. The question stays the same: does the approval name the exact version of every file it covers, including linked ones?

Are client deliverables something an agency can license?

Often not in full. Deliverables are frequently owned by the client under the services agreement, while the agency's own briefs, process notes and approval history may be its own. SourceX's rights review sorts this out with the company.

Sources

  1. help.asana.com/s/article/approvals
  2. support.google.com/drive/answer/2409045
  3. support.google.com/mail/answer/6584
  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