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 packet | Never in the packet |
|---|---|
| System names: Asana, Google Drive, Gmail | Task titles, file names or email subjects |
| Object types: approval task, file with versions, thread | Client names, brand names or campaign names |
| Year ranges and rough count bands | Exported lists, even of counts by client |
| Admin owners by role | Screenshots 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 questions | Guesses 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
| Field | What to write |
|---|---|
| A1 Sponsor | Name and role of the person who can authorize a licensing discussion |
| A2 Service lines in scope | Which kinds of client work the chain covers |
| A3 Headcount at peak | Full-time employees, contractors excluded |
| A4 Client contract position | Whether client agreements restrict reuse of briefs or deliverables: yes, no, some, unknown |
Section B: one block per system
| Field | What to write |
|---|---|
| B1 Step held | Brief and revisions, work product, or acceptance |
| B2 Object type | Approval task, file with version history, email thread |
| B3 First year and last year | From the admin console |
| B4 Count band | Rough, never exact |
| B5 Admin owner | Role, not personal email |
| B6 Retention or deletion setting | As the admin understands it today |
Section C: the links between steps
| Field | What to write |
|---|---|
| C1 Brief to work product | What ties them: a Drive link in the task, a shared code, nothing |
| C2 Work product to acceptance | Whether the accepted file is attached, linked or only described |
| C3 Join key reliability | From 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.
| Field | Value |
|---|---|
| A1 Sponsor | Managing director |
| A2 Service lines | Packaging design and retail display |
| A3 Headcount at peak | 190 full-time |
| A4 Client contracts | Some restrict reuse; counsel holds the list |
| B Asana | Approval tasks for briefs and rounds, 2018 to now, about 6,000, operations manager |
| B Google Drive | Design files and appendices with versions, 2016 to now, about 45,000, IT lead |
| B Gmail | Client acceptance threads, 2016 to now, count unknown, IT lead |
| C1 Brief to work product | Drive link pasted in most approval tasks since 2019 |
| C2 Work product to acceptance | Final file attached when small; linked when large |
| C3 Join key | Job number in the email subject, consistent since 2020 |
| D1 | Is the appendix version the client saw recoverable? Owner: IT lead |
| D2 | Were 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.