Deadlines and the timeline

Every transaction has a set of milestones: the dates it turns on, such as earnest money, the investigation, loan, and appraisal contingencies, the final walk-through, close of escrow, and possession. They appear in two places on the transaction, and a change in either saves as you make it:

• the Workflow tab's Milestones section, where every date is open for editing at once;
• the Milestones section on the Overview tab, a list in date order that you correct one date at a time. It appears once the transaction has a document; until then, use the Workflow tab.

Where the dates come from

You don't enter them. When the purchase agreement finishes processing, LetterScript reads the agreed time periods and computes the calendar dates. Counter offers and later amendments, such as an extension of time, override the original contract's terms, so the dates reflect what was finally agreed.

Only paper that took effect moves the dates:

• A counter offer or an amendment accepted after its own expiration date, with no late acceptance signed by the side that made it, isn't a contract: when LetterScript can read the form's dates, its terms and its acceptance date don't move anything, and the transaction record raises a finding. When the maker did sign the late acceptance, the dates count from that signature; on a seller multiple counter offer, from the buyer's late acceptance in its paragraph 9.
• A purchase agreement whose Offer Not Accepted block the seller initialled is a rejected offer. While another copy of the contract is on file, it doesn't set the dates, even when it's the fullest copy, and of several copies, the one both sides signed is the one counted from.
• A contingency removal, notice to perform, demand to close escrow or withdrawal whose signature lines were read and left unsigned, or signed without the side that acts on it, changes nothing on the dates. One whose signatures couldn't be read counts as before.

An extension of time can move the close of escrow, the contingencies whose boxes it checks, or both. Each date it moves says so on its line and links to the extension. When LetterScript can see that an extension left its new date blank, it moves nothing, and the transaction record flags the blank. If an extension's new close of escrow reads as the day it was signed and the form names nothing it extends, the record raises Extension's new close may be its signing date: that is usually the signature date read into an empty blank, so check the form. If an extension states a contingency date but LetterScript can't tell which contingency it extends, no contingency date moves, and the transaction record raises Extended contingency not applied so you can confirm which one.

The seller's contingency removal (CR-S) can extend the close of escrow too, in its paragraph 2A, as the seller's replacement-property addendum (SPRP) paragraph 2C allows. When the seller has signed it and the SPRP is on file, the close moves to the date it gives, or by the number of days it gives, and the close cites the removal. It never moves the close earlier. The transaction record raises Seller's close of escrow extension either way: to confirm the SPRP's paragraph 2C allows the extension, or to say why it wasn't applied, such as no SPRP on file or no seller signature read.

A date that a later document set cites that document, not the purchase agreement: a close moved by an extension of time says Extended by Extension of Time Amendment and the date it moved from, a cure date links to the notice to perform, and a rent-back's dates link to the seller-in-possession addendum. When that addendum prints the day the seller's stay ends, the Seller vacates date is that day, and the line under it notes where counting the days from the close would have landed instead. If the close has moved since the addendum was written, so its day count no longer reaches that day, the count from the current close is used and the line names the date the addendum wrote.

