Reading Schedule B Before the File Moves

Separate requirements from exceptions

Schedule B is two different lists wearing one label. The requirements tell the parties what must happen before the policy issues, such as paying off a lien or recording a release. The exceptions describe what the policy will not cover, such as an easement or a boundary matter.

A preparer who treats both as a single checklist will either chase items that need no action or miss a condition that blocks issuance. The first pass sorts every line into requirement, exception, or unclear, and unclear lines go to the title officer rather than into a guess.

Map each requirement to a source document

For every requirement, record the instrument or payoff that satisfies it, the party responsible, and the evidence expected. A mortgage payoff needs a good-through date and a per-diem figure. A release needs a recording reference once it exists. An HOA item needs the association's current statement or estoppel.

The map should show which requirements are already satisfied in the file and which are only promised. A promise in an email is not a recorded release, and a payoff quoted two weeks ago may no longer be accurate at disbursement.

Read exceptions against the property record

Compare each exception to the survey, plat, and prior policy. Note the recording number, the affected area, and whether the exception is standard for the jurisdiction. If an exception appears in a new location or with different language than the prior policy, mark the difference for the title officer.

The assistant can gather and compare documents. The decision about whether an exception is acceptable, insurable, or needs a curative affidavit belongs to the title officer and, where required, the underwriter.

Track endorsement requests separately

Endorsements often depend on facts that are easy to lose in a general checklist: the loan type, the property use, the survey date, and whether the borrower is an entity. Keep a short endorsement log with the requested form, the reason, the supporting document, and the approval status.

When a requested endorsement cannot be supported by the file, say so early. Discovering the gap at the closing table forces a choice between delaying the signing and accepting coverage the parties did not expect.

Re-read the commitment after every update

Commitments change. A new exception can appear after a survey is returned, a requirement can be added after a lender review, and a payoff can be revised. Each update gets a dated comparison against the prior version, with additions and removals called out.

Store the comparison beside the commitment in the transaction record. A reviewer should be able to see which version governed the closing and why a line disappeared, rather than assuming the newest PDF erased the issue.

Set the handoff point for the closing table

Before the signing appointment, confirm that every open requirement has a named owner and a realistic completion date. Anything that cannot be satisfied before signing should be identified in writing so the closing manager can decide whether to proceed, hold, or restructure.

A clean schedule is not one with no exceptions. It is one where each line has been read, classified, sourced, and assigned, and where the remaining judgment sits with the person authorized to make it.

Questions