# Deliverable acceptance records: who says yes? | SourceX

Canonical: https://refer.sourcex.si/questions/who-can-license-deliverable-acceptance-revisions-records
Last updated: 2026-11-04

The program operations director is the right first contact: they run delivery reviews and know where drafts, acceptance criteria, revision requests and sign-off dates are kept. They sponsor the conversation; they rarely decide it. The yes comes from the CEO, after counsel has read the client contracts, because an accepted deliverable often belongs to the client and a government acceptance carries its own rules. What can be licensed stays open until SourceX's rights review.

This decision tree is part of [why data rights matter](/proof/why-data-rights-matter), which explains how one record splits into the firm's work, the client's terms and personal data. Here the job is practical: walk a contract operations advisor through four forks in one conversation and end with a named signer. The inventory of the records themselves is in the [deliverable acceptance revisions guide](/guides/workflow-deliverable-acceptance-revisions).

## Four forks from the review room to the signer

Each fork is a question you ask out loud. None requires opening a file.

**Fork 1: Who runs acceptance reviews today?**
Ask who chairs the review where a draft meets the client's acceptance criteria and a revision request comes back. In engineering, architecture and government services firms it is usually the program operations director or head of delivery assurance.
- One person across all programs: start there.
- Split by program or business unit: pick the longest-serving lead and note the others as secondary sources.

**Fork 2: Who is the client on most of the work?**
This fork decides which contract terms carry the most weight.
- Federal agencies: the firm works under the Federal Acquisition Regulation. FAR 46.501 treats acceptance as the government's acknowledgment that supplies or services conform with contract quality and quantity requirements, ordinarily evidenced by an acceptance certificate on an inspection or receiving report. The certificate is the government's decision, even when the firm files a copy. Go to counsel before anything else.
- Commercial clients: the master services agreement and each statement of work decide who owns the deliverable and whether review comments are confidential. Go to Fork 3.
- A mix: treat each portfolio separately; the tree runs twice.

**Fork 3: What does the record contain besides the firm's own work?**
Ask, by description only, whether revision logs quote client reviewers, attach the deliverable itself, or include drawings and data the client supplied.
- Mostly internal: QA findings, fix times, revision counts. These are the firm's own work and take the short branch to the signer.
- Client content inside: counsel reads the agreements first. A firm can also choose to keep particular clients out entirely.

**Fork 4: Who can authorize a first discussion about licensing firm records?**
The CEO, often with the COO or managing partner sponsoring the discussion internally.

Then the tree ends at SourceX rights review, which decides scope after the introduction, not before.

## The fork table at a glance

| Fork | Ask | If the answer is A | If the answer is B | Who answers |
|---|---|---|---|---|
| 1. Review owner | Who chairs acceptance reviews? | One director: start there | Several leads: pick one, note the rest | Program operations director |
| 2. Client type | Government or commercial work? | Government: counsel first | Commercial: check client content next | Director, confirmed by contracts |
| 3. Record content | Do logs quote clients or attach deliverables? | Internal only: short path | Client content: counsel reads agreements | Director and quality manager |
| 4. Signer | Who can approve a licensing discussion? | The CEO, once briefed | The CEO, after the COO or managing partner briefs them | Director names them |
| End | What can actually be licensed? | Decided in rights review | Decided in rights review | SourceX, with the firm's counsel |

## Illustrative walk-through: one firm, two branches

**Illustrative and fictional.** A 280-person environmental engineering firm delivers site assessment reports. About 60% of revenue comes from federal agency task orders; the rest from private developers. Eight years of reviews sit in a document control system and a project platform, each with draft versions, revision requests and a final sign-off date.

- **Fork 1.** The program operations director chairs every review and has done so for six years. Sponsor found.
- **Fork 2.** Mixed portfolio, so the tree splits. On the federal side, the director confirms acceptance certificates exist for each task order and that the firm retains its records. FAR 4.703 already requires contractors to make records available for three years after final payment unless a clause says longer, and not to destroy or overwrite computer data during that period, so the federal archive should be intact for recent years, and the director confirms that it is. That says nothing about rights; counsel reads the task orders.
- **Fork 3.** Private developer reports quote site owners and attach their survey data. The internal QA log for both portfolios records only the firm's findings, fix times and reviewer initials.
- **Fork 4.** The COO owns the delivery operation and agrees to bring the CEO to a first call. General counsel will read the federal task orders and the three largest developer agreements before any scope is proposed.

What the partner wrote down: record types, two systems, eight years, the split by client type, three names. Nothing else.

## Where the tree stops and SourceX's rights review starts

Some branches cannot be closed in a first meeting, and saying so is part of a credible introduction.

- **Government data clauses.** Whether a task order restricts reuse of deliverables, review comments or technical data is a legal reading of each contract.
- **Promises already made.** A firm cannot quietly widen what it promised clients after the fact. FTC staff have warned that adopting more permissive data practices, such as AI training, through a surreptitious, retroactive change to terms may be unfair or deceptive. The review works from the promises as made.
- **Personal data.** Client reviewers' names and comments are usually removed or de-identified.
- **Demand and terms.** Whether these records match current dataset demand, what survives redaction and whether any offer follows are unknown until SourceX reviews them.

SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. The partner's part ends at an authorized introduction; the [client-owned vs company-owned data](/resources/client-owned-data-vs-company-owned-data) page shows how that line is usually drawn.

## Before you send the introduction

Three checks, all answerable without seeing a record:

1. **Sponsor confirmed.** The director has described the trail (systems, years, rough reviews per year) and agreed to raise it internally.
2. **Signer named.** The CEO has agreed to a first call, or the sponsor will ask this week.
3. **Firm fits.** At least 50 full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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.

Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. If a firm abstracts leases rather than delivering reports, the [lease abstraction corrections tree](/questions/who-can-license-lease-abstraction-corrections-records) follows the same logic with different owners. For other structures, see [finding the right decision-maker](/guides/how-to-find-the-right-decision-maker-for-a-data-partnership); consultants who sit close to delivery teams will find more on the [management consultants page](/for/management-consultants).

## 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 tree ends at the CEO and the CEO will take the call, [register as a partner](/register), confirm the firm against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce them.

## Sources

- https://www.acquisition.gov/far/46.501
- https://www.acquisition.gov/far/4.703
- https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/02/ai-other-companies-quietly-changing-your-terms-service-could-be-unfair-or-deceptive
- https://refer.sourcex.si/terms
