When a consulting scope ends at closing but the problem surfaces thirty days later
A client closes on a small mixed-use acquisition and the consulting engagement ends at the closing table, clean scope, delivered work, paid invoice. Five weeks later a recorded mechanics lien surfaces that the title policy does not cover because the work was completed before the policy date but invoiced after, and the client calls asking what to do. The scope said nothing about post-closing support. The question I have not settled is whether a well-written scope that ends at closing should include one sentence about what happens to problems that trace back to pre-closing work, or whether adding that sentence opens a liability that the flat fee was never priced to carry. A success-fee engagement is a different animal because the advisor has skin in the outcome past the closing date, but on a flat scope the delivered work is delivered. What I keep coming back to is the gap between what the client understood the engagement to cover and what the document actually said, and that gap is almost always wider than either party noticed at signing. Have you ever written a scope that explicitly addressed what happens to a pre-closing problem that shows up after your engagement ends, and did that language protect you or just invite the conversation you were trying to avoid?