The professional referral audit trail without excess client detail: a nine-event decision register that records what was decided, when, by whom and with what outcome, points to where the proof already sits, and copies no client fact into the trail

Short answer

Keep a record of decisions, not of the client. Each line in a professional referral audit trail should say what was decided, when, by whom and with what outcome, and then point to where the proof already lives inside the firm's own systems: a conflicts entry, counsel's memo, the CEO's email. It should never copy the client's facts, files or the reasons behind a confidential judgment. Log declines and decisions to stay out as carefully as introductions that go ahead.

Visual briefFull-size diagram
A register sheet with five filled columns, event, date, decided by, outcome and pointer, beside a sixth column of client facts struck through; arrows from the pointer column run out to three boxes labeled conflicts system, counsel's memo and the CEO's email, under a caption reading proof stays where it is.
Illustrative register. Column names follow the table on this page; no real firm, client or record.

This page gives no legal advice and describes no retention rule. It is a design for the register, written for a law firm alliance manager or a compliance lead at a regulated advisory firm who keeps it on the firm's behalf.

Who keeps the trail, and which decisions it covers

One person keeps it, usually whoever owns the firm's participation decision. It covers every occasion on which someone in the firm considered telling a company's CEO about SourceX, including the occasions that went nowhere. The proposed activity is the same throughout: a person mentions SourceX to a CEO and, if the CEO wants the conversation, either submits an introduction as a registered partner or lets the company apply with no partner named.

The trail exists for a later reader who was not in the room. That reader might be the firm's general counsel, an examiner, a client who asks why the firm raised the subject, or SourceX reviewing a disputed credit. Every one of them wants the same thing: the sequence of decisions and who made each one. None of them needs the client's records to get it, and the trail that holds them becomes a second copy of confidential material with weaker protection than the original.

What SourceX already records, so the firm does not duplicate it

Part of the trail already exists on SourceX's side. Section 3.3 of the sample Channel Partner Agreement says: "Each introduction record must identify the company, domain, Partner, opportunity, introduction method and timestamps." Schedule A, paragraph 8, adds that "SourceX retains dated introduction evidence, linked deal and inventory references, attribution decisions, supplier payout calculations, cap usage and payment status." Section 2 of the program terms decides credit from dated records, including written introduction evidence, and only one partner is credited per company.

So the firm's register does not need to describe the company or the opportunity again. It needs enough to match SourceX's record on two points, the date and the introduction method, and to show the firm's own decisions that SourceX never sees: the conflicts check, the compensation review and the route counsel approved. Updates from SourceX arrive in a deliberately thin form; section 4.6 says a partner receives what it reasonably needs "using generic stages or reference codes." Copy the stage word and the code, nothing more.

Six questions every audit record answers

Security engineers solved the shape of an audit record long ago, and the shape transfers well. NIST's control catalog, in paraphrase of its AU-3 control (Content of Audit Records), asks each record to establish what type of event occurred, when, where, its source, its outcome and the identity of the people or entities involved. The same catalog carries an enhancement titled Limit Personally Identifiable Information Elements, and NIST's guidance notes that logging can itself involve processing personal information, with privacy risks of its own.

Applied to referrals, those six elements become columns, and the limit becomes a seventh column that says what each line must never contain. The register below is that translation. It is this page's design, not a NIST requirement and not a SourceX rule.

The minimal decision evidence register

#EventDecided byOutcome recordedPointer to proofNever written in this line
1Idea raisedNobody yetSource type: public, the CEO said it, or a matter; a matter source ends the trail hereThe CEO's own message, if there is oneWhat a file, data room or board pack showed
2Conflict check runThe firm's conflicts functionClear, issue found or blockedConflicts entry numberNames or relationships beyond what the conflicts system already holds
3Route reviewedEthics counsel, or the employer's compliance functionPaid referral, unpaid introduction or no partMemo or reply reference and dateCounsel's reasoning
4CEO askedThe CEOYes, later or noMessage reference in the introducer's mailboxAnything the CEO said beyond the answer
5Fit facts confirmedThe CEOEach published fact marked confirmed or not statedSame message reference as row 4The figures, system names or record descriptions
6Agreement signedThe signing partySigned as an individual or as the firmPartner portal recordBank or tax details
7Introduction submittedThe registered partnerSubmitted, with date, time and methodSourceX's submission referenceAttachments of any kind
8Status receivedSourceXThe stage word as SourceX sent itSourceX's reference codeGuesses about the outcome
9Trail closedThe register keeperReason: CEO declined, no part, not credited, completed or stoppedRetention date under the firm's policyWhy a confidential judgment went the way it did

