You've just drawn the automation that produces the one document a closing can't happen without.
How do you find out whether it works?
Not by selling one.
There's a Test workflow button on the canvas. It opens a rehearsal room: what you are pretending happened on the left, what the engine did about it on the right.
The left side asks for an order that doesn't exist. Pick a community, pick an address — real ones, out of your own records — and the unit, the association and the current owner fill themselves in. Street, city, state, zip, the owner's name, their email, their phone. Exactly what a real purchase would have handed over.
Then you invent the buyer, because there isn't one. Order number, name, email, phone. Whatever you like.
Everything the community brings is real. Everything the buyer brings is yours to make up.Hit Run Test.
The canvas lights up station by station while you watch. Each one turns green as it finishes, carrying its own stopwatch. Click any station to read what it actually produced. A station that fails goes red and gives you the real reason.
Then the part people brace for and don't get.
It isn't a simulation. The letter that comes out is the letter.Nothing is held back. The letter merges against that real address. The PDF is built for real. If you wired an email step, that email leaves the building. The only thing a test run skips is attaching the result to an order, because there isn't one.
So use a real address, and put your own email in the buyer box.
A dress rehearsal with real costumes. The costumes are the point.
Test runs keep their own history, apart from real orders. Numbered, timed, replayable in one click — and a replay starts from the same sample data, so the only thing that changed is your fix. The earlier attempt stays where you left it.
None of this is glamorous. It is the difference between shipping automation and hoping.
Next: what happens when the engine needs an answer from someone who does not work for you.