Assess whether to re-trade, restructure, or drop (5b76a8)
August 31, 2026
SITUATION Add-backs that are just delayed opex raised whether to re-trade, restructure, or drop for integration-risk PMO at a roll-up of three regional service companies. Post-merger systems-integration risk register is incomplete relative to that question, so Hold remains live until the file is complete.
DECISION Integration-risk PMO in a roll-up of three regional service companies must choose To re-trade, restructure, / Drop using post-merger systems-integration risk register after add-backs that are just delayed opex.
HYPOTHESES TO TEST 1. Authorize To re-trade, restructure, now; post-merger systems-integration risk register already has the discriminator after add-backs that are just delayed opex. 2. Keep Drop in force until post-merger systems-integration risk register is completed after add-backs that are just delayed opex for integration-risk PMO. 3. Treat post-merger systems-integration risk register as To re-trade, restructure, because both readings appear after add-backs that are just delayed opex. 4. Refuse a M&A Due Diligence close: integration-risk PMO does not have the decision to re-trade, restructure, or drop turns on in post-merger systems-integration risk register.
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 Legal, IP, and Regulatory file, read post-merger systems-integration risk register against add-backs that are just delayed opex 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 / Legal, IP, and Regulatory packet (post-merger systems-integration risk register after add-backs that are just delayed opex). The follow-on Legal, IP, and Regulatory action is what integration-risk PMO 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 integration-risk PMO - Hypothesis scorecard against post-merger systems-integration risk register: supported / rejected / untestable - Named option among To re-trade, restructure,, Drop and the fact that kills the others - Owner and next date for integration-risk PMO in a roll-up of three regional service companies
Explore more
More M&A Due Diligence prompts
- Assess whether earnout definitions will cause a post-close fight (ef7b24)
- Assess whether management can run this without the founder (68bd29)
- Assess whether working capital should be a walk-away (f6bf6f)
- Assess whether related-party sales should be backed out of valuation (24518e)
- Assess whether the carve-out is operable on day one (0182f8)
Explore related decision areas
- Assess whether umbrella attachment is too thin for the hazard (66ca21)Insurance Underwriting
- Assess whether a control deficiency is significant or material (25b892)Forensic Accounting
- 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.

