How contract reading works
What Closingbird reads from a contract, which files it can read, and what to check afterwards.
When you add a PDF to a transaction, Closingbird reads it with AI and fills in the file. From the executed contract it looks for:
- the deadlines in it, with how each is counted (for example 10 days after acceptance, or 3 business days before closing);
- the people: buyers, sellers, agents, lender and escrow or title, with names, emails and phone numbers where the contract has them;
- the property address, purchase price, earnest money, financing and acceptance date.
It also recognises the documents themselves, such as a signed disclosure or an addendum, and ticks them off your required-documents list.
It only fills blanks
Facts from a contract only fill fields that are empty, and never overwrite a value you've entered. A later document (an addendum or counter-offer) that states a new date replaces the earlier one. The Activity log records what each document added.
Files it can read
- PDFs only. Photos and Word files are stored on the file but not read.
- Scanned PDFs work too. When a PDF has no text layer, the first 6 pages are read as images.
- Very long documents are read up to about 12,000 characters, which covers the dates section of a standard purchase agreement.
Forms differ by state and by deal, so always look over the dates it found. Hover a deadline's name to see From <document>, and correct anything that's off with the pencil on its row. There's no "re-read" button: to read a document again, upload it again.
Reading uses AI credits from your plan's monthly allowance. If you're out of credits the file is still stored, but not read.