The request usually comes from trust, not carelessness. You know the systems better than anyone at the client, so it feels natural to ask you to "just confirm it". The kind answer is a short refusal that hands each question to the person who can actually answer it.
Five ways the request reaches a consultant
Certification requests rarely say "certify". They arrive inside ordinary project work, often from a person who is sponsoring the licensing idea internally but cannot authorize it.
| How it is phrased | Who usually asks | What it really asks you to vouch for |
|---|---|---|
| "Can you write a line saying all of this is ours?" | The CFO or controller filling in an application | Ownership and the right to license |
| "Confirm there's no customer data in the helpdesk." | The operations director who owns the system | The content of records you were never asked to review |
| "You'd know if this was ever sold before, right?" | The CEO, wanting comfort before a call | That the records were never licensed for AI training |
| "Sign off that the export is anonymized." | A project lead after a migration | A de-identification result |
| "Be our technical reference for SourceX." | Anyone at the client | That you will answer for the company in its own deal |
The system event behind each one is familiar: a migration that put every year of history on one screen, a retirement that forces a decision about an archive, a retention review that surfaced a decade of tickets. The person asking is often the right internal sponsor for the idea. The CEO is still the one who decides whether the company discusses licensing, and the one who signs for it.
Why SourceX does not ask for your signature
Nothing in SourceX's process needs a statement from the company's IT provider. The trust center describes the rights review this way: "We review whether the supplier owns the original records and can license them, including any customer or vendor contract limits. The supplier confirms its rights in the agreement." The company, not its consultant, gives those confirmations. SourceX's process page lists what the company confirms: that it holds the rights to license the data, that personal data was collected lawfully, that the data has not been licensed for AI training before, and that it was not created or altered with AI for the sale.
SourceX itself stops short of legal judgment. Its FAQ says it asks structured questions about where data came from and which contracts or policies apply, that it does not give legal advice, and that a company should bring in its own counsel wherever something is uncertain. It also warns that owning records does not automatically allow a company to license personal information or material that belongs to customers, vendors or other third parties. If the licensor does not offer a legal verdict, a technician signing one has stepped well past the job.
Your referral role adds no authority either. Section 7.1 of the unsigned Channel Partner Agreement sample says a partner is not SourceX's agent and cannot commit it to prices, licenses or payouts, section 7.2 says supplier agreements grant the partner no data rights, and section 4.2 gives the partner no authority to share a supplier's records or reach its extraction systems.
Security vocabulary keeps the two roles apart as well. NIST's glossary describes an information owner as the official with statutory or operational authority over specified information, responsible for the controls on how it is created, processed, shared and disposed of (a paraphrase). An administrator account carries none of that authority.
The scope refusal and expert handoff template
The template has two parts: a refusal short enough to send the same day, and a handoff table that names who answers each claim. The wording is Illustrative; keep the substance and use your own voice.
Part A: the refusal.
Thank you for trusting us with this. We can't sign a statement about who owns your records, whether you may license them, what they contain or whether they have been licensed before. Our access lets us run your systems; it doesn't make us the people who can answer those questions, and SourceX's process doesn't call for a statement from us. SourceX asks the company to confirm those points in its own agreement, after its rights review. Here is who can answer each one, and we're glad to tell you anything about how the systems themselves are set up.
Part B: the handoff table.
| Claim in the request | Who makes it | Where it is settled | What you can still contribute, to the client only |
|---|---|---|---|
| "The company owns these records" | The company, through its CEO | The company's signed agreement with SourceX, after SourceX's rights review | Which system holds them and since when, as a fact about your service |
| "No customer or third-party material is inside" | The company's records owner, with counsel reading customer and vendor contracts | SourceX's rights review, which looks at contract limits | Nothing: answering would mean reading content you have no reason to open |
| "Never licensed for AI training" | The CEO, from the company's own contract history | The confirmations in the company's agreement | Nothing: you do not see the company's contracts |
| "Personal data is removed" | No one, before a deal | SourceX de-identifies through approved processing routes after the go-ahead, and says no method is perfect | Nothing: the step has not happened yet |
| "Full-time headcount peaked at 50 or more" | Payroll or HR, with contractors excluded | The company's own application | Nothing: user counts are not employees |
| "The company may enter a licensing discussion" | The CEO | The CEO's own yes, then the company's application | Telling the sponsor that the CEO decides |
Send Part A with the rows that match the request, and stop there.
Method note. The template was built on 2026-10-27 from SourceX's trust center, process page and FAQ, the unsigned partner agreement sample (version 2026-10-19), program terms version 2026-10-22.2, since replaced by version 2026-11-04 and the NIST glossary entry above. It assumes a consultant whose service agreement says nothing about licensing. It is not legal advice: if your contract or a professional code imposes stricter duties, they govern.
What a custodian may write down, and for whom
The useful test is not "is it true?" but "whose statement is it?" Some sentences are facts about your own service. Others are claims only the company can make, and a few are decisions only SourceX makes.
| Sentence | Whose statement | Can you write it? |
|---|---|---|
| "Your helpdesk has been in service since 2013." | Yours, as a fact about the service you run | Yes, to the client, as part of your normal work |
| "The 2013 to 2019 tickets sit in a read-only archive." | Yours, about configuration | Yes, to the client |
| "The company owns the tickets and may license them." | The company's | No |
| "The tickets contain no personal data." | Nobody's yet | No |
| "These records fit a current SourceX program." | SourceX's, after review | No |
| "The company qualifies." | SourceX's, after review | No |
Facts in the first two rows still go to the client, never to SourceX. If the company wants to repeat them in its own application, it restates them in its own words. Partners never see, upload or handle a company's records, inventory or data room, and a certification letter is just another way of handling them.
A rights letter that stayed unsigned (Illustrative)
Illustrative. The company and people are fictional, and no outcome is implied.
A 280-person HVAC parts distributor is retiring an on-premises ERP. Its CFO reads about data licensing and asks the MSP running the migration to sign a one-paragraph letter: the company owns everything in the ERP and the helpdesk, and none of it belongs to customers.
The account lead sends Part A that afternoon with three rows: ownership to the CEO, customer material to the records owner and counsel, and "never licensed" to the CEO. She adds one service fact the CFO had asked about: the helpdesk went live in 2013.
The CFO takes the idea to the CEO, who emails the account lead a week later asking to be introduced. The account lead mentions that SourceX may pay her firm a reward if a license closes, checks that nobody at the distributor has already contacted SourceX, signs the partner agreement and submits the introduction. The company applies with its own description of its systems. Counsel reads the dealer agreements before anything is signed, because some dealer-submitted warranty claims may carry contract limits.
Suppose SourceX later paid the distributor $160,000 under its Dataset Deal Confirmation. The reward would be the greater of $50,000 plus 5% and 15% of that, $40,000, paid by SourceX on its own account once every payment condition in the terms was met; none of it would come out of the distributor's agreed compensation. The figures are invented, and SourceX does not publish how it prices offers. The letter was never signed, and nothing in the deal needed it.
Introduce the owner without vouching for anything
Once the CEO says yes in writing, the introduction is short and makes no claims at all.
- It names the company, the CEO and the fact that the CEO asked to be introduced.
- It discloses your interest: SourceX may pay your firm a reward, from its own funds, if a license closes.
- It leaves out every statement from the handoff table: ownership, contents, licensing history, de-identification, headcount and fit. The company makes those itself.
- It comes after two checks: you have signed the SourceX Channel Partner Agreement, and nobody at the company has an earlier application, lead, account or email thread with SourceX. A company SourceX already knows is reviewed as a duplicate and is not credited to anyone new.
Fit facts are worth one conversation with the CEO, not a document: a full-time headcount of 50 or more at its peak, contractors excluded; years of records the company created itself; rights to license them; and a CEO who wants the talk. If the client was acquired, the acquirer's CEO now decides. When the CEO's real worry is legal, the guide on a client who wants a lawyer first covers that conversation, and what happens after a founder says they own the data follows the claim through review.
Where the refusal gets harder
- A long-standing client who presses. The answer stays the same. Offer the service facts generously and keep the claims with the company.
- Your own contract. Audit or cooperation clauses may oblige you to produce your own records for the client. That is service work for the client, and your own counsel can say how far it reaches; nothing here is legal advice.
- Your own data. Licensing your firm's own ticket history would make you a supplier, not a referrer, and your customer contracts decide which of those records are yours.
- A former client after a sale. Whoever certifies nothing still needs the right decision maker, and after closing that is the acquirer's CEO.
- No published data. Nobody has measured how often clients ask consultants to vouch for ownership or how they react to a refusal. Log each request, the rows you sent and whether the CEO later asked for an introduction.
For the neighboring situations, see when a client wants the consultant to upload everything, how to ask about ownership without creating a diligence project and keeping ownership of data when licensing. The partner overview is on the managed service providers page, and more technology playbooks are in the guides library.
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 request for your signature has turned into a CEO asking for an introduction, register as a partner, recheck the company against who qualifies and read the program terms, then send an introduction that vouches for nothing.