Subcontractor evidence reconciliation: what to inventory before a subcontractor transition

Short answer

Before a subcontractor transition, inventory the record classes that explain each evidence reconciliation: the flowdown list for every subcontract modification, the evidence the subcontractor submitted, the reviewer's notes, the approval or rejection that closed it, and the scope changes behind it. For each, record the system, the years covered, the named owner and the date access actually ends. Then introduce the supplier compliance director. Partners describe records; they never collect them.

Visual briefFull-size diagram
A timeline around a subcontractor transition day showing five record classes and when access to each ends: the portal account on day 0, departing staff mailboxes at day 30 and the project folder at day 60, with the inventory finished before day 0.
Illustrative access deadlines for one subcontractor transition. Real dates come from the company's contracts and IT plan.

Why a subcontractor transition puts reconciliation history at risk

Subcontractor evidence reconciliation is the work of checking what a subcontractor submitted against what its subcontract required: certifications, insurance, flowdown clause acknowledgments, test results, staffing records. For commercial products and services, FAR 52.244-6 lists the clauses a contractor must flow down, several only when their own conditions apply, and FAR 44.402 limits the required clauses to that list. Each modification can change the list, so the history is a sequence of requirement sets and the evidence matched to each.

A transition happens when a prime or higher-tier contractor replaces a subcontractor at a recompete, terminates for convenience, or consolidates trades under a new firm. The evidence history does not move with the work. The outgoing firm's portal account is deactivated, its submittal folder is closed out, and the compliance team's notes stay scattered across a portal, a project platform and email. Nobody decides to discard the history; it simply stops being reachable on dates set by IT tickets and vendor contracts.

The pre-transition inventory sheet

Inventory record classes, their date coverage, the system that holds each, the named owner and the real access deadline. Every column is metadata; none requires opening a document.

Record classTypical systemAsk the companyOwner to name
Flowdown list per subcontract and modificationContract management or subcontract filesHow many subcontracts and mods, over how many years?Subcontracts manager
Evidence submissionsSupplier portalIs the submission history retained after a supplier account is closed?Supplier compliance director
Reviewer notes and deficiency lettersSupplier portal comments, email, shared driveAre notes attached to the submission or kept separately?Compliance analysts' manager
Approvals, conditional approvals, rejectionsSupplier portal workflow or project platformIs the decision timestamped and tied to a scope revision?Supplier compliance director
Scope revisions and change ordersProject platformCan each change order be matched to a subcontract mod number?Project controls lead
Corrective actions and closeoutsQuality system or spreadsheetIs the closeout linked back to the original deficiency?Quality manager

Reviewer notes are the class most often lost. Submissions and approvals usually live in a workflow tool with an export path; the reasoning between them often lives in individual inboxes that are archived when staff move to other programs.

Work backward from each access deadline

The access deadline, not a sales timeline, is the only real urgency. Different record classes lose access on different days, so list each one.

Illustrative deadline map for one transition, not a real company:

Day relative to transitionWhat happensRecord classes affected
Day -30Inventory complete and owners namedAll
Day 0Outgoing subcontractor's portal account deactivatedEvidence submissions, approvals
Day 30Departing project staff mailboxes archivedReviewer notes, deficiency letters
Day 60Project folder closed out on the project platformScope revisions, closeouts

In practice the steps are:

  1. Find each date. Ask IT and the portal administrator when accounts close, mailboxes are archived and project folders are closed out. If nobody knows, that is the first finding.
  2. Measure coverage. Count subcontracts, modifications and years per record class. Approximate figures are fine.
  3. Check the joins. Do approvals cite a modification or scope revision number? If not, a later reader cannot tell which requirement set the evidence was judged against.
  4. Name owners and restrictions. Note controlled unclassified information, customer confidentiality clauses and subcontract terms that limit reuse.

What a partner should not recommend

FAR 4.703 generally requires contractors to keep records and supporting evidence available for 3 years after final payment, longer if a contract clause says so. That is a retention floor for audit, not permission to reuse anything. Do not recommend that a company keep records it has no authority to keep, or override its retention schedule to preserve material for a licensing discussion. The right outcome of an inventory is a decision by the record owner, not a copy made by an outsider. The metadata-only inventory method shows how to keep discovery at that level, and the page on government contractor data and CUI restrictions covers the controlled-information questions.

Does the company qualify?

The introduced company needs 50+ full-time employees at peak (contractors excluded, which matters in a subcontract-heavy business), 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 90% of the data is in English.

What stays unknown until SourceX reviews it: whether the records can be licensed after the contract and controlled-information review, which records a buyer would want, the company's offer, and therefore any reward. Partners sign the Channel Partner Agreement before submitting an introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. For the wider picture, see the industries hub, the guide to a recompete loss and why data rights matter.

Go deeper on subcontractor evidence reconciliation

Next step

Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's transition date is set and its reconciliation history spans years, register as a partner, confirm the company against who qualifies, and read the program terms before you send the one-page handoff.

  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 rewardYour 25% of the actual supplier payout. 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

Does the FAR retention period mean the company can license these records?

No. FAR 4.703 sets how long a contractor must keep records available to the government. It says nothing about reuse. Whether the records can be licensed depends on the company's contracts with its customer and its subcontractors, any controlled information, and SourceX's rights review.

Can the outgoing subcontractor be the referred company instead?

Possibly, if it meets the eligibility rules on its own and owns the records it would license. Its view of the same reconciliation is different: its submissions and correspondence, not the prime's review notes. Only one partner is credited per company.

Should the partner ask for a sample reconciliation file?

No. Describe record classes, counts, date ranges and systems. SourceX reviews actual content only after the company has authorized a discussion and the rights review starts.

Sources

  1. refer.sourcex.si/terms
  2. acquisition.gov/far/52.244-6
  3. acquisition.gov/far/4.703
  4. acquisition.gov/far/subpart-44.4

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 90% 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