Assess whether to re-trade, restructure, or drop (b3ea93)
August 31, 2026
SITUATION The working file is post-merger systems-integration risk register after a contractor who actually wrote the core code. Buy-side QoE lead in a roll-up of three regional service companies has to name To re-trade, restructure, or Drop for this M&A Due Diligence People and Contracts file.
DECISION Buy-side QoE lead in a roll-up of three regional service companies must choose To re-trade, restructure, / Drop using post-merger systems-integration risk register after a contractor who actually wrote the core code.
HYPOTHESES TO TEST 1. Buy-side QoE lead can defend To re-trade, restructure, from post-merger systems-integration risk register after a contractor who actually wrote the core code in a M&A Due Diligence challenge. 2. Buy-side QoE lead cannot defend To re-trade, restructure, from post-merger systems-integration risk register; Drop is what the extract actually supports after a contractor who actually wrote the core code. 3. A contractor who actually wrote the core code never reached the population in post-merger systems-integration risk register — reopen intake, do not close to re-trade, restructure, or drop. 4. Two facts in post-merger systems-integration risk register after a contractor who actually wrote the core code conflict for buy-side QoE lead; hold this People and Contracts file.
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 roll-up of three regional service companies 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 People and Contracts file, read post-merger systems-integration risk register against a contractor who actually wrote the core code and write the one fact that would move to re-trade, restructure, or drop for buy-side QoE lead.
RECOMMENDATION Choose To re-trade, restructure, / Drop on this M&A Due Diligence / People and Contracts packet (post-merger systems-integration risk register after a contractor who actually wrote the core code). The follow-on People and Contracts action is what buy-side QoE lead 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 post-merger systems-integration risk register, then the action for buy-side QoE lead - Hypothesis scorecard against post-merger systems-integration risk register: supported / rejected / untestable - People and Contracts finding in post-merger systems-integration risk register that a second reviewer can re-perform - Missing page in post-merger systems-integration risk register after a contractor who actually wrote the core code, if any
Explore more
More M&A Due Diligence prompts
- Assess whether regulatory approval is a timing risk or a deal risk (8662a5)
- Assess whether integration costs were sandbagged in the CIM (6a267b)
- Integration-risk PMO must resolve whether working capital should be
- Assess whether earnout definitions will cause a post-close fight (481e74)
- Assess whether earnings quality supports the bid price (c8cdc3)
Explore related decision areas
- Whether pollution coverage should be site-specific or blanket from CAT modelInsurance Underwriting
- Assess whether to price to win or walk from a buy-in after a data-rightsGovernment RFP
- Determine aI Commercial Auto Fleet Renewal Analysis PlaybookInsurance 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.

