The Series· No. 52 · Act XIII — The Working Surface

By DocuSeller · Published

The Studio
DocuSeller · No. 52

The letter that asks you questions

Most documents need three values nobody has yet.

The closing date. Who to make the check out to. A signature.

So we let the letter ask.

An untouched separate form gathers a cobweb while a person walks past it One more thing to openSeparate formThe letter waits on a second page
The separate form. Six months old. Still blank.

The usual answer is a separate form. You build it, you email it, you wait. A form is a second thing to open, and second things do not get opened. They get replied to with "sorry, just seeing this".

So the fields live inside the sentence instead.

In the letter editor you drop a field into the middle of a paragraph — text, email, date, a dropdown, a signature — and it sits exactly where the sentence needs it. The letter still reads like a letter. It just has holes in it, on purpose.

Every field gets a setting for who fills it:

→ Connected — we already hold the answer, take it from the records
→ Purchaser — it shows up in the buyer's pending actions
→ Admin — it lands on a desk here
→ or a party you name yourself — the seller, the listing agent, the vendor

That last one matters more than it looks. You are not stuck with our three roles. Name your own parties and each gets their own link, showing them their own blanks and nobody else's.

Owner, date, and signature fields sit in the letter and are assigned to connected records, the purchaser, and a named seller party The sentence holds its own fieldsForonsignedOwnerDateSignatureConnectedFrom recordsPurchaserBuyer actionSellerNamed party
Same sentence. Different people finishing it, and you choose who.
A letter that knows which of its own blanks it cannot answer.
An unfinished letter projects above an open package because its closing-date field is still awaiting input One missing value keeps it openLetterClosing dateAwaiting inputWaiting on inputsPaused until the answer arrives
One value missing, so the lid stays open. That is the correct behavior.

Then the part people find odd at first.

If a field needs a human, the order stops. Not fails. Stops. That line item goes to waiting on letter inputs and sits there. No timeout. Indefinitely, if that is what it takes.

Waiting on somebody who has stopped replying is not the same as waiting forever, though. Staff can open the same fields and fill them on the buyer's behalf, or just copy the link and send it somewhere more useful.

Because the alternative is issuing a legally binding document with the closing date still reading as a placeholder, and that is considerably worse than late.

A completed merged letter enters a bank of PDF workers and sends a ready update to the watching screen Complete input → render → notifyMergedletterPDFPDFPDFPDF readyLive update
Nobody sits refreshing. The finished page announces itself.

When the last answer lands, the merged letter joins a small rendering queue — a bank of workers whose entire job is turning a finished page into a PDF — and the moment one is done it pushes itself back to whoever is watching.

The document is the form. There was never a good reason for two of them.

Next: four minutes of syncing, and what it looks like when you can actually watch it.

#DocumentAutomation · #PropTech · #HOA