# Decide how two files identify the same material

Withdraw a prepared declaration, confirm one pair and deliberately declare two shared material numberings.

Source: https://help.smartfact.ai/tracebench/guides/connect-records

Audience: Operator

Practice runs the real TraceBench application with synthetic files and isolated saving. Prepared controls only supply files to real input controls. Nothing is uploaded or sent to a live service.

## Decide how two files identify the same material

1. **Open the prepared two-file example**

   Open the prepared two-file example.

   Try an example prepares synthetic production and despatch files, mappings, coverage and one numbering declaration. This is disclosed setup; your own files need explicit review.

2. **Open the explicit identity decisions**

   Open the explicit identity decisions.

   The prepared example already has one declaration. Matching text alone creates only a possible link, never an automatic join.

3. **Explain why a decision is being withdrawn**

   Explain why a decision is being withdrawn.

   Give the basis for the change. Withdrawing appends a decision and keeps the earlier decision and saved results.

4. **Withdraw the prepared declaration**

   Withdraw the prepared declaration.

   Remove the active example numbering bridge. New runs use current decisions; earlier saved results retain their original basis.

5. **See where the unconfirmed trace stops**

   See where the unconfirmed trace stops.

   The trace still reaches production batches, but cannot cross to despatch on text alone. Reached possible links remain explicit gaps.

6. **Find one exact material pair**

   Find one exact material pair.

   Filter possible identity pairs to B-1001. This selects candidates for your review; it does not confirm one.

7. **Choose the exact pair**

   Choose the exact pair.

   Read both source and numbering labels. Confirm only this pair when that is the extent of your knowledge.

8. **State the pair confirmation basis**

   State the pair confirmation basis.

   The reason is your declaration of knowledge. This synthetic reason does not assert a real source check.

9. **Confirm only that pair**

   Confirm only that pair.

   This confirmation crosses B-1001 only. It does not confirm B-1002 or all other matching codes.

10. **Trace through the single confirmation**

   Trace through the single confirmation.

   Only the confirmed B-1001 bridge adds S-501 and S-502. B-1002 remains unconfirmed until you deliberately declare or confirm its identity.

11. **Choose the two material columns**

   Choose the two material columns.

   A numbering declaration applies only to compatible exact material codes in these two versioned roles. It never matches shipments or operations.

12. **State the numbering declaration basis**

   State the numbering declaration basis.

   Give a reason for believing these two roles share their numbering. A declaration cannot prove either file is exhaustive.

13. **Declare the shared numbering**

   Declare the shared numbering.

   Only exact matches in the two chosen material roles are bridged. Remapping either file needs a new decision.

14. **Read the result with both bridges**

   Read the result with both bridges.

   S-503 now joins the reached set through B-1002. The missing source sequence still means Partial; confirming identities does not repair coverage.

[Watch or practise this chapter](https://help.smartfact.ai/tracebench/demo?guide=connect-records&chapter=connect-records&audience=office)