Assess whether environmental liability is capped or open-ended (851ea0)

Situation

Add-backs that are just delayed opex put environmental known-condition schedule in front of integration-risk PMO in a roll-up of three regional service companies. This M&A Due Diligence / Legal, IP, and Regulatory close is environmental liability is capped from environmental known-condition schedule, and the live options are Environmental liability is capped, Open-ended.

Decision

Integration-risk PMO in a roll-up of three regional service companies must choose Environmental liability is capped / Open-ended using environmental known-condition schedule after add-backs that are just delayed opex.

Hypotheses to test

• Authorize Environmental liability is capped now; environmental known-condition schedule already has the discriminator after add-backs that are just delayed opex.
• Keep Open-ended in force until environmental known-condition schedule is completed after add-backs that are just delayed opex for integration-risk PMO.
• Treat environmental known-condition schedule as Environmental liability is capped because both readings appear after add-backs that are just delayed opex.
• Refuse a M&A Due Diligence close: integration-risk PMO does not have the page environmental liability is capped turns on in environmental known-condition schedule.

Analysis required

• Test whether add-backs that are just delayed opex is a diligence gap, a price chip, or a walk-away.
• Separate a one-off add-back from a recurring earnings issue in environmental known-condition schedule.
• Map reps, earnout mechanics, and integration risk a roll-up of three regional service companies would inherit.
• 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 environmental liability is capped for integration-risk PMO.

Recommendation

Choose Environmental liability is capped / Open-ended on this M&A Due Diligence / Legal, IP, and Regulatory packet (environmental known-condition schedule 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.