On an Already-Built Subdivision Purchase Agreement, a Condominium Conversion and Subdivision Purchase Agreement or a New Construction Purchase Agreement, each date cites that form's own paragraphs, not the RPA's. On the new construction form the final walk-through cites its paragraph 19 (the seller goes with the buyer to list corrective work, and it doesn't hold up the close), the close cites paragraph 1D, and the appraisal, which that form has no contingency for, cites nothing. On the subdivision form the Public report review contingency gets a date like the other contingencies. When its review period can't be read from the form, the date uses the printed 17 days, the line under it says so, and the transaction's review flags ask you to confirm the period.

A note above the list says how many deadlines were added, and from which document. Undo takes them back. If automatic deadlines are off for the transaction, the note says so and offers Turn on. On the Workflow tab, Sync dates from record recomputes the deadlines from the transaction's current dates: acceptance, close, and the contingency periods.

While a document on the transaction is still being identified, read or re-run (its row on the Files tab shows Queued or Processing, for example), the documents don't take a contract deadline off the list or move one, and your edits to those deadlines stay. The transaction's status, such as cancelled, doesn't change either. The documents already read can only add a deadline the list doesn't have yet, and on a cancelled or withdrawn transaction they add nothing. Once every document has been read or has failed to process, the normal rules apply: the dates follow what the documents say, and an automatic date that no document on file states any more comes off the list. If the documents on file give no dates at all, the list is left as it is.

There are two exceptions:

• The transaction has reached its AI processing limit. LetterScript can't identify or read any more of its documents until the limit is lifted (on a free first transaction, buying a transaction lifts it), so a document it can't read doesn't hold anything back: the normal rules apply to the documents already read, and the status follows them too.
• The document being re-run is the only one on the transaction. While it runs, its automatic dates can come off the list and its status can be cleared; both are worked out again once it has been read. On a transaction at its AI processing limit the re-run can't be read, so they don't come back until the limit is lifted and the document has been read. A date you marked done, reopened, marked not applicable or renamed stays on the list with your mark or your name for it (see Marking a date done, below), and the re-read dates it again. A status you set by hand stays.

A document LetterScript can't identify is filed with no type, and its row on the Files tab reads Set type: until you pick its type and it has been read, the dates and the status are worked out from the other documents, with one difference for In contract that the transaction record describes. Dates you added yourself never come off.

When the clock starts after acceptance

Some addenda start the contract's time periods on a later event instead of acceptance: the short sale lender's consent, the cancellation of a prior transaction (back-up offer), the seller's removal of a replacement-property contingency, or the exercise of an option. The contingency for the sale of the buyer's property does it only when its paragraph 11A box is checked. On those transactions:

• Until the event is on file, the contingency deadlines stay off the calendar, and the transaction record says what everyone is waiting for under These deadlines have not started yet. A date nobody can act on is left out rather than shown from the wrong start.
• Once it's on file, each date's line names the event it was counted from, for example "Replacement-property contingency removed (2026-09-07) + 21 days", instead of acceptance. The counting-rule preview skips these dates, because they don't count from acceptance.
• A contingency date set by an extension of time signed after that event is the date used, even when counting from the event would put the deadline later: the extension's date is the one both parties signed. An extension signed before the event never pulls the deadline earlier.
• On a short sale, a back-up offer, or a replacement-property contingency, the deposit moves with the other dates. A home-sale contingency leaves it on the purchase agreement's schedule.
• On a home-sale contingency that starts the clock, the time periods begin on the first of three events: the buyer's escrow evidence, a signed election, or removal of the contingency. When only the removal is on file, the dates are counted from it and the record raises These deadlines may start earlier. Check whether the escrow evidence or an election came first, and set the dates by hand if it did.
• On a short sale, the lenders' consent usually arrives on its own form, the Delivery of or Failure to Deliver Short Sale Lender Written Consent (DSSC). The dates count from the delivery date written on it, or from the day the seller signed it when none is written. When the lenders' consent changes the terms (its paragraph 3), they count from the day the buyer accepts that amendment, and not before. A DSSC dated before the short sale addendum belongs to an earlier escrow and doesn't count. If the short sale addendum kept the purchase agreement's time periods (its paragraph 3(ii)), the dates stay counted from acceptance whatever the DSSC says. A DSSC whose paragraph 2 is checked and signed by the party cancelling cancels the transaction.
• On a replacement-property addendum whose paragraph 1B is checked, the seller is already in contract on a replacement: the dates and the deposit count from acceptance, and unless paragraph 1C (close of the replacement property) is checked too, the seller has no replacement-property contingency left to remove.

The seller's notice on a home-sale contingency

Page 2 of the contingency for the sale of the buyer's property (COP) ends with the seller's Notice to Remove Buyer Contingencies and Provide Proof of Funds. Once the seller has signed and dated it, it works like a notice to buyer to perform: under the COP's paragraph 7B the buyer has 2 days after it (or the number written there) to remove the home-sale and loan contingencies and show the funds to close without the sale, or the seller may cancel. Its cure date goes on the calendar, counted from the date the seller signed it, since the delivery date isn't printed, and the transaction shows At risk until a contingency removal the buyer signs after it takes out every buyer contingency. LetterScript can't see the proof of funds itself; if the buyer performed some other way, mark the cure date done and set the transaction's state from the pill beside its name. The date the seller signed this notice isn't read as the buyer removing the contingency.

Reading a date

Markers on each row say how the date got there:

• ✨ means the date was derived from a document. Click it to see how the date was counted (for example, "Acceptance + 17 days"), with a link to the Source document and to the counting rule. A derived date is an estimate: confirm it against the executed contract, or use Set this date by hand.
• From Follow Up Boss means the date came from the transaction's Follow Up Boss deal (its projected close, or a date field such as earnest money or possession). It follows Follow Up Boss until someone changes it here, and once the contract is uploaded the contract's date replaces it.
• Edited means someone changed a derived date by hand. Hover over it to see who changed it and when; the revert arrow beside it puts back the document's value, or Follow Up Boss's for a date that came from Follow Up Boss, which then follows Follow Up Boss again. A date added by hand is marked Added.
• rolled means the date moved off a weekend or holiday (see How deadlines are counted, below).
• TC marks a finer-grained date a transaction coordinator tracks (see TC dates and All dates, below).
• A first name beside a Done or N/A chip says who marked it. Hover over it to see when. If the documents have moved the date since, the name is outlined and the hover says the date it was marked on. Reopened means someone un-ticked a date the documents show as done (see Marking a date done, below).

A line under each derived date spells out how it was counted. A date you set by hand always wins: re-processing a document never overwrites it.

Following a date to its source

On the Workflow tab, a derived date has a document icon. Click it to preview the page the date was read from. When the date couldn't be pinned to one spot on a page, the icon is a speech bubble instead: clicking it opens the document beside the assistant, with a question about the date ready to send. On the Overview, the date itself is the link (it's underlined with dots) and works the same way.

