This map is part of the subcontractor evidence reconciliation guide. It is a reference for contract compliance consultants who need to describe, at metadata level, whether a client's history can be followed across its tools.
The five systems in a typical reconciliation
Many federal and commercial prime contractors spread this workflow over five places, even when two of them run on the same software.
- Contract files. The subcontract, every modification and the flowdown list attached to each. Sometimes a contract management system, often a structured folder.
- Supplier portal. Where subcontractors upload evidence packages and where analysts comment on them; often also the approval workflow.
- Project platform. Change orders and scope revisions that drive the modifications.
- Compliance mailbox. Deficiency letters and the subcontractor's replies, in a shared or personal mailbox.
- Quality log. Corrective actions and closeouts, sometimes in a quality system, often a spreadsheet.
The flowdown list deserves its own node because it changes. For subcontracts for commercial products and services, FAR 52.244-6 sets out 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. A scope change can switch one of those conditions on or off, so a correct history keeps one list per modification rather than one list per subcontract.
System, record, linking key and owner
The core of the map. Fill the last column with the role at the client who looks after that system.
| System | Record | Linking key it must carry | Joins to | Typical owner |
|---|---|---|---|---|
| Contract files | Subcontract and modification | Subcontract number and mod number | Flowdown list, change order | Subcontracts manager |
| Contract files | Flowdown list per mod | Mod number and clause references | Evidence attestations | Subcontracts manager |
| Project platform | Change order and SOW revision | Scope revision and mod number | Subcontract mod, evidence package | Project controls lead |
| Supplier portal | Evidence package | Submission ID and scope revision cited | Flowdown list, reviewer comment | Supplier compliance director |
| Supplier portal | Reviewer comment | Submission ID | Evidence package | Compliance analysts' manager |
| Compliance mailbox | Deficiency letter | Deficiency number and submission ID | Comment, approval, closeout | Supplier compliance director |
| Supplier portal | Approval or conditional approval | Submission IDs and reason | Evidence and supplemental | Supplier compliance director |
| Quality log | Closeout entry | Deficiency number | Deficiency letter, supplemental | Quality manager |
Two rows carry most of the risk. The evidence package must cite a scope revision, or it cannot be matched to the right flowdown list. The deficiency letter must carry both its own number and the submission ID, or the closeout cannot be traced back to the gap that triggered it.
One case, fully joined (Illustrative)
A different case from the worked exception example, to show the keys at work on another kind of requirement. Everything here is fictional. A 120-person electrical subcontractor works under subcontract SC-204. Modification 02 adds a site-access training module for every worker badged onto the base. The subcontractor's next package, EV-3105, includes a training roster, but four of its 19 workers completed only the older course.
| Order | System | Record | Keys present on the record |
|---|---|---|---|
| 1 | Project platform | Change order CO-12 adding the training module | SC-204, new SOW paragraph |
| 2 | Contract files | Mod 02 with the requirement added to the flowdown list | SC-204, mod 02 |
| 3 | Supplier portal | Package EV-3105 with roster of 19 workers | SC-204, mod 02 cited |
| 4 | Supplier portal | Analyst comment: 4 workers lack the new module | EV-3105, requirement named |
| 5 | Compliance mailbox | Deficiency letter D-112 | D-112, EV-3105, 14-day deadline |
| 6 | Supplier portal | Partial approval: 15 workers badged, 4 held | EV-3105, D-112, reason recorded |
| 7 | Supplier portal | Supplemental certificates EV-3160 | SC-204, D-112 |
| 8 | Quality log | Closeout with all 19 badged | D-112, EV-3105, EV-3160 |
The decision in row 6 is the interesting one: rather than reject the whole package, the director let most of the crew work and held four badges. It can be read later only because the approval carries both the package ID and the deficiency number. Had the hold been agreed by phone, the closeout in row 8 would show a result with no visible decision behind it.
Where the joins usually break
| Join | Common break | What a later reader loses |
|---|---|---|
| Mod to flowdown list | List kept as one unversioned spreadsheet | Which clauses applied on a given date |
| Evidence to requirement | Attestations describe controls, not clause numbers | Which requirement each document answers |
| Evidence to scope | Revision field blank or free text | Whether the package was judged against the right scope |
| Comment to evidence | Deficiency sent from a personal mailbox | The reasoning behind the request |
| Decision to evidence | Conditional approval agreed in a meeting only | Why work was allowed to continue |
| Closeout to deficiency | Closeout logged without the deficiency number | Proof the gap was actually closed |
A partner does not need to fix any of this. Knowing which breaks exist lets the company describe its history honestly, and a history with known gaps can still be worth reviewing.
Confirming fields with the administrator, not a brochure
Whether the supplier portal and project platform can export these keys, including comment history and workflow timestamps, depends on the product, the edition and how the company configured it. Treat that as unknown until the company's own administrator confirms it. Ask about field names and retention, never for an export or a login. The metadata-only inventory method shows how to phrase those questions, and the general ledger reconciliation prep sheet applies the same idea to finance records. Construction subcontracting raises similar joins between pay applications and change orders, covered in pay application review records.
The map also feeds the introduction. A completed version supplies the systems, coverage and open-question lines of the subcontractor reconciliation referral brief. If you are a consultant placed through another firm, check the subcontractor agreement guide before raising the subject.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license 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: subcontractor confidentiality terms, controlled information, buyer interest and any offer.
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 records carry most of these keys across its systems, register as a partner, confirm the company against who qualifies, and read the program terms before you share the map's findings with the supplier compliance director.