Brief-to-client-acceptance metadata packet: the fields a partner can share without opening a task, file or email

Short answer

A partner can collect the shape of the chain and nothing inside it: which system holds the brief, the work product and the client's acceptance; the date range and rough count for each; the object type; who administers it; what key, if any, joins one step to the next; and what nobody yet knows. That fits on one page. The packet below lists every field, shows an Illustrative filled copy, and marks the line it never crosses.

Visual briefFull-size diagram
A packet card fills in field by field (systems, date range, counts, owners, join key, unknowns) while a stack of raw tasks, files and email threads beside it stays closed under a lock.
Illustrative packet. The fields describe the records; the records themselves stay locked with the company.

The packet is part of the warm introduction brief for a business owner. The case behind it, a client approving work across three tools, is walked through in the brief-to-client-acceptance evidence chain.

What the packet holds, and the line it never crosses

Think of the packet as a label on a sealed box. It says what is inside, roughly how much, how old it is and who has the key. It never contains the contents.

Allowed in the packetNever in the packet
System names: Asana, Google Drive, GmailTask titles, file names or email subjects
Object types: approval task, file with versions, threadClient names, brand names or campaign names
Year ranges and rough count bandsExported lists, even of counts by client
Admin owners by roleScreenshots of settings pages that show user or client names
The join key's form, such as "project code in subject"Any example of the key itself
Known unknowns, written as questionsGuesses written as facts

If an admin offers to send "a quick export so you can see", decline. A packet built from metadata is something the owner can forward; a packet with an export attached is a data transfer.

The packet, section by section

Fill it with the owner and their admins in one sitting. Every field is answered from the admin console or from memory.

Section A: company and sponsor

FieldWhat to write
A1 SponsorName and role of the person who can authorize a licensing discussion
A2 Service lines in scopeWhich kinds of client work the chain covers
A3 Headcount at peakFull-time employees, contractors excluded
A4 Client contract positionWhether client agreements restrict reuse of briefs or deliverables: yes, no, some, unknown

Section B: one block per system

FieldWhat to write
B1 Step heldBrief and revisions, work product, or acceptance
B2 Object typeApproval task, file with version history, email thread
B3 First year and last yearFrom the admin console
B4 Count bandRough, never exact
B5 Admin ownerRole, not personal email
B6 Retention or deletion settingAs the admin understands it today

Section C: the links between steps

FieldWhat to write
C1 Brief to work productWhat ties them: a Drive link in the task, a shared code, nothing
C2 Work product to acceptanceWhether the accepted file is attached, linked or only described
C3 Join key reliabilityFrom which year the key is used consistently

Section D: known unknowns

Write each as a question with an owner. D1 is always the appendix question below.

Illustrative filled packet: a 190-person packaging design consultancy

Every value is invented to show the level of detail.

FieldValue
A1 SponsorManaging director
A2 Service linesPackaging design and retail display
A3 Headcount at peak190 full-time
A4 Client contractsSome restrict reuse; counsel holds the list
B AsanaApproval tasks for briefs and rounds, 2018 to now, about 6,000, operations manager
B Google DriveDesign files and appendices with versions, 2016 to now, about 45,000, IT lead
B GmailClient acceptance threads, 2016 to now, count unknown, IT lead
C1 Brief to work productDrive link pasted in most approval tasks since 2019
C2 Work product to acceptanceFinal file attached when small; linked when large
C3 Join keyJob number in the email subject, consistent since 2020
D1Is the appendix version the client saw recoverable? Owner: IT lead
D2Were projects before 2018 tracked in another tool? Owner: operations manager

Three things make this a good packet. It names a join key without claiming the tools are connected. It dates where the key becomes reliable. And it leaves the Gmail count blank rather than guessing.

Recording the linked-appendix gap without opening a file

The weakest point in the chain is usually an acceptance that covers a main file while a referenced appendix travels as a link. Two documented behaviors explain why, and both can be answered from settings, not content.

  • Large attachments become links. Gmail removes attachments over its size limit and adds them as Google Drive links instead. So the client may have approved an email that points to a live file that was edited later.
  • Old versions can age out. For Drive 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 a version is marked Keep forever.

On the Asana side, approval tasks can be marked Approve, Request changes or Reject, and an Asana resource export includes task stories (comments and changes) by default, though attachment entries need a separate lookup to get current links. That tells the owner the brief history is likely recoverable even if file links have moved.

So D1 is one question to the IT lead: when a client approves a deliverable with linked appendices, does the team keep or export the version that was approved? "Yes", "sometimes" and "unknown" are all valid answers. The missing-context comparison shows what the chain looks like with and without that answer.

Who fills it in, who signs off, and what stays unknown

Admins supply the values; the sponsor in A1 decides whether the packet is shared and with whom. If A4 says client contracts restrict reuse, the packet still goes forward, because SourceX's rights review is where that gets tested. What stays unknown until SourceX reviews the company: rights, de-identification needs, buyer interest and any offer.

Before you pass it on, check fit: 50+ full-time employees at peak (contractors excluded), a 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. Sign the Channel Partner Agreement, tell the sponsor you are a SourceX referral partner who may receive a reward funded separately by SourceX, and introduce them through your partner account. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application.

For tool-by-tool detail, use the Google Drive inventory template, the Gmail inventory template and the Asana system page; preparing a metadata-only inventory covers other systems, and the client opportunity brief generator turns the packet into a short note.

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.

When the sponsor has filled in the packet and wants to talk, register as a partner, confirm the company against who qualifies and read the terms before introducing them.

  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

Can the partner fill in the packet on the owner's behalf?

The partner can hold the pen while the owner's admins read out answers, but every value comes from them. The partner never logs in to Asana, Drive or Gmail to look something up.

Is an approximate count good enough?

Yes. Bands such as "about 6,000" or "between 10,000 and 20,000" are what the packet asks for. Exact counts invite someone to run a report, which is more access than the first conversation needs.

Does SourceX need a connector for every tool named in the packet?

The packet does not assume one. It records which systems hold each step; how any approved records would be prepared and delivered is settled later, under a signed agreement.

Sources

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