Real Estate Transaction Workflow, Offer to Closing File

TL;DR: A real estate transaction workflow is the path every document takes from listing to closing, and the filing that path demands. It works when documents are filed by property address rather than by client or by month, because the address is the one identifier on the contract, the inspection report, the title commitment, and the closing disclosure. The Drive AI can read the address out of the document itself and file by it, so a title company email, an agent's phone photo, and a client upload all land in the same transaction folder without anyone typing a folder name.

A transaction coordinator running fifteen deals handles 450 to 700 documents at once, and not one arrives named correctly. The purchase agreement comes back from the e-signature platform as Completed_Document_8821.pdf. The title company emails Commitment_TX226-4471.pdf from an address nobody recognizes. The buyer texts a photo of a wire receipt to the agent, who forwards it on Slack as "for the Cedar Ridge one".

Every one of those documents belongs to a property, and almost none of them says which property anywhere a computer can see it, unless the computer opens the file.

A real estate transaction workflow is the ordered arc a deal's documents travel, from listing agreement through offer, inspection, appraisal, title, and closing, together with the filing that keeps each document attached to its property from the day it arrives until the retention period expires.

The document arc of a transaction

Every residential deal produces the same documents in roughly the same order. Knowing the arc is what lets you tell at a glance whether a file is complete.

• Listing. Listing agreement, agency disclosure, comparative market analysis, marketing photos.
• Offer and contract. Purchase agreement, counteroffers, proof of funds, earnest money receipt.
• Due diligence. Inspection and pest reports, repair request and seller response, HOA resale certificate, survey.
• Appraisal and financing. Appraisal report, loan estimate, conditions list, insurance binder.
• Title. Title commitment, exception documents, payoff statements, lien releases.
• Closing and after. Closing disclosure, settlement statement, deed, final walk-through, commission disbursement, title policy.

Two things about that list matter. It is roughly sequential, so a missing document is usually one that has not arrived yet rather than one that is lost. And every item names the property, because a real estate document that does not identify the property is not enforceable.

Why file by property address, not by client or by month?

File by address because the address is the only identifier that appears on every document in the deal, and it does not change when the people do.

Filing by client breaks the first time a seller is also a buyer, which happens constantly. The Ruiz folder now holds two transactions with overlapping dates and two closing disclosures that look identical in a list. The seller is the same. The transaction is not.

Filing by month breaks because a transaction does not happen in a month. A listing agreement signed in March produces an inspection report in June and a recorded deed in August, so anyone reconstructing the deal opens three folders. Filing by MLS number is closer, because it is unique, but nobody remembers it, half the documents do not carry it, and it changes when a listing relists.

The address survives all of it. It is on the contract, the appraisal, the title commitment, and the deed. It is what the client says on the phone and what the broker asks for in an audit. Folder layouts are covered in full in the guide to organizing real estate transaction files; this post is about keeping documents flowing into that layout as the deal moves.

A folder structure that survives an audit

One folder per property, numbered subfolders inside it, nothing filed at the top level. The numbering is not decoration: it forces the folders into transaction order in every file browser, so anyone can see how far along the deal is.

Transactions/
  1420 Cedar Ridge Dr, Austin TX/
    01 Listing/
    02 Contract/
    03 Inspections/
    04 Appraisal and Financing/
    05 Title/
    06 HOA/
    07 Amendments/
    08 Closing/
    09 Post-Closing/
    10 Correspondence/
    11 Media/

The part people skip is the compliance file. On request from a state commission, or in a lawsuit years later, a broker has to produce the executed contract with every amendment, every signed disclosure, the agency agreement, and the final settlement statement, for a deal that closed long after the coordinator left. That means executed documents kept apart from drafts and redlines.

The test is simple. Handed this folder on a Friday afternoon with no context, could you tell which version of the contract is the operative one?

Why do real estate documents arrive from so many different places?

