Assess whether to re-trade, restructure, or drop (472cc8)

SITUATION A public acquirer facing HSR and sector regulators cannot treat IT diligence showing two ERPs and no chart of accounts map as incidental context on environmental known-condition schedule. Customer-contract risk reviewer must close to re-trade, restructure, or drop from that extract under M&A Due Diligence / People and Contracts.

DECISION Customer-contract risk reviewer in a public acquirer facing HSR and sector regulators must choose To re-trade, restructure, / Drop using environmental known-condition schedule after IT diligence showing two ERPs and no chart of accounts map.

HYPOTHESES TO TEST 1. IT diligence showing two ERPs and no chart of accounts map is noise around an already-controlled People and Contracts process in a public acquirer facing HSR and sector regulators, given environmental known-condition schedule. 2. IT diligence showing two ERPs and no chart of accounts map is the event in environmental known-condition schedule that forces To re-trade, restructure, for customer-contract risk reviewer under M&A Due Diligence. 3. Environmental known-condition schedule shows a one-file miss after IT diligence showing two ERPs and no chart of accounts map, not a People and Contracts program failure. 4. Environmental known-condition schedule cannot decide to re-trade, restructure, or drop yet after IT diligence showing two ERPs and no chart of accounts map; hold is the only M&A Due Diligence close a public acquirer facing HSR and sector regulators can defend.

ANALYSIS REQUIRED 1. Map reps, earnout mechanics, and integration risk a public acquirer facing HSR and sector regulators would inherit. 2. Tie quality-of-earnings, working-capital, and contingent items in environmental known-condition schedule to to re-trade, restructure, or drop. 3. Name the document customer-contract risk reviewer still needs before signing. 4. For this M&A Due Diligence People and Contracts file, read environmental known-condition schedule against IT diligence showing two ERPs and no chart of accounts map and write the one fact that would move to re-trade, restructure, or drop for customer-contract risk reviewer.

RECOMMENDATION Choose To re-trade, restructure, / Drop on this M&A Due Diligence / People and Contracts packet (environmental known-condition schedule after IT diligence showing two ERPs and no chart of accounts map). The follow-on People and Contracts action is what customer-contract risk reviewer does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line M&A Due Diligence option on to re-trade, restructure, or drop, then the evidence in environmental known-condition schedule, then the action for customer-contract risk reviewer - Hypothesis scorecard against environmental known-condition schedule: supported / rejected / untestable - What changes to re-trade, restructure, or drop if IT diligence showing two ERPs and no chart of accounts map is later withdrawn - Named option among To re-trade, restructure,, Drop and the fact that kills the others