Transaction work runs backward from the closing date. A closing in 3 days with half the paperwork still open is the signal an admin acts on, not a line buried in a PDF. Joymore treats dates as structured data on every file, not text to hunt for.
When a document lands on a file, Joymore pulls out the dates that matter: contract date, closing date, inspection period, financing contingency deadline, earnest money due date, and similar milestones. Each one is stored as a structured field on the transaction, alongside parties and property details (see Getting transactions in).
When an amendment pushes the closing date back two weeks or shortens an inspection period, Joymore reads the change and updates the file's dates. You don't re-enter anything, and the rest of the file, including compliance and any automation watching that date, follows the new schedule.
A contract often states a deadline as a period rather than a date, like "inspection contingency: 17 days after acceptance." Joymore takes the acceptance date and every contractual period on the file and calculates the actual calendar date each one falls on, so a deadline shows up as a real day, not math you do by hand.
Counteroffers and amendments control which terms apply. When a counteroffer changes a period, or a later amendment resets one, Joymore recalculates the due date from whichever terms are currently in force, not the original offer.
Each transaction shows its next relevant due date, so a file's timeline points at what's coming next without anyone opening the contract to check.
The Transactions page can filter and sort on these fields directly: closing in the next 3 days, inspection periods ending in 10 to 14 days, contracts still inside the 72-hour submission window, files with no activity in 30 days. It can also sort by each file's calculated due date, so the file closest to its next deadline rises to the top. That turns "what needs attention this week" into a sort, not a search through files.
Automations can key off these same dates. Tell Joymore something like "list transactions closing within 10 days that still have failing checks" or "flag files with no activity in 30 days" and it runs on that schedule, no separate configuration screen involved (see Knowledge and automations).