How to document a potential confidentiality constraint: a four-level escalation register that records the kind of duty and who can read it, never the secret itself

Short answer

Document a possible constraint as a type, a holder and a next step, never as a description of the confidential thing. One register line says where the duty may come from (a customer contract, an NDA, an employee-privacy promise, a regulator or your fund's own information rights), who at the company can read the governing text, whether the company has approved sharing the line, and one of four escalation levels. Attach no contracts or records: the company and its counsel decide what SourceX hears.

Visual briefFull-size diagram
Four rising steps labeled 1 Note, 2 Counsel reads first, 3 Hold and 4 Stop, each with the kind of situation that puts a constraint there, under the line that the register logs the type of duty, never the secret, and attaches no contracts or records.
The four escalation levels from this page's register. Levels describe how an introduction is handled, not how a rights review will end.

This page is for the portfolio operations analyst who prepares a referral brief for a company the fund knows and spots something that might limit what the company can license. A brief earns attention by being honest about that, not by guessing at it.

Why a careless constraint note can breach the duty it describes

The quickest way to break a confidentiality clause is to describe it in detail to someone outside it. A note such as "their largest customer's master agreement bars reuse of shipment data" names a customer relationship, hints at a contract term and characterizes the records: three things the company may be bound to keep private.

An analyst carries a second duty the company does not. Much of what a fund knows arrives under its own confidentiality terms. The NVCA's model management rights letter, for example, makes confidential information an investor receives under the letter subject to the confidentiality provisions of the Investors' Rights Agreement, and lets the company keep highly sensitive material from the investor's board observer. A constraint you learned about from a board deck is information you hold to monitor the investment, not information you may pass to SourceX. Only the company can tell SourceX.

Your own agreement adds a third layer. The program terms say the signed SourceX Channel Partner Agreement governs confidentiality, and summarize its obligations as lasting three years, longer for trade secrets while they remain legally protected.

The program draws the line from the other side too. SourceX's screening guidance says a company has the rights to license when it owns the material or can license it without breaching client confidentiality, employee privacy or third-party contracts. Whether that holds is settled in SourceX's rights review with the company, not in your brief. Your job is narrower: make sure a possible constraint is neither lost nor exposed.

The minimum context the register sits under

A register line means little without a few company facts around it. Collect only these, each labeled confirmed, estimated or unknown.

Context fieldExample entry (Illustrative)Label
CompanyA 180-person engineering consultancy, legal name as registeredConfirmed
CEO's positionHas agreed to a first call and named the COO as sponsorConfirmed in the CEO's email
Full-time employees at peakAbout 180Estimated by the COO
Operating historyProject files since 2008 in two document systemsEstimated by the COO
Record familiesProject reports, QA checklists, internal method guidesConfirmed at metadata level
Records the fund holdsNoneConfirmed

The constraint escalation register

Each possible constraint gets one line with eight fields. None of them describes the secret.

FieldWhat to writeWhat never goes in it
Constraint typeCustomer contract, NDA, employee privacy, consumer privacy promise, regulator or court, fund information rightsThe clause text
How it surfacedThe COO mentioned it, a board pack, or a public filingThe document itself or a screenshot
Records it may touchA record family at metadata level, such as project reportsSample records or client names
Holder at the companyThe role that can read the governing text, such as general counselPersonal details beyond the role
Sharing approvedYes or no: has the company agreed this line can go to SourceX?Anything the company has not approved
Read byWho has actually read the governing text for this purpose, and whenYour interpretation of it
Level1 to 4, defined belowA forecast of the rights review
Next stepOne action, one owner, one dateAn open-ended "look into it"
LevelNameWhen it appliesWhat happens to the introduction
1NoteSomeone at the company has read the source and says it does not reach the likely recordsProceed; the line travels only if sharing was approved
2Counsel reads firstThe source may reach the records and nobody has read it for this purposeA first call can go ahead if the CEO wants one; company counsel reads before any scope discussion
3HoldThe likely records hold another party's confidential information, or the constraint appears only in fund materialsSubmit nothing until the company raises it itself or decides to go ahead
4StopThe records belong to the company's clients, or a binding order or law bars the useDrop that record family, or the introduction if nothing else remains, and record the reason without detail

Two rules move a line. It moves down only when someone at the company who has read the source says so, never because the analyst reread a summary. It moves up whenever a new fact appears, and anyone can move it up. A constraint that shows up only in fund materials starts at level 3: you cannot raise it with SourceX, and you should not quietly drop it either. Ask the CEO or sponsor whether the company wants to raise the topic in its own words.

A filled register for a 180-person engineering consultancy (Illustrative)

#TypeRecords it may touchHolderSharing approvedRead byLevelNext step
1Customer contractsProject reportsGeneral counselYes, type only, no client namesNot yet2Counsel reads the standard terms before the first call
2NDA with a technology partnerInternal method guidesCEONoCEO, this month1None; the line stays in the fund's file
3Employee privacyQA checklists carrying reviewer namesCOOYesNot yet2The company decides whether names come out before any scope talk
4Fund information rightsReports for one client sectorFund counselNoThe analyst3Ask the CEO whether the company wants to raise it
5Client-owned deliverablesDrawings delivered to clientsGeneral counselYesGeneral counsel4 for that familyLeave the drawings out; the other families continue

What travels to SourceX from this register: lines 1, 3 and 5, in the words the company approved. Line 2 stays behind because the company did not approve sharing it, and line 4 because it came from board materials.

Estimates, constraints and open questions carry different labels

Three kinds of uncertainty sit in a referral brief. Each needs its own label so nobody reads one as another.

  • Estimate. A number with a range and the person who gave it, such as "about 180 full-time at peak, COO's estimate". Never round an estimate up to clear a threshold.
  • Constraint. A register line with a type and a level. "None mentioned" is not "none exists"; write which person was asked and on what date.
  • Open question. The question, its owner and the date asked, such as "Do client contracts allow reuse of project reports? General counsel, asked last week."

One habit protects all three: keep the company's verbs. If the COO said a clause "might" cover project reports, the brief says might. Turning may into does overstates a constraint; turning it into does not hides one. For how use restrictions and survival periods work in practice, see confidentiality clause use restrictions and whether an NDA prevents licensing data for AI training.

The authorized handoff and first-call agenda

The handoff happens after the CEO has said yes and approved the summary. It contains the context table, the approved register lines and the contacts the CEO named. It leaves out contracts, clause text, client names the company did not approve, sample records and anything from board materials.

Before anything is submitted, check the published fit facts: a peak of 50+ full-time employees, contractors not counted; an operating history the company can document; records the company owns or can license; and location. 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. Authority to open a licensing discussion and to sign for the company sits with the CEO; the COO in this example sponsors it. What stays unknown until SourceX reviews the company: whether any constraint actually bars licensing, whether the records match current data needs and what a license would cover.

A first call that respects the register runs in this order:

  1. The CEO confirms the company wants the conversation and names the sponsor.
  2. The sponsor describes the record families at metadata level.
  3. For each approved line at level 2 or above, the holder says whether the governing text has been read, and by whom.
  4. SourceX explains how its rights review works and what it would need from company counsel.
  5. Everyone agrees who owns each open question and when it will be answered.

No submission happens until the submitter has signed the SourceX Channel Partner Agreement; a partner whose signature sits on the earlier version, titled Channel Partner Non-Circumvention and Non-Disclosure Agreement, stays bound by it as signed. SourceX settles credit from dated records once the company submits a verified application, giving it to the earliest valid introduction of the new company inside the 90-day attribution window, so the register's dates do double duty. If a former NDA from a sale process is how you know the company at all, read referring a company you learned about under an NDA first.

Risks and limits of a constraint register

  • It knows only what the company said. Constraints nobody has noticed surface in SourceX's rights review, or later. A clean register is not a clean rights picture.
  • AI developers may look further than you can. NIST's AI Risk Management Framework asks organizations for policies and procedures covering AI risks tied to third parties, including infringement of a third party's intellectual property or other rights (GOVERN 6.1), and NIST's generative AI profile suggests contracts that spell out content ownership and usage rights. A level 1 line can still matter in a licensee's diligence.
  • Over-escalation has a cost. Marking everything level 3 stalls introductions a CEO wanted. Use hold for a specific reason you can name.
  • You are not counsel. The register records who has read what. It never interprets enforceability, survival periods or exceptions.
  • No outcome data. SourceX has not published how often constraints delay or stop introductions, so this page offers no rates; the figures are not yet published. A fund can measure its own: per introduction, the highest level reached, how long each line stayed open and whether the company proceeded.

Methods note. The register's fields and levels were built for this page from SourceX's who-qualifies page and program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the NVCA model management rights letter and NIST's AI RMF materials, all checked 2026-10-27. It records the presence, type, holder and handling of a possible constraint. It does not measure enforceability, how common each constraint type is or the chance that SourceX accepts a company. For the wider portfolio workflow, see the overview for venture platform teams.

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.

With a holder and a level on every register line and the CEO's approval of what travels, sign up on the registration page for your partner link, compare the company with the who qualifies criteria, and read the program terms before you submit; related guides sit in the guides library.

Keeping a portfolio company's constraints straight is referral work; deciding whether SourceX itself merits an investment is a separate question; for that one, request investor materials through the SourceX investor overview.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

  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 I tell SourceX about a constraint I first saw in a board pack?

No. What a fund learns through board or information rights is usually held under confidentiality terms for monitoring the investment. Ask the CEO or the sponsor whether the company wants to raise the topic itself; until it does, the line stays at level 3 in your own file.

Does a confidentiality constraint mean the company cannot be introduced?

Not by itself. A constraint may reach one record family rather than the whole archive, and SourceX's rights review decides what can be licensed. Material that belongs to the company's clients is usually not a fit, so that family drops out; the rest can still be introduced if the CEO wants the conversation.

Where should the register live, and who sees it?

In the fund's own files, open only to the people preparing the introduction. The company keeps its own view of its obligations, and SourceX receives only the lines the CEO approved, in the company's words.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. nvca.org/wp-content/uploads/2019/06/NVCA_Model_Manage…
  4. airc.nist.gov/airmf-resources/airmf/5-sec-core
  5. nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf
  6. sourcex.si/investors

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