The Series· No. 18 · Act IV — The Engine

By DocuSeller · Published

Human Gates
DocuSeller · No. 18

Everything except the judgement

We spent as long on the stop button as we did on the start button.

Automating everything is the wrong goal.

Automating everything except the judgement is the goal.

A person deliberately pauses the workflow at a review gate Pause for human judgmentReview gate
Built with exactly as much care as the other one.

There are two places our fulfillment engine stops itself and waits for one of your people.

The first is Document Review.

The flow halts and hands somebody the generated documents alongside the data that was filled into them. Not the finished PDF on its own — the PDF and the numbers that went into it, side by side.

"This letter looks fine" and "this letter is correct" are two different sentences.
An illustrative certificate and its owner and balance inputs are shown together for review Review the document with its inputsCertificateExample recordOwner: M. AlvarezBalance: $1,284Collected inputsOwnerM. AlvarezBalance$1,284Inspect both, edit the inputs if needed, then approve
The document, and the numbers that went into it. Together, or it isn't a review.

Only one of them survives a closing.

If something is off, the reviewer edits the collected inputs right there and approves. Nothing re-runs from the top.

And there is no timeout. None. It will wait until Thursday. It will wait until next Thursday. These documents carry legally binding balances, and a queue that gives up after 24 hours is worse than no queue at all.

The second stop is Bucket Approval.

A reviewer adjusts the assembled order package before final approval The last look before releaseOrder packageDocumentsAdd or renameCurate before approval
The last look before the lid goes on.

The package is assembled, and before it goes anywhere near a title company an admin can take the lid off on the order page. Nested folders. Drag things around. Rename, add a file, remove a file. Even re-fill the form fields on a PDF.

Last-mile curation. Every real package needs a bit of it.

Sitting beside those two is the Approval step, for when somebody has to formally sign off rather than tidy up.

→ any one approver
→ all of them
→ or a majority

An example approval group shows two approvals and one pending decision, with a request-changes path Choose the approval ruleAny oneAllMajorityExample: two approvals, one pendingApprover 1Approver 2Approver 3Request changes
Any one. All. Majority. And a road back.

Plus a "request changes" path that loops back into the flow instead of dead-ending in somebody's sent folder.

And it can stop for someone who doesn't work for you at all — email a vendor a link, wait for the certificate, carry on. That one gets its own post.

And each approver gets a real task on their board. Not an email that everyone quietly assumes somebody else answered.

The usual pitch for automation is "no humans needed."

Ours is narrower and, I think, more honest.

No humans needed for the typing. Humans absolutely needed for the judgement.

We just made sure the machine knows which is which.

Next up: what this thing does on a bad day. Because there are bad days.

#Automation · #HOA · #PropTech