Each line has a date, a channel (meeting, call, email or portal) and the name of the person who raised the event; they are left out of the table only for width. Two habits make the register work. First, a pointer names a system and a record number, never the record's content; if the pointer would itself reveal a client fact, counsel decides what replaces it. Second, rows 6 to 8 exist only on a paid route. The sample agreement names the Partner as "an individual, or entity type and jurisdiction", so row 6 records which kind of party signed.

Three trails, three endings (Illustrative)

Illustrative. Generic firms and companies, invented dates, no outcome implied.

RowTrail A: paid referralTrail B: unpaid introductionTrail C: no part
13 March, the CEO raised AI data at a lunch9 April, public news of a system change2 May, seen in a diligence data room
24 March, clear10 April, clearNot run
318 March, paid route, counsel memo ref. 11415 April, unpaid only, employer replyNot run
420 March, yes16 April, yes; the company will apply itselfNot asked
520 March, all facts confirmedNot recorded; no partner namedNot recorded
6 to 8Signed as the firm 21 March; submitted 24 March; stage word received 2 AprilNot applicableNot applicable
9Open16 April, closed: no partner named2 May, closed: matter source, no part

Trail C is the shortest and the most important. A matter source stops the trail at row 1, and the closing line records only that fact and its date. Nobody writes down what the data room held. Trail B shows that an unpaid introduction leaves almost nothing to log once the company applies on its own.

Confidentiality, conflict and compensation questions about the register itself

The register is a record about clients, and the firm's ethics counsel should settle four questions before the first line is written:

  • Is the register client information? If counsel says yes, it inherits the firm's protections for client material, and its access list shrinks.
  • Could a line reveal a conflict? Row 2 points to the conflicts system for this reason. If the register sits outside that system, it should hold no more than the outcome.
  • Do pointers to counsel's memos put privilege at risk? Counsel decides how row 3 references its own advice, or whether it does at all.
  • How long is it kept, and who deletes it? Row 9 takes the retention date from the firm's records policy, not from this page.

Compensation needs one more line of discipline. Whether a person or the firm may be paid is decided in row 3 and nowhere else. Section 5 of the terms is the reason the register never records an expected reward: "A lead, meeting or signed agreement alone does not earn a payable reward." When a constraint on a company's records surfaces along the way, it belongs in a separate, type-only note of the kind described in documenting a potential confidentiality constraint, not in this trail.

Fit facts belong in the CEO's message, not the register

Row 5 records confirmation, not content. SourceX's who-qualifies page screens for a company that reached 50 or more full-time employees at its peak, with contractors left out, holds years of records it created itself, has the rights to license them, and has a CEO who agrees to the discussion. 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.

The page says the screening questions are answered from a conversation, never from files, samples or logins, and the register follows the same rule. What the records are worth to a current program, what a license would cover and whether customer contracts restrict reuse stay unknown until SourceX reviews the company. The register never guesses at them. Privilege-specific leaks, such as a matter note slipping into an introduction, are covered by the privilege-preserving introduction checklist, and the habits a team needs before anyone writes a line are taught in the compliance training session plan.

When a lean trail is not enough

  • Disputes need originals. Section 3.3 of the sample agreement says "A dispute must not erase original evidence or authorize disclosure of another partner's confidential information." The register points to originals; it never replaces them, so the originals must survive.
  • Some reviewers will ask for more. A regulator or court may want what the register deliberately leaves out. That request goes to counsel, who retrieves it from where it lives.
  • Pointers break. Mailboxes are archived and systems migrate. Record the system's name with each pointer and check the links when the firm changes tools.
  • People leave. A trail kept in one person's inbox ends when they do. Keep it in a firm system with a named successor.
  • It cannot prove a negative. The register shows decisions that were logged. A conversation nobody recorded is simply absent, which is why the training matters as much as the template.

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 row 3 of a trail reads paid route and row 4 reads yes, the signing party can register, compare the CEO's confirmed facts with who qualifies and file the program terms version beside the trail it governs.

  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

Why log a decision to stay out if no introduction was ever made?

Because the question someone asks later is usually why the firm did nothing, and a dated line showing who decided, on what route and when answers it without reopening the client file. A missing line is what invites the reopening.

Can the register hold the numbers the CEO gave us, such as headcount at peak?

It does not need to. Record that each published fit fact was confirmed by the CEO, with the date and a pointer to the CEO's own message. The figures stay in that message, under whatever protection the firm already gives client correspondence.

Who should be able to read the register?

As few people as the firm's ethics counsel allows, typically the person who keeps it, the introducer for their own lines and the compliance or ethics function. Counsel also decides whether the register itself is treated as client information.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r…
  4. refer.sourcex.si/who-qualifies

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