# Brief-to-acceptance completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/brief-to-client-acceptance-completeness-checklist
Last updated: 2026-11-04

A brief-to-client-acceptance trail breaks when one of its links cannot be shown: the brief version the team worked from, the exact work product the client saw, the message in which the client accepted it, or the timestamps that put them in order. The most common break is an appendix linked from the approved file that kept changing after sign-off. This scorecard tests six links at metadata level, scores each pass, partial or fail, and tells you what you can honestly say before drafting a brief.

The scorecard belongs to the [client opportunity brief generator](/tools/client-opportunity-brief-generator). The generator drafts an editable brief and introduction email; this page decides which completeness statements those drafts are allowed to make.

## How to run the scorecard

Run it in a short call with the owner or managing partner of the agency or professional-services firm, not with a project coordinator. Ask each question below as written, accept the answer as given, and score it. Do not open any client file, ask for a sample export or request a screenshot. If the owner does not know, score it as a fail and note "unknown"; that is an answer too.

Score each check 2 for pass, 1 for partial and 0 for fail. Six checks give a maximum of 12.

## The six checks

| Check | Question for the owner | How to check at metadata level | Pass (2) | Partial (1) | Fail (0) |
|---|---|---|---|---|---|
| 1. Coverage | "For which years and which share of client projects does the brief-to-acceptance sequence exist in your tools?" | Owner names years and rough share | Most projects across several years | Some years or some service lines | Unknown or a few recent projects |
| 2. Brief versions | "Are client briefs kept with their revision history?" | Owner names where briefs live and whether revisions are kept | Native documents with revision history | Some briefs as uploaded files, versions uncertain | Briefs overwritten or kept only in email |
| 3. Work product attached | "Is the delivered file attached to the approval task, or only linked?" | Owner describes the approval step in the project tool | Attached to an approval task with outcome recorded | Linked, file still exists | No consistent approval step |
| 4. Acceptance names the file | "Do client acceptance messages name the file or task they approve?" | Owner describes a typical acceptance | Usually names the deliverable | Sometimes; often "approved" in a thread | Acceptances are verbal or untraceable |
| 5. Timestamps in order | "Can you tell whether acceptance came before or after the last edit?" | Owner says whether tools record edit and approval times | Both recorded in the tools | One recorded, the other approximate | Approval marked whenever someone remembers |
| 6. Linked files frozen | "Are linked appendices copied, attached or locked at sign-off?" | Owner describes what happens to linked sheets and annexes | Frozen at sign-off as a rule | Frozen for some clients | Linked files keep changing |

Check 6 fails most often. A live spreadsheet linked from an approved report shows today's figures, not the figures the client accepted, and nothing in the approval itself warns anyone that the two differ.

## Why checks 2 and 6 depend on file type

Version history is not uniform, even inside one tool. Google's Drive help says an older version of an uploaded file, such as a PDF or workbook, may be permanently deleted after 30 days or once there are 100 newer versions, unless someone marks it Keep forever. Google's developer documentation adds that this purge applies to binary files, while native Google Docs and Sheets revisions follow different rules. So a firm whose briefs are Google Docs may pass check 2, while a firm uploading PDFs of the same briefs may only reach partial.

The approval side is more consistent where a firm uses one. Asana lets a team mark a task as an approval, attach the files to be approved, assign an approver and record the outcome as Approved, Changes requested or Rejected. Firms that use that step usually pass check 3; firms that approve by email reply rarely do.

## A scored example (Illustrative)

Fictional: a 140-person brand and digital agency with six years of client work across a project tool, a shared drive and email.

| Check | Owner's answer, paraphrased | Score |
|---|---|---|
| 1. Coverage | "Every retained client since 2020; smaller projects are patchy." | 2 |
| 2. Brief versions | "Briefs are shared docs with history; older ones were PDFs." | 1 |
| 3. Work product attached | "Final files go on an approval task, outcome recorded." | 2 |
| 4. Acceptance names the file | "Clients reply to the approval email; most quote the task." | 2 |
| 5. Timestamps in order | "The tool stamps approvals; edits we would have to reconstruct." | 1 |
| 6. Linked files frozen | "Appendices are live sheets. We do not lock them." | 0 |
| Total | Sum of the six scores | 8 of 12 |

What the brief may say: "Six years of retained-client work with approval tasks and named acceptances; brief history partly kept; linked appendices not frozen at sign-off." What it may not say: "complete records," "every version preserved" or anything implying check 6 passed.

## Reading the total, and its limits

| Total | What it suggests | What to put in the brief |
|---|---|---|
| 10-12 | Links are kept as routine | State the checks that passed; note any partial |
| 6-9 | A usable trail with known gaps | Name the gaps plainly, check by check |
| 0-5 | The trail exists only in parts | Describe what exists; make no completeness claim |

The total is a conversation aid, not a grade SourceX uses. It cannot show whether the firm has the rights to license client-related records, whether client contracts restrict use, or whether a buyer would want them. Those are settled in SourceX's own review, after the owner agrees to proceed. A worked trail across the three tools is in [brief-to-client-acceptance records across Asana, Drive and Gmail](/guides/chain-brief-to-client-acceptance), and [what a task export cannot show](/guides/brief-to-client-acceptance-missing-context) covers the context lost outside the project tool.

## Who confirms each answer, and who can authorize the next step

The owner or managing partner can answer most checks; the operations lead or head of delivery can confirm checks 3 and 5, and whoever administers the shared drive can confirm check 2. Only the owner, or partners with authority under the firm's agreement, can authorize a licensing discussion. Client deliverables can carry client rights, so the owner should expect SourceX's rights review to separate the firm's own records from client-owned material.

The firm itself must meet the 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. For the introduction itself, see the [warm introduction brief for a business owner](/resources/a-warm-introduction-brief-for-a-business-owner) and, at a yearly review, the [data opportunity handoff checklist for an annual client review](/resources/a-data-opportunity-handoff-checklist-for-an-annual-client-review). If the owner asks what a fuller review involves, [what is a data audit](/proof/what-is-a-data-audit) explains it.

## 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.

Once the owner has scored the trail and wants to proceed, [register as a partner](/register), check the firm against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send the brief.

## Sources

- https://help.asana.com/s/article/approvals?language=en_US
- https://support.google.com/drive/answer/2409045?hl=en&co=GENIE.Platform%3DDesktop
- https://developers.google.com/workspace/drive/api/guides/manage-revisions
- https://refer.sourcex.si/terms
