Assess whether to re-trade, restructure, or drop (a38074)
August 31, 2026
SITUATION A roll-up of three regional service companies cannot treat add-backs that are just delayed opex as incidental context on environmental known-condition schedule. Integration-risk PMO must close to re-trade, restructure, or drop from that extract under M&A Due Diligence / Legal, IP, and Regulatory.
DECISION Integration-risk PMO in a roll-up of three regional service companies must choose To re-trade, restructure, / Drop using environmental known-condition schedule after add-backs that are just delayed opex.
HYPOTHESES TO TEST 1. Authorize To re-trade, restructure, now; environmental known-condition schedule already has the discriminator after add-backs that are just delayed opex. 2. Keep Drop in force until environmental known-condition schedule is completed after add-backs that are just delayed opex for integration-risk PMO. 3. Treat environmental known-condition schedule 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 environmental known-condition schedule.
ANALYSIS REQUIRED 1. Tie quality-of-earnings, working-capital, and contingent items in environmental known-condition schedule to to re-trade, restructure, or drop. 2. Name the document integration-risk PMO still needs before signing. 3. Test whether add-backs that are just delayed opex is a diligence gap, a price chip, or a walk-away. 4. For this M&A Due Diligence Legal, IP, and Regulatory file, read environmental known-condition schedule 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 (environmental known-condition schedule after add-backs that are just delayed opex). Lead with the M&A Due Diligence option environmental known-condition schedule can support after add-backs that are just delayed opex, then the two facts that force it, then the Monday action for integration-risk PMO in a roll-up of three regional service companies.
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 integration-risk PMO - Hypothesis scorecard against environmental known-condition schedule: supported / rejected / untestable - Regulatory or exam hook Legal, IP, and Regulatory would cite - Legal, IP, and Regulatory finding in environmental known-condition schedule that a second reviewer can re-perform
Explore more
More M&A Due Diligence prompts
- Assess whether integration costs were sandbagged in the CIM (938b7b)
- Assess whether integration costs were sandbagged in the CIM (f2bfea)
- Assess whether management can run this without the founder (0bfe78)
- Assess whether related-party sales should be backed out of valuation (7d543c)
- Assess whether IP is owned or merely licensed (9f500c)
Explore related decision areas
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.

