Endorsements I did not order showed up on the commitment and I did not catch them until after closing

Mixed-use in Ohio I've seen this exact thing, Columbus specifically, where the title company added an ALTA 9 without a request and it quietly changed what the lender thought they were getting.

The assumption doing the most work in the closer's answer is that "routine on mixed-use" functions as an authorization. It does not. An endorsement is a contractual modification of the policy's covered risks, and the underwriter's decision to add it has to trace back to a documented request or a disclosed underwriting rule, not a verbal practice.

The specific risk you named is real and underappreciated. If a claim arises under ALTA 9 coverage, and the insured's counsel starts reconstructing what representations were made during the commitment phase to support the endorsement's issuance, a file with no written request creates a gap. The underwriter issued coverage on an assumption about the property's condition that nobody on the transaction side reviewed or confirmed. That cuts both ways: the insured might argue coverage, the underwriter might argue the endorsement was issued in error and the scope should be read narrowly. Neither outcome is clean.

On the checklist question: the control point that works is a pre-HUD endorsement reconciliation step. Before the closing disclosure or settlement statement goes final, somebody compares the endorsement schedule on the most recent commitment against a written request log maintained from the opening order. Every endorsement on the commitment should map to a written request, either from lender's counsel, the buyer, or a disclosed underwriting requirement with a citation. Anything on the HUD that is not in the log triggers a hold until it is resolved in writing, not verbally explained by the closer.

The FinCEN compliance work coming in 2026 makes this kind of file hygiene more important, since the transactions that attract the most regulatory attention, non-financed transfers to entities, are also the transactions where endorsement scope questions around title representations could surface in a review.

What does your current order-opening workflow look like for capturing endorsement requests from lender's counsel, and is that log living in the file or only in email?

My triplex acquisition in 2022, the title company added an ALTA 9 without being asked and when I pushed back the closer said "we always do it on properties with shared walls." That is not a reason, that is a habit someone wrote into a checklist years ago and nobody questioned since. I ended up paying it because catching it at the table felt petty against the size of the deal, which is exactly the psychology that lets this persist. The $340 is not the problem you named and I agree completely, but I want to be more specific about why the claim scenario bothers me: if the endorsement was issued without the underwriter actually underwriting the risk it covers, meaning no survey review, no environmental search, no zoning confirmation, just a box ticked because mixed-use triggers a template, then you potentially have coverage that was never properly underwritten sitting on a policy. When a claim hits that covered risk the underwriter has a defensible argument that issuance was procedurally defective. That argument might not win but it will absolutely delay and complicate a payout.

The written request log idea is right and I would go one step further: the request log needs to tie each endorsement to the document or condition that justified it. Zoning 3.1 exists because someone confirmed the current use is legal nonconforming or wanted protection if it is, not because the property has a commercial component. So what did the title company actually pull before they added that ALTA 9, was there a survey in the file or did they just see "mixed-use" and reach for the template?