A deadline counted from another date, such as acceptance plus 17 days, isn't printed anywhere in the contract, so its link points at the date it was counted from. See the transaction record for how citations work.

Dates shown as a chip

Some rows show a chip instead of a date:

• Waived: a contingency the contract waived, with a 0-day period.
• Removed: a deadline struck because the transaction was cancelled.
• Done: a contingency that a signed contingency removal has already removed, the investigation contingency when an agreed request for repair removed it by its own terms (RR paragraph 4A, or the seller's response and buyer reply, RRRR, paragraph 2), or a final walk-through that a signed Verification of Property Condition records. A buyer's removal made on a request for repair or on the seller's response to one (the boxes at the top of the CR-B) counts only once that repair is agreed: until an agreed response dated on or after it is on file, its contingencies stay open and the transaction record raises Contingency removal waiting on an agreed repair. A signed Verification of Property Condition shows the walk-through on the date on the form instead of the estimate of five days before close. That needs a signed form dated no later than today, within ten days before the close and not after it, and not signed before the extension that set the close. Otherwise the estimate stays live, and the line under it gives the date of the form on file. The smoke and carbon monoxide alarm and water heater bracing date is Done once the documents on file certify all three items between them. A Transfer Disclosure Statement (TDS) certifies the smoke alarms and the water heater bracing but not the carbon monoxide device, so a TDS also needs the Water-Conserving Fixtures and Carbon Monoxide notice (WCMD). A water heater statement (WHS) covers the water heater only, not the smoke alarms. The carbon monoxide row on the Documents checklist and the seller's Retrofit & compliance step on the Purchase timeline follow the same rule. Until all three are certified, the step names the items still to certify, such as the carbon monoxide device when only a TDS or a WHSD is on file. The HOA document fees are Done once the HOA documents are on file. These dates keep the contract's date. A date you tick yourself shows Done too, with your name beside it.
• N/A: a date someone marked Not applicable in Purchase timeline, such as the loan contingency on a cash deal.

None of these land on the calendar or send a deadline alert to your phone.

Marking a date done

The check mark on a date marks it done. Click it again to take the mark back. A date you mark is yours, whatever the documents do next:

• It stays done when a counter offer, an extension, a corrected acceptance date or a change to the counting rule moves the date, after Undo on the note above the list, and when you replace the transaction's only document. The date itself still follows the documents.
• When the documents show a date as done, for example a contingency a signed removal took out, and you un-tick it because the removal didn't cover it, it stays open and on your calendar until you tick it again. Ticking it again hands it back to the documents. Once the documents no longer show it done, your un-tick has nothing left to answer and the date follows the documents again, so a later removal that does cover it marks it done.
• A cure date answers one notice to perform. When you mark it done, the calendar moves on to the next notice still waiting to be cured, with its own cure date, even when the documents still show the first notice open (a demand for the deposit, for example, which no contingency removal answers). The notice you marked is then listed under the dates as Notices to perform settled by hand, with who marked it and when. If it wasn't settled after all, its Reopen puts its cure date back on the calendar. A later notice that sets a new cure date opens the date again, whatever you marked before. When that later notice goes, because a signed removal cured it or you deleted it, and every notice still open is one you marked, the cure date goes back to the latest of them still marked done (or not applicable) in the name of whoever marked it, and stays off your calendar. To reopen it, mark it not done there. Undo on the note above the list doesn't reopen a notice you marked either: when marking it done moved the calendar on to the next notice, Undo puts the cure date back on the notice you marked, still done. A demand to close escrow's cure date comes off by itself when both sides sign an extension after it that moves the close past that date.
• Mark done and Not applicable on a step in Purchase timeline mark the step's date the same way when finishing the step is that date: the deposit, the increased deposit, delivering the disclosures, the loan and insurance contingencies, the buyer's home sale, the replacement property, a cure, the final walk-through, early occupancy, close, possession and the seller moving out. It then comes off your connected calendar, Follow Up Boss tasks and deadline alerts. A step that's only dated by a contingency, such as Inspections, Appraisal or a review step, leaves that contingency's removal date alone: the buyer still holds the contingency until it's removed in writing. Ticking the date yourself only marks it done in LetterScript; it doesn't remove the contingency. Reopen on the step, or Undo after Mark done on the phone, takes back what the step marked and puts back what it replaced, such as your un-tick of a date the documents show as done. When marking a cure done had moved the calendar on to the next notice, it puts the earlier notice's cure date back. Reopening the date itself reopens the step too, and so does Reopen on a notice in Notices to perform settled by hand that the step marked.

Each mark, and each one taken back, is recorded in the transaction's history with the name of whoever made it.

When a date has passed

A deadline doesn't drop off when its day goes by. While the Workflow tab's Purchase timeline still shows its step open, with no document proving it and nobody marking it done, the transaction counts it as past due:

• the What's next card on the Overview leads with the oldest one, shown as −8d with "was due Sep 23" and how many more are past due. The next two dates still ahead stay below it;
• the transaction's Needs you band starts with one item, for example 2 deadlines past due, which opens Purchase timeline, where those steps are flagged.

A step a document already proves, such as seller disclosures that are on file, isn't counted, and a transaction that's closed, cancelled, or withdrawn has nothing past due. Once a late step is handled, use Mark done on it in Purchase timeline. When finishing the step is the date itself, such as the deposit or the walk-through, its date is marked done too, so it stops counting and comes off your calendar (see Marking a date done, above). If the date itself is wrong, correct it instead.

How deadlines are counted

By default, deadlines count calendar days, as the C.A.R. California Residential Purchase Agreement (RPA) does. When a computed contract deadline, such as a contingency, the deposit, or close of escrow, lands on a Saturday, Sunday, or a holiday county recorders close for (the federal holidays plus the day after Thanksgiving), it rolls to the next business day, under paragraph 25.I(4) of the purchase agreement. Under the standard purchase agreement, a deadline passing doesn't remove a contingency or cancel the contract by itself; that takes a signed removal or the contract's notice process. The final walk-through and possession dates never roll. A rolled date carries the rolled marker, and the line under it says it rolled to the next business day. Click its ✨ to see the weekend or holiday it moved off and the date it landed on. On the Calendar, the date is marked rolled from the original day.

The rule is set for your whole account on the Calendar page, in the strip above the calendar grid. Click Adjust to choose Calendar days or Business days (business days aren't the purchase agreement's standard) and to turn Roll weekends & holidays forward on or off, then click Save rule. Unlike milestone edits, nothing changes until you do; Cancel throws the choice away. A change applies to each transaction the next time its dates are derived. To recount a transaction under the new rule right away, open its Workflow tab and use Re-derive these dates (see below) or Sync dates from record. Settings → General shows the current rule under Deadline counting, with a Change on Calendar link.

On the Workflow tab's Milestones section, a line notes which rule the transaction's dates were counted under and how many were rolled, with a Counting rule → link. If your account's rule has changed since, it says so and offers Re-derive these dates or Keep as counted. Re-deriving can move a deadline that's already in the contract, so it's your call.

TC dates and All dates

The finer-grained dates a transaction coordinator tracks are tagged TC: delivery of the seller's documents and the review of those documents, the installation of smoke and carbon monoxide alarms and water heater bracing (paragraph 3N(4) of the purchase agreement, paid by the party paragraph 3Q(4) names), and the fees for ordering the HOA documents when the transaction has an HOA, plus informational access to the property, an increased deposit, or due diligence when you add one with Add milestone. An increased deposit read from a signed addendum or counter offer is an ordinary date: it isn't tagged TC and shows on the Calendar without All dates. The Calendar leaves them out unless you turn on the All dates filter in its toolbar. A transaction's own Milestones list always shows every date. The review of the seller's documents is the one TC date that also sends a deadline alert to your phone (see Deadline alerts on your phone, below); the other TC dates don't.

Adding and renaming milestones

Dates aren't limited to what the contract derives. In either Milestones section:

• Add milestone adds a row you then set to a standard event, such as inspection scheduled, appraiser scheduled, seller or buyer signing, loan funding, or counter offer.
• Add custom adds a free-form milestone. Name it anything.
• Rename any date: on the Workflow tab, type over its name; on the Overview, use the pencil beside its name. Renaming is only a rename: the date stays the document's, keeps its ✨, and still moves when a counter offer or a re-read changes it — including being dropped if the documents stop calling for that deadline at all. Your name sticks through those refreshes. To take the date over as well, type the date you want.

Each change saves only what you changed. A date the documents move while you're working on another one keeps the documents' date, and a deadline they drop isn't put back by your next save. If a date changes while you have it open on the Overview, the row says what it is now: saving replaces it with yours, and cancelling keeps it. A deadline you add while the documents are still being read keeps the date you typed, even if they come up with the same deadline a moment later. If someone else removed a deadline while you had the page open, your change to it isn't saved: it's listed under Removed deadlines, where Restore puts it back. Older transactions can hold several custom dates under one name, some without a date. A change to any other date leaves every one of them as it is. Changing one of them (a new name, or Done, even on one with no date), removing it, or Undo right after, changes only that one, and one that someone else removes while you're working on another stays removed. If the dates changed while you had the page open in a way it can't match up, your change isn't saved, and the message asks you to reload the page and make it again.

Remove a row with its ×. Undo appears for a few seconds afterwards and puts the row back exactly as it was. Clearing a date to type a new one doesn't remove anything; only the × does. A deadline that came from your documents or from Follow Up Boss stays removed: uploading another document, Sync dates from record, re-deriving after a counting-rule change and the next Follow Up Boss sync all leave it off, while every other date keeps following the documents. It's listed under Removed deadlines, below the dates, with who removed it and when; Restore puts it back as it was. Adding the same deadline again by hand also lifts the removal, and removing it again later keeps it off again. A date you added yourself just goes when you remove it. Custom milestones also appear, marked Yours, among the steps of the Workflow tab's Purchase timeline.

If the transaction is shared with you as view-only, you can see the dates but not change them.

The rest of the Workflow tab

The same documents drive the Workflow tab's Purchase timeline section, the transaction's checklist, and its Activity section, the record of what each document did. Under Documents on the timeline, every document is listed by the date it took effect, with a badge for what it did (Establishes, Amends, Settles, Lifecycle for one that changes the transaction's status, such as a cancellation, or Context) and a link to the document itself. See The Workflow tab.

These links point at a document, not a spot on a page — the claim is "this is why this row exists", not "this page says X". For a value quoted out of a page, see the transaction record.

The Calendar

Calendar, in the navigation bar (in the menu on a phone), shows every active transaction's dates, along with your booked meetings, on one calendar in Month, Week, or Day view. Filter to Inside 7 days or Meetings, or turn on All dates to include TC dates. In Month or Week view, click a derived date to see how it was counted, with a link to its transaction; a date set by hand opens its transaction directly. A date someone set or moved by hand shows a small pencil in place of the ✨, and hovering the date says who set it and when; a date from Follow Up Boss says so too. In Day view, clicking a date opens its transaction, and the info icon beside it shows how it was counted.

On a transaction's Workflow tab, See these dates on the Calendar under the list of sections opens the same calendar. On a phone, where the sections become a row of buttons across the top, that link isn't shown; open Calendar from the menu instead.

To push these dates into your own Google or Outlook calendar, use Calendar sync in Settings → Integrations (the Calendar page links to it); see Sync deadlines to Google or Outlook Calendar.

Deadline alerts on your phone

LetterScript doesn't email deadline reminders, to you or anyone else. What it does send is a push notification to your phone, through the LetterScript mobile app:

• Turn them on with Deadline alerts in the mobile app's Account tab. That switch signs your phone up for LetterScript's notifications, so the same phone also hears when a batch of documents finishes processing and when new email arrives on a transaction. Turn it off to stop them all. If you signed up with an email and password, or you sign in with Microsoft, confirm your email address first (see Confirm your email address).
• Which deadlines: every contingency on either side, such as the investigation, loan, appraisal and insurance contingencies and the reviews of the seller's documents, the preliminary title report and the HOA disclosures, plus close of escrow. The review of the seller's documents is tagged TC, but it's a contingency, so it's the one TC date that sends alerts. The deposit, the final walk-through, possession and the other TC dates don't.
• When: two alerts per deadline, both at 8 AM Pacific time: one two days before, and one on the morning of the deadline. The two days count the way your account counts deadlines (Calendar days or Business days; see How deadlines are counted, above), and with Roll weekends & holidays forward on, an early alert that would land on a weekend or holiday comes the business day before instead. Each says what's due and when, such as Loan contingency in 2 days, with the property's address and the date; tap it to open the transaction.
• Whose phone: only the person who created the transaction. Collaborators don't get alerts for a transaction shared with them, even with Can edit access.
• Which transactions: active ones in a board category marked In flight (see Create a transaction). A sample transaction, or one that's cancelled or withdrawn, sends none. A transaction whose automations you muted (with the old Mute automations for this transaction switch, before LetterScript stopped sending automatic emails) stays silent too: it sends no deadline alerts.

A deadline that's waived, voided, marked done or already past sends nothing. When a date moves, the new date gets its own two alerts. An alert that can't go out by 11 AM, because your phone couldn't be reached or the service was down, is skipped rather than sent late. Alerts are a nudge, not a guarantee: the dates on the transaction, and the contract, are what count.

Meetings booked through Calendly are different: their reminders are emails, and they're the one automatic email LetterScript still sends.

Sending the dates to someone else

Dates sheet, at the top of the Workflow tab's Milestones section, downloads this transaction's deadlines as a one-page PDF, as they stand — the sheet to hand escrow, the agent or the lender. Review first… beside it opens the sheet on a review screen instead, where you can check each date, leave a row off this copy, or correct a date, either for this copy only or in the transaction record too, before you download it or attach it to an email. Each row carries the day of the week as well as the date, because under the standard purchase agreement a contract deadline that lands on a weekend or a holiday usually moves to the next business day, and the day name is the quickest way to check that. For a date the contract derived, the sheet also shows how it was counted; a date you set by hand appears without that note, and any reason you typed beside it stays private to the transaction rather than travelling with the sheet.

Dates already done, or waived, or voided by a cancellation stay on the sheet and are labelled as such: that a contingency was waived is something the other side needs told, and an absent row says nothing at all. A date someone marked Not applicable in Purchase timeline reads N/A, not Waived, because the contract didn't waive it. A milestone you haven't dated yet isn't listed, but the sheet says how many there are, so nothing drops off it quietly. The footer carries the same caveat the app shows beside these dates — they are derived from your documents, and the executed contract governs.

The button appears once the transaction has at least one date. A collaborator with view-only access can download it too. The same sheet is Dates sheet in the Send menu in the transaction's header, which opens the review screen from any tab; see Send and share from a transaction. A date you correct for one copy only loses its "how it was counted" note on that copy, since the note no longer applies.

A sheet is a snapshot: it says what the dates are today. If the other side would rather their own calendar followed your dates as they move, send them the subscribable feed instead — it comes from the same read-only link, on the transaction's People tab. Once you have a link, Send → Copy calendar link copies the feed from anywhere on the transaction. See Share a transaction.

After the close of escrow date

The documents can only show that a transaction closed through a settlement record: the recorded grant deed, the Closing Disclosure, or escrow's settlement statement. Many files end without one. So once the close of escrow date has passed with none on file, the top of the transaction reads Close was instead of Closes and asks whether it closed:

• Set to Closed asks you to confirm, then sets the transaction's state to Closed, the same as choosing Closed from the state pill beside its name. The state then stays Closed until you choose Auto (clear override) from that pill: documents uploaded later, such as a notice to perform or an extension, don't change it. The pill shows a pin while the state is set by hand; hovering it says who set it and when (see The transaction's state).
• If escrow was extended instead, upload the signed extension or change the close date. The question goes away once the close date is ahead again.

It isn't asked on a transaction that's cancelled or withdrawn, marked closed or archived from the ⋮ menu, or whose close of escrow milestone is marked done.

If a date looks wrong or is missing

Deadlines depend on the contract documents. If the purchase agreement or the latest counter offer isn't uploaded yet, or is still being read (Processing or Queued on the Files tab), dates will be missing or out of date. A transaction with no documents yet shows an Upload documents button on its Overview tab. If a derived date is simply wrong, type the right one: your date wins. See Extraction didn't fill in.

An empty deadline list tells you which case you're in

A transaction with no deadlines says why, and the three reasons need different things from you:

• "No deadlines yet — the acceptance date couldn't be read." A contract is on file, but the date the contract was accepted wasn't found in it — and every other deadline is counted from that one, so nothing can be derived. This is the case that looks most like a bug and isn't: set Acceptance on the transaction record and the whole timeline is generated from it. Merged or scanned signature pages are the usual reason the date doesn't read.
• "No deadlines yet. Nothing on file states a date or a time period to count from." There are documents, but none of them is the contract. Add the signed purchase agreement, or add a deadline by hand below the list.
• "No deadlines yet. Upload the signed purchase agreement…" — nothing is uploaded yet.