Because every party in a transaction uses a different system, and none of them will change theirs for you.

Count the inbound paths on a single deal. The agent photographs a disclosure a seller signed on a car hood and sends it by text or Slack. The title company emails PDFs from an address that changes per deal. The inspector sends a portal link. The client replies to a thread with attachments named IMG_4821.jpg. The e-signature platform emails completed packets back. The HOA mails a resale certificate that gets scanned on the office copier as a 40-page PDF.

No other industry combines this many counterparties with this little shared infrastructure, so any filing system that depends on documents entering through one door catches a fraction of them. Email attachments are the biggest single stream, which is why the Gmail workflow post is the closest companion to this one, but a workflow that only watches email misses the agent's phone entirely.

How a real estate transaction workflow files by address

The address is inside the document. That is the thing that makes this automatable at all, and it is why filename matching never worked.

In The Drive AI you describe what should happen in plain English, and the steps appear on a canvas where each one can be edited. Every step carries a cost badge: free for decisions made from details already known, ai for steps that open and read the file, human for steps that wait for a person, external for steps that contact another service. All of them are covered in the guide to workflow steps.

For a transaction, the useful shape is short.

• Sources. Email Attachment watches a connected Gmail or Outlook account, scoped by sender or by "Subject contains", so the title company and the lender feed the same workflow. Messaging watches a Slack or Microsoft Teams channel, where the agent's phone photos land. File Uploaded covers anything a coordinator drops in or creates in a connected Google Drive, OneDrive, SharePoint, or Dropbox folder.
• Read Details from File (ai) pulls named values out of the document. Name the fields property address, document type, and closing date, and every later step can use them. This is what makes address filing work, and extracting data without templates covers it in depth.
• Ask AI About the File (ai) routes the document into branches you author per node, such as purchase agreement, disclosure, inspection report, title document, and appraisal.
• Move (ai) files it. A plain answer works: "into the transaction folder for this property address, then the subfolder for the document type".
• Ask a Person to Approve (human) pauses the run until someone approves, rejects, or the wait expires.
• Merge Files (ai) assembles a packet from a folder, ordered by date or by what each document is.

For documents you need from clients, file requests collect them through a link with a checklist, so a buyer sends a photo ID and proof of funds without being given access to your drive.

Example workflows

Each of these is typed as a sentence. The steps appear from it.

When an attachment arrives from a title company or lender email, read the property address and the document type out of the file, then file it in Transactions under that address, in the subfolder for that document type, and rename it with the address, the document type, and the date.

When a file arrives in the brokerage inbox, ask the AI whether it is a fully signed purchase agreement. If it is, ask Priya to confirm before filing it to 02 Contract, and if she rejects it put it in Transactions/Needs Review.

When a file is shared in the Slack channel #deals, if it is an image, file it to the Media folder for that property. Otherwise read the address and document type and file it with the rest of the transaction.

Every weekday, go through Transactions/1420 Cedar Ridge Dr, Austin TX/08 Closing and merge the closing disclosure, settlement statement, deed, and final walk-through into one PDF ordered by date, then ask Priya to approve it before it is filed as the closing packet.

The third one is worth reading twice. The image test runs on Check File Details, which is free and exact, so sixty photos from a listing shoot never reach an ai step. The second is review by exception, the subject of the human in the loop post: the approver sees the file and the question you wrote beside it in the Approvals inbox, and can be a named person, any admin, or anyone in the workspace.

Manual filing, transaction platforms, a shared drive, and workflows

A transaction management platform and a filing workflow solve different halves of the problem, and plenty of brokerages run both.

Transaction platforms own compliance. They know your state's forms, they track which documents a file is missing, and they give the broker a review queue built for that job. Nothing here replaces it. What they do not do is catch a document the moment it arrives in an inbox or a Slack channel and file it without a person opening it. That is the gap a workflow fills, alongside the rest of the real estate solution.

Limits worth knowing before you build this

• No e-signature step. A workflow cannot send a document for signature. It can file what comes back from the platform you use, and ask the AI whether the document is fully signed.
• No forms library and no MLS integration. There is no state forms package, and no listing feed. The address comes out of the document.
• No compliance checklist. Nothing counts whether a file is complete or flags a missing disclosure. A merge runs on what is in the folder at the time, which is why the packet example ends with a person approving it.
• ai steps can be wrong. Reading an address off a fax-quality scan is harder than reading it off a typed contract. Put Ask a Person to Approve in front of anything that leaves the brokerage.
• Approvals expire. The wait is 24 hours, 3 days, or 1 week, with 3 days the default. After that the file takes the Expired exit, and if nothing is connected there, the expiry is recorded and nothing happens.
• Connected files stay where they are. A workflow watching a folder in Google Drive, OneDrive, SharePoint, or Dropbox renames and moves files inside that storage. Nothing is imported unless you add Save a Copy.
• Connected accounts need a paid plan. Workflows on files uploaded to The Drive AI work on every plan. Connecting Gmail, Outlook, Slack, Teams, or a cloud drive needs the Max plan on a personal workspace, or any Team plan.

Setting it up

1. Create the Transactions folder and one property folder with the numbered subfolders. One live example is enough to show the shape you want.
2. Connect the account documents arrive in. Usually the coordinator's Gmail or Outlook, plus the Slack channel agents post to from their phones.
3. Write the sentence. "When an attachment arrives from a title company, read the property address and document type, then file it in Transactions under that address." Check the steps on the canvas and edit the Move instruction if it is not precise.
4. Put the free type check first. Check File Details in front of the ai steps sends images to Media so they never get read.
5. Turn on approval for the contract branch. Ask a Person to Approve on executed agreements, set to Specific people, with the actual question the coordinator should answer.
6. Run it on one live deal for a week. Open the activity feed, replay any run that went somewhere unexpected, and fix the step that caused it.

Frequently Asked Questions

How does a workflow know which property a document belongs to?

It reads the document. A Read Details from File step opens the file and extracts fields you name, such as property address and document type, and those values are available to the Move and Rename steps. That is why it works on a title commitment named Commitment_TX2226.pdf, whose filename carries nothing useful. Because the step reads the file, it carries the ai badge and can occasionally be wrong.

Can it create the transaction folder for a new listing automatically?

A Move step files into a path built from what it read, and creates structure where it needs to. That is convenient and also the thing most worth reviewing, because a new folder for 1420 Cedar Ridge Drive beside an existing 1420 Cedar Ridge Dr is how one transaction becomes two. Set the approval step to ask whenever a new folder would be created.

Does this replace Dotloop or SkySlope?

No. Those platforms own compliance checklists, state forms, e-signature, and the broker review queue, and none of that exists here. A workflow handles the filing around those systems: catching documents as they arrive by email, chat, and upload, identifying them, naming them, and putting them in the right property folder. Keep the platform for compliance and use workflows for what lands outside it.

How do I get documents from a client without giving them drive access?

Use a file request. You build a checklist of what you need, send one link, and the client uploads against each item without an account and without seeing anything else in your workspace. That covers proof of funds, photo ID, insurance binders, and HOA paperwork, the items that otherwise turn into a four-email thread per client.

Can it organize transactions I already have filed badly?

Yes, with a scheduled workflow. On a Schedule runs over a folder hourly, daily, weekly, or monthly, and its "Each run goes through" setting has an option for "Every file, every run", which is how a backlog gets reorganized in place rather than only new arrivals. Start with the current year and review the first run in the activity feed.

Start with one address

Pick the transaction closing soonest, build the folder shape once, and write one sentence that files the title company's email into it. When it holds for a week, add the Slack channel, then the contract approval. You can see how the steps fit together on the workflows page, or create a workspace and set the first one up on a live deal.