The closing packet checklist, per state
Lesson 2 of 6 · Close it
1 · Learn the move · Recipe pattern
A closing runs on a packet: who delivers what, from which document, before the deed can record. The mistake is building it from a generic checklist or from your last closing in a different state, which invents items this contract never required and drops the one the county recorder will reject the deed for. The recipe pattern fixes the inputs and the output shape. Feed it only the contract, the title company's list of requirements and the recorder's own recording requirements sheet, and make every row cite the document that requires the item. 'Per state' does not mean the model knows your state. It means the state's requirements enter as a document you pasted, and a row with no source is a question for the recorder or an attorney licensed there, not an item.
Build the closing packet checklist for this cash land purchase from ONLY the contract, the title requirements and the county recorder's requirements sheet below. One row per item: item, who delivers it, source, timing, status. A row with no quoted source is not an item. [documents]
2 · Your turn. You write the prompt
You are closing a cash purchase of an 11-acre tract in Pellam County through a title company. You have the signed contract, the title company's list of requirements, and a one-page recording requirements sheet from the county recorder's office. Last month you closed in another state and your old checklist does not fit. Write the prompt that builds this closing's packet from this closing's documents.
Write the prompt for this scenario as given, or swap in a real one from your own work. The score works the same either way.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.