Leadership and readiness
Data licensing pilot decision memo: approve a small pilot with limits
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Approve a small data pilot with a one-page decision memo signed by a single named decision owner. The memo fixes the records, counterparty, permitted use and end date; names an evidence owner for each concern such as privacy, contracts and security; lists events that end the pilot automatically; and records open questions with owners and consequences. Any expansion needs a new decision.
Provenance trail
Data licensing pilot
Key takeaways
- One named person decides; data, privacy, security, counsel and customer owners supply signed evidence.
- Confirm the decision owner's authority in bylaws, delegations and investor agreements before signing.
- Write expiry conditions as triggers with actions, so the pilot stops without another meeting.
- Check what customers were promised before scope is final; a pilot is still a disclosure.
- Track open questions in a register with an owner, the resolving evidence and a pre-agreed consequence.
How should a company approve a small data pilot with explicit limits?
Approve it in one short decision memo signed by a single named decision owner. The memo fixes what may be shared, with whom, for what use and until when; names an evidence owner for every approval concern; lists the conditions that end the pilot automatically; and says who decides if something unexpected comes up. If the memo cannot be written that precisely, the pilot is not ready to approve.
A data licensing pilot decision memo is different from a board resolution or a full license. It authorizes a bounded experiment: one dataset slice, one counterparty, one permitted use, a fixed end date. Its job is to let leadership say yes quickly without saying yes to more than it meant. The memo also becomes the record a later reviewer reads to understand why the company shared what it shared.
The failure the memo prevents is drift. Pilots that begin with a verbal yes tend to grow: a second system gets added, a buyer asks for one more year of history, the end date passes while everyone is busy. Writing limits and expiry conditions down at approval time means any expansion needs a new decision rather than a favor.
Who signs the memo, and who only supplies evidence?
One person decides; several people supply evidence. Name the decision owner by role and person, and confirm they actually hold the authority. For a Delaware corporation, section 141(a) of the General Corporation Law says the business and affairs of the corporation are managed by or under the direction of the board, except as the statute or the certificate of incorporation provides otherwise. In practice boards delegate day-to-day contracting to officers, so the question is whether your delegation of authority, bylaws or investor agreements reserve this kind of decision.
Evidence owners answer specific questions and sign their part; they do not approve the pilot. Typical owners are the data owner for what the records contain, privacy for personal information, security for the transfer method, counsel for contracts and rights, the customer-relationship lead for what customers were told, and finance for any consideration received.
This split mirrors guidance companies already use for AI governance. The NIST AI Risk Management Framework's GOVERN 2.1 asks that roles, responsibilities and lines of communication for mapping, measuring and managing AI risks are documented and clear to individuals and teams. A pilot memo is a small, concrete instance of that: every concern has a named person, and everyone can see who decides.
The pilot approval memo and expiry conditions
Use these fields as the memo template. Each row says what to write, who owns the evidence and what makes the field fail, which is the signal not to sign yet.
| Memo field | What to write | Evidence owner | Not ready if |
|---|---|---|---|
| Decision owner | Name, role and the authority relied on | Counsel | Authority is assumed rather than located in bylaws or a delegation |
| Purpose | The one question the pilot answers for the company | Decision owner | Purpose is to see what happens |
| Records in scope | System, record types, date range, maximum record count | Data owner | Scope is described as a system rather than a defined slice |
| Records excluded | Customers, fields and record types left out, with the reason | Data owner and customer-relationship lead | No exclusions have been checked |
| Counterparty and use | The buyer, the permitted use and uses expressly not permitted | Counsel | Use is described as AI purposes |
| Privacy treatment | De-identification approach and residual personal information | Privacy lead | Personal information status is unknown |
| Transfer and access | Channel, named recipients, access end date | Security lead | Recipients are a team rather than named people |
| Expiry conditions | End date plus the automatic stop events in the next section | Decision owner | There is no end date |
| End-state actions | Deletion or return, certificate due date, what the buyer may keep | Security lead and counsel | No one owns closing the pilot |
| Escalation path | Who decides an issue the memo did not foresee, and by when | Decision owner | Issues default to whoever notices them |
Which events should end the pilot without another meeting?
Expiry conditions should be events that end the pilot by themselves, so stopping does not depend on someone calling a meeting. Write them as triggers, each with the action that follows.
Enforcement on the technical side can be automatic too. NIST SP 800-53, for example, includes a control enhancement for automatically removing or disabling temporary accounts after a set period, which is exactly how pilot credentials should behave. For the end-state record, NIST SP 800-88 Revision 2 says a certificate should be completed for each item sanitized, in paper or electronic form; ask the buyer for an equivalent record of what it deleted.
- The end date arrives. Access closes, the buyer deletes or returns the data and the certificate is due within the period the memo sets. Extending requires a new signed memo.
- The record cap is reached. No further deliveries, even if the date has not passed.
- A customer objects, or a review finds a contract term that restricts its records. That customer's records are withdrawn and the evidence owner reports what was already shared.
- Personal information is found in delivered records beyond what the privacy treatment allowed. Deliveries pause until privacy review is complete.
- The buyer changes control, or asks to share the data with an affiliate or contractor not named in the memo. The pilot pauses for a new decision.
- The buyer uses the data outside the permitted use. The pilot ends and counsel takes over.
What have you already promised customers about these records?
Check customer expectations before scope is final, because a pilot is still a disclosure. Read the privacy notice, customer agreements, terms of service and any data processing agreements that cover the records, and record in the memo what each one allows.
Changing those promises after the fact is risky. The FTC has said it may be unfair or deceptive for a company to adopt more permissive data practices, such as sharing data with third parties or using it for AI training, and to tell consumers only through a surreptitious, retroactive amendment to its terms or privacy policy. A pilot should fit the commitments in force when the data was collected, or wait.
For records with personal information, privacy law adds its own tests. Under the GDPR, personal data must be collected for specified, explicit and legitimate purposes and not further processed in a manner incompatible with them, and Article 35 requires a data protection impact assessment where processing is likely to result in a high risk to individuals. Under California's CCPA, selling is defined broadly to include making personal information available to a third party for monetary or other valuable consideration, so a pilot that exchanges personal information for payment or other value needs that analysis even when the amount is small.
Keep four questions apart in the memo: whether the company can technically access and export the records, whether privacy rules permit sharing them, whether the company owns or controls them, and whether any contract restricts licensing them. De-identification helps with the second question only; it does not create the right to license.
Who owns each unresolved approval question, and what evidence would close it?
Most pilot memos go to signature with a few questions still open. That is acceptable only if each open question has an owner, the evidence that would resolve it and a consequence written in advance. Track them in a register attached to the memo.
Review the register on a fixed rhythm, weekly for a short pilot, with the decision owner present. An item whose date passes moves to its pre-agreed consequence without debate, and the owner records the outcome next to the question. That habit matters more than the format: a register that nobody reads becomes a list of risks the company accepted without deciding to. When the pilot closes, the register and its outcomes go into the same file as the memo and the deletion record, so anyone reviewing a later license can see which questions the pilot settled and which it left open.
| Open question | Owner | Evidence that resolves it | If unresolved by the date |
|---|---|---|---|
| Does any customer contract restrict sharing its records? | Counsel | Review of the contracts for customers in scope, listed by customer | Those customers' records are excluded |
| Does the slice contain personal information after preparation? | Privacy lead | Sample review results and a description of the method | No delivery until resolved |
| Do investor or lender agreements require consent? | Counsel | Consent provisions located and read | Pilot waits for consent or a no-consent finding |
| Is the buyer's permitted use specific enough to enforce? | Counsel | Use clause wording agreed with the buyer | Pilot is not signed |
| Can the buyer delete everything it receives, including backups? | Security lead | Buyer's written deletion method and backup rotation | Data is delivered only into a workspace the company controls |
Worked example (illustrative): a building services company approves a 90-day pilot
This example is illustrative and invented. A building services company with about 300 staff is asked by an AI developer to pilot two years of de-identified work orders from its field-service system. The chief operating officer is the decision owner under the company's delegation of authority, which lets officers approve non-exclusive data agreements under one year.
The memo limits scope to 25,000 work orders from two regions, excludes free-text notes and photos, permits evaluation only, names three recipients at the buyer and sets a 90-day end date with a certificate due 10 days later. Four evidence owners sign their rows. The register holds two open questions: whether any facilities-management client contract restricts sharing, and whether the buyer can purge backups.
The exception arrives in week two. Counsel finds that one national client's master agreement prohibits disclosure of its service data to third parties for any purpose. Under the memo's trigger, that client's records, roughly 1,800 work orders, are withdrawn before delivery, and the memo is amended with a note rather than reopened. The pilot proceeds on the remaining records and closes on day 90 with a deletion certificate filed alongside the memo.
The limit of the example is the delegation itself. A company whose bylaws or investor agreements reserve data agreements to the board would need a resolution, and the memo would become the evidence pack that supports it.
When is a memo not enough?
A signed memo is the right instrument for a bounded test. It is the wrong one when the decision is no longer small, and the memo should say so in its escalation path.
- Board or investor approval is reserved for data transactions, sales of assets or material contracts. Prepare a resolution or consent instead, using the memo as the briefing.
- The records include sensitive categories, such as health, financial account or biometric data. Specialist privacy review comes first.
- A customer prohibition affects most of the records in scope. Narrow the pilot to a slice without the restriction, or stop.
- The buyer asks for training rights, exclusivity or a term beyond the pilot. That is a license negotiation, not a pilot extension.
- Nobody can say who the decision owner is. Stop until authority is located; a pilot approved by the wrong person is the hardest kind to unwind.
How does a pilot memo fit a license through SourceX?
Licensing through SourceX puts the company's signature on scope and terms ahead of any delivery, and keeps every use, sublicense or distribution of the de-identified dataset within that agreement's limits. A pilot memo prepared internally gives the decision owner the evidence needed to approve that scope with confidence.
Sourcing and qualification, rights review, contracting, data preparation and delivery are the stages SourceX covers. It opens with a short company assessment, so learning whether the company qualifies does not require uploading data.
Frequently asked questions
Does a small data pilot need board approval?
It depends on your bylaws, delegation of authority and investor agreements. Many companies let officers approve bounded agreements, but some reserve data transactions or material contracts to the board or to investors, so locate the authority before signing.
What is the difference between a pilot memo and a data license?
The memo is an internal decision record that authorizes a bounded test and sets its limits. The license is the contract with the buyer. The memo should be approved first and the license should match it, not exceed it.
How long should a data licensing pilot run?
Long enough to answer the one question in the memo, usually measured in weeks or a few months. The end date matters more than the length, because a pilot without one tends to become an unpriced, unreviewed license.
Can a pilot use records that contain personal information?
Only after a privacy review of what remains after preparation and of what notices and contracts allow. Where personal information is shared for value, laws such as the GDPR and the CCPA can apply even to a small test.
What happens to the data when the pilot ends?
The memo should say: typically deletion or return with a certificate by a fixed date, plus a list of any outputs the buyer may keep, such as aggregate evaluation results with no records in them.
Sources
- Delaware General Corporation Law section 141(a) provides that a corporation's business and affairs are managed by or under the direction of its board, except as the statute or certificate of incorporation provides otherwise. Source
- NIST AI RMF 1.0 GOVERN 2.1 states that roles, responsibilities and lines of communication for mapping, measuring and managing AI risks are documented and clear across the organization. Source
- The FTC said it may be unfair or deceptive to adopt more permissive data practices, such as third-party sharing or AI training, and inform consumers only through a surreptitious, retroactive amendment. Source
- The GDPR requires personal data to be collected for specified, explicit and legitimate purposes and not further processed incompatibly (Article 5(1)(b)), and requires a DPIA where processing is likely to result in a high risk (Article 35). Source
- The CCPA defines selling to include making a consumer's personal information available to a third party for monetary or other valuable consideration. Source
- NIST SP 800-53 Rev. 5 control enhancement AC-2(2) covers automatically removing or disabling temporary and emergency accounts after a defined period. Source
- NIST SP 800-88 Rev. 2 says a certificate of sanitization should be completed for each item sanitized and may be a paper or electronic record. Source
See if your company qualifies
A short company assessment. No data uploads are needed.