The dates come out of your contract, not out of a formula. Beverly watches them and writes the nudge before one slips.
In testingBuilt, and running in our own testing environment. It is switched off for customer accounts, so you cannot use it yet. The Transaction Assistant is built and runs against real contracts in our own testing environment. It is switched off for customer accounts, so you cannot use it today. It is on this site because it is close, not because it is available.
Beverly used to calculate deadlines from state rules, and we took it out. Those windows are negotiated blanks, not arithmetic: two Texas contracts on the same day can carry different option periods because two people agreed to different numbers. So Beverly reads the dates in your contract and asks you to confirm them.
The dates that hang off another date are worked out for you: the closing disclosure three business days before closing, the final walk through the day before, the inspection review two days before the inspection deadline.
Business days skip weekends. There is no holiday calendar yet, which is worth knowing in a week with a federal holiday in it.
An amendment that moves a date moves what depends on it.
Beverly watches the ladder every day rather than at the moment you happen to look, and flags overdue dates, dates due within two days, dates nobody owns, and dates that contradict each other.
The checklist tracks the stage the file is in, what is done, and what nobody has started.
A deliberate restraintIt is easy to build a system that generates work faster than a human can clear it. A competitor's own marketing screenshot advertises 388 open tasks. Beverly is meant to tell you the few things that matter today, not to hand you a longer list.
Walkthrough coming
A deadline about to slip, and the message already written
You approve a nudge rather than discovering a missed date. Planned length: 60 seconds. We would rather leave the space marked than fill it with something staged, so this is a slot and not a video yet.