Assess whether to re-trade, restructure, or drop (9ca402)
August 31, 2026
SITUATION IT diligence showing two ERPs and no chart of accounts map put post-merger systems-integration risk register in front of integration-risk PMO in a health-system acquiring a specialty practice. This M&A Due Diligence / Separation and Integration close is to re-trade, restructure, or drop from post-merger systems-integration risk register, and the live options are To re-trade, restructure,, Drop.
DECISION Integration-risk PMO in a health-system acquiring a specialty practice must choose To re-trade, restructure, / Drop using post-merger systems-integration risk register 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 Separation and Integration process in a health-system acquiring a specialty practice, given post-merger systems-integration risk register. 2. IT diligence showing two ERPs and no chart of accounts map is the event in post-merger systems-integration risk register that forces To re-trade, restructure, for integration-risk PMO under M&A Due Diligence. 3. Post-merger systems-integration risk register shows a one-file miss after IT diligence showing two ERPs and no chart of accounts map, not a Separation and Integration program failure. 4. Post-merger systems-integration risk register 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 health-system acquiring a specialty practice can defend.
ANALYSIS REQUIRED 1. Separate a one-off add-back from a recurring earnings issue in post-merger systems-integration risk register. 2. Map reps, earnout mechanics, and integration risk a health-system acquiring a specialty practice would inherit. 3. Tie quality-of-earnings, working-capital, and contingent items in post-merger systems-integration risk register to to re-trade, restructure, or drop. 4. For this M&A Due Diligence Separation and Integration file, read post-merger systems-integration risk register 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 integration-risk PMO.
RECOMMENDATION Choose To re-trade, restructure, / Drop on this M&A Due Diligence / Separation and Integration packet (post-merger systems-integration risk register after IT diligence showing two ERPs and no chart of accounts map). If post-merger systems-integration risk register cannot force a M&A Due Diligence label under Separation and Integration, stop. If post-merger systems-integration risk register after IT diligence showing two ERPs and no chart of accounts map cannot support To re-trade, restructure, versus Drop on this M&A Due Diligence Separation and Integration close, integration-risk PMO must do not proceed, reprice, or walk on a quality-of-earnings fact the packet does not carry.
Explore more
More M&A Due Diligence prompts
- Assess whether working capital should be a walk-away (4db4fd)
- Assess whether earnout definitions will cause a post-close fight (293d16)
- Assess whether environmental liability is capped or open-ended (5fc53c)
- Assess whether regulatory approval is a timing risk or a deal risk (694a53)
- Assess whether a top customer is actually sticky (b09610)
Explore related decision areas
- Assess whether a referral to counsel is warranted (2a08df)Forensic Accounting
- Price-to-win analyst must resolve whether the SBIR data-rights assertions areGovernment RFP
- Assess whether prior-acts and notice issues make D&O unbindable as submittedInsurance Underwriting
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

