# Procurement decision data referral: origin screen | SourceX

Canonical: https://refer.sourcex.si/guides/procurement-decision-records-avoid-confusing-client-and-company-content
Last updated: 2026-11-04

A company's procurement decision records can support an introduction when its own buyers wrote the reasoning behind its own purchases: the need, the evaluation, the negotiation and the award. Two kinds of material get mistaken for that. Bids, quotes and price files were written by suppliers, and sourcing a company ran on behalf of clients records the clients' decisions even when it sits in the company's platform. Screen every document at two gates, whose purchase and whose pen, before anyone puts the idea to the CEO.

This page is for specialists who handle sourcing files for a living: procurement and sourcing consultants, purchase-to-pay implementers, group purchasing and procurement outsourcing operators, and category managers who now advise. The confusion it guards against is a natural one. You worked inside the files, you know the evaluation notes are excellent, and it is easy to forget that excellent notes may record somebody else's purchase.

## What a procurement decision record holds

A sourcing decision leaves a trail: a requisition or business case, a sourcing plan, the request for quotation or proposal, the supplier list, the bids, clarification questions and answers, an evaluation scorecard with evaluators' comments, a negotiation record, an award approval, the contract and, later, supplier performance reviews. Debriefs to unsuccessful bidders sometimes close it.

The fullest public list of such a file comes from U.S. federal purchasing. FAR 4.803 sets out the records "normally contained, if applicable" in a government contract file, and its list for the contracting office includes "(13) Source selection documentation." alongside each offer received, the record of negotiation and the notice to unsuccessful offerors with any debriefing record. A private company's files are less formal, but the same layers usually appear. Those layers do not share an author, and that is the whole difficulty.

## Gate one: whose purchase was it?

Start with the decision, not the document. A company buying for itself, whether raw materials, freight, software or facilities services, owns the reasoning behind its own choices, subject to the contracts it signed. A company buying for someone else does not, however much of the work its people did. That second group is larger than it looks:

- group purchasing organizations and procurement outsourcing firms running sourcing events for members or clients;
- facilities managers buying services for clients' sites;
- general contractors and construction managers buying subcontracts for an owner's project;
- agencies buying media or production on clients' budgets;
- consultancies whose engagement files record clients' sourcing decisions.

For these firms, the records of client purchases are client content, and SourceX's screening page lists material that belongs to a company's clients rather than the company as usually not a fit. What such a firm may own is its method: category playbooks, templates, internal training and its own overhead purchasing. Whether anything beyond that is its own depends on its client agreements, which counsel reads.

## Gate two: whose pen wrote each document?

Inside a purchase that passed gate one, documents still come from different authors. Company staff write the requirement, the evaluation notes, the negotiation record and the award rationale. Suppliers write bids, proposals, price sheets and answers to clarification questions. Third parties supply market price indices, analyst research and benchmark data under their own subscription terms.

Federal rules show plainly whose a bid is. FAR 3.104-4 bars disclosing contractor bid or proposal information, or source selection information, to anyone not authorized to receive it, and makes clear that it does not stop a contractor from disclosing its own bid or proposal information. The protection runs to the bidder. Private requests for proposals usually carry their own confidentiality terms, and those are what counsel reads for a private company.

SourceX's own buyer-side guidance on third-party material compresses the principle into five words: "A supplier can grant what it holds." For a procurement archive, that means the company can discuss its own evaluation and decision records, while suppliers' documents in the same files are listed separately for SourceX's rights review.

## The procurement content-origin screening

The screening sorts the usual documents twice: once for a purchase the company made for itself, once for a purchase it ran for a client. There are four outcomes. Company means its own work about its own decision; Supplier means written by a bidder or vendor; Third party means licensed from a data or research provider; Client means a record of the client's decision.

| Document | Usually written by | Company's own purchase | Purchase run for a client |
|---|---|---|---|
| Requisition and business case | Company staff | Company | Client |
| Sourcing plan or category strategy | Company buyers | Company | Client, unless it is the firm's generic playbook |
| Request for quotation or proposal | Company buyers | Company | Client |
| Bids, proposals and price sheets | Suppliers | Supplier | Supplier, inside a client's file |
| Clarification questions and answers | Both sides | Company for the questions, Supplier for the answers | Client and Supplier |
| Evaluation scorecard and evaluator notes | Company evaluators | Company | Client |
| Negotiation record | Company negotiators | Company, with supplier positions noted | Client |
| Award memo and approval | Company approvers | Company | Client |
| Signed contract | Both parties | Company, subject to the contract's confidentiality terms | Client |
| Supplier performance review | Company staff | Company | Client |
| Market price index or analyst report | A data or research provider | Third party | Third party |
| Debrief notes to unsuccessful bidders | Company buyers | Company, describing suppliers' bids | Client |

Two rows need care. A negotiation record is the company's own writing, but it often restates a supplier's prices and concessions, which is worth a line in the description. A signed contract has two authors and its own confidentiality clause; describe it as a category and let counsel read the clause.

## Three sourcing archives screened (Illustrative)

Illustrative. The archives are invented, the companies generic, and no outcome is implied.

**1. Original work.** A 450-person building-products distributor buys for its own branches. Since 2015 its buyers have run requests for quotation in an e-sourcing tool and written a bid-leveling note and an award memo for every category review, a few hundred events a year by the procurement director's estimate. Gate one: its own purchases. Gate two: memos, scorecards and negotiation notes are company writing, and the attached bids are suppliers'. An introduction rests on the decision records, with the bids listed as supplier content.

**2. Mixed third-party content.** A 280-person general contractor buys subcontracts for every project it builds. Its buyout files hold subcontractors' bids, estimators' scope-leveling sheets that restate those bids line by line, and on some projects the owner's written approval of the chosen subcontractor. Gate one is mixed: the contractor makes the selections, but for an owner's project. Gate two is heavy with supplier pricing. Counsel reads a sample of prime contracts for clauses on project records, and the estimators' leveling method, written as an internal procedure, may be the clearest company material.

**3. An uncertain ownership case.** A 160-person procurement outsourcing firm runs indirect-spend sourcing for about 40 client companies in a platform it licenses. Its own staff wrote the category playbooks and evaluation templates it uses for every client. The event records, though, are clients' purchases, and its master services agreements differ on whether the firm may use anything derived from client work. Until counsel sorts those agreements, the event history counts as client content. The playbooks may be the firm's own, and its CEO decides whether that narrower conversation is worth having. A client whose own purchasing records are strong would be a separate introduction, to that client's CEO, and only with the client's agreement.

## When the procurement files are your clients'

Specialists often keep copies of client sourcing files: evaluation workbooks, negotiation notes, the award memo they drafted. Those copies are not an archive you can refer. They record clients' decisions, they reached you under your engagement terms, and nobody in the program hands over or describes a client's records on the client's behalf.

Two things remain open to you. If a client company might fit, you can ask whether its CEO would like a conversation about the company's own records, and leave the description to the company. And if your own firm has had 50 or more full-time employees at its peak, its methodology may be its own, provided client deliverables are kept out of it; your CEO decides about that, not the engagement lead. The [management consultants overview](/for/management-consultants) covers the program from a firm's side.

## Owner and origin: who answers which question

The chief procurement officer or procurement director knows which systems hold sourcing events, from which year, who writes evaluations and whether any events were run for others. The e-sourcing or purchase-to-pay administrator can confirm dates and fields, nothing more. Counsel reads supplier confidentiality terms, client agreements and third-party data subscriptions. The CEO decides whether the company discusses licensing its records and signs for it.

Fit comes before origin. SourceX screens for a peak headcount of 50 or more full-time employees, contractors excluded, years of documented operations, rights to license and an authorized CEO. 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.

## Six questions for a first note, with no attachments

1. Which system holds sourcing events and award decisions, and since which year?
2. Roughly how many sourcing events close in a year?
3. Are any of them run on behalf of clients, members or project owners?
4. Who writes the evaluation notes and award memos?
5. What supplier, client or third-party material is attached to each event?
6. Has any of it been licensed for AI training before?

Ask for answers in a reply. If a buyer offers a sample scorecard, decline it. The company describes its own records, and SourceX's screening page counts an introduction the decision maker never heard about as usually not a fit, so the CEO learns of the conversation first. The [metadata-only opportunity map](/guides/metadata-only-referral-opportunity-map) keeps notes at the right level.

## Where an origin screen can mislead

- **Mixed authorship.** A negotiation record or an evaluator's note can quote supplier prices at length; the screen labels the document, not every sentence in it.
- **Federal files are a model, not the rule.** The FAR lists show what a decision file can hold; private files follow the company's own practice and contracts.
- **Contracts decide.** Supplier terms, client agreements and data subscriptions vary, and only counsel's reading settles them.
- **Demand is separate.** A clean screen does not show that a current SourceX program wants procurement decision history.
- **Nothing is measured yet.** SourceX has not published how often procurement records lead to introductions or licenses. Those figures are not yet published, and a log of screenings and CEO replies is the place to start.

## 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 both gates show a company making its own purchases and writing its own reasoning, and the CEO wants a conversation, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [terms](/terms), which require a signed Channel Partner Agreement before you submit it. Neighboring material sits in [procurement and vendor workflows](/data-types/procurement-and-vendor-workflows) and a worked [purchase order mismatch case](/guides/purchase-order-mismatch-resolution-exception-examples); more specialist guides are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.acquisition.gov/far/4.803
- https://www.acquisition.gov/far/3.104-4
- https://sourcex.si/humanoid-data/procurement/third-party-content-in-recordings
