Transaction Support
A real estate transaction involves many moving parts — agreements, disclosures, inspections, financing documents, title or escrow information, signatures, deadlines, follow-ups, and closing requirements. Different people may be responsible for different parts of the process.
A Real Estate Support VA can help keep the administrative side organized: organizing transaction folders, maintaining document checklists, tracking milestones, monitoring authorized deadlines, identifying missing documents, following up on pending items, maintaining a transaction status tracker, preparing status updates, documenting exceptions, and escalating issues that require professional judgment.
The work requires attention to detail. A missing document can matter. A wrong date can matter. An outdated document can matter. An unclear instruction can matter.
At the same time, transaction support has important boundaries. A VA does not interpret contracts, provide legal advice, decide whether a condition has been satisfied, determine whether a transaction should proceed, or make other professional decisions simply because the information appears in a transaction file.
The goal of this module is to help you keep the transaction organized while knowing when something belongs with the appropriate professional.
A Quick Note About Transaction Terms
You will encounter terms such as contingency, disclosure, amendment, addendum, title, escrow, and closing in this module. These terms have specific meanings in real estate, and some processes vary by state, brokerage, transaction type, and client. If a term is unfamiliar, add it to the Real Estate Support VA Quick Glossary as you work through the module — plain-English definition, noting variation. You do not need to memorize every transaction term before you can provide administrative support. Focus on understanding what the term means for the task you are being asked to perform, and ask when the client's process is unclear.
Module Goal
Learn how to organize transaction information, track documents and milestones, monitor deadlines, manage follow-ups, and communicate transaction status while staying within the VA's administrative role.
Learning Outcomes
- Explain the basic stages of a residential real estate transaction.
- Identify common transaction milestones.
- Explain the administrative role in transaction support.
- Organize transaction folders and document checklists.
- Identify missing transaction items.
- Track milestones and deadlines from authorized sources.
- Maintain transaction status.
- Manage follow-ups.
- Prepare transaction status updates using the Standard Status Report Template.
- Identify discrepancies and information gaps.
- Apply Act, Clarify, Verify, or Escalate to transaction situations.
- Log transaction exceptions in the Running Exception & Escalation Log.
- Handle transaction information responsibly using the Module 1 confidentiality principle.
- Recognize transaction-specific information-handling risks.
- Stay outside contract interpretation, legal advice, and professional decisions.
- Produce a Transaction Support Tracker.
Understanding the Real Estate Transaction
A residential real estate transaction involves a series of activities that move a property from an accepted offer toward closing. A simplified teaching model is:
Actual transactions vary by state, brokerage, transaction type, contract, client process, property, and parties involved. The sequence is a learning model, not a universal legal process.
Offer
A buyer may submit an offer to purchase a property. A VA may help organize information or documents related to the offer according to the client's instructions. The VA does not negotiate the offer or decide whether it should be accepted.
Accepted Offer / Contract
Once the appropriate parties have accepted an agreement, the transaction moves into the next stage. The VA may help organize the executed documents and begin tracking transaction requirements. The VA does not interpret the contract.
Due Diligence & Contingencies
Due diligence is the period when the parties complete or review information and requirements related to the property and transaction. A contingency is a condition or requirement that may affect how the transaction proceeds. The exact requirements depend on the transaction. Depending on the transaction, this stage may involve inspections, financing conditions, disclosures, other contingencies, required documents, and deadlines.
Financing & Other Conditions
A transaction may involve financing-related requirements and other conditions. It may include lender documents, financing milestones, appraisal-related information, title or escrow activities, and additional conditions. The VA may track whether requested information or documents have been received. The VA does not determine whether a buyer qualifies for financing or whether a condition has legally been satisfied.
Final Preparations
As closing approaches, there may be outstanding documents, signatures, title or escrow requirements, final confirmations, scheduling, and follow-ups. The VA can help track these administrative items according to the client's process.
Closing
Closing is the point at which the transaction is completed according to the applicable process. The people and documents involved vary by location and transaction. The VA may support administrative preparation and tracking.
Who May Be Involved?
Buyer, seller, real estate agent, broker, transaction coordinator, lender, inspector, appraiser, title professional, escrow professional, attorney where applicable. Not every transaction involves every role. The important question is: Who owns the decision?
| Lender | Financing decisions |
| Inspector | Inspection findings |
| Appraiser | Professional valuation |
| Attorney | Legal interpretation |
| Agent / broker | Professional real estate decisions |
| VA | Administrative support |
Transaction Support Is Not Transaction Decision-Making
Consider: "The inspection report is in. Is the property still a good deal?" That is not a document-tracking question — it requires professional judgment. A VA may locate the inspection report, file it correctly, record that it was received, and notify the appropriate person. The VA should not decide whether the property remains a good deal.
Map Tasks to Stage and Role
For each scenario, identify transaction stage, administrative task, responsible professional if applicable, what the VA may support, and what the VA should not decide.
- The buyer's lender requests confirmation that financing documents were received.
- The seller asks whether the inspection findings mean the buyer will walk away.
- The title company sends closing documents for review.
Transaction Documents & Checklists
Transactions generate documents — purchase agreement, disclosures, inspection documents, financing documents, title documents, amendments, addenda, signatures, closing documents. The exact document list varies by transaction, state, brokerage, and client. Do not assume that every transaction requires the same documents.
Use the Client's Checklist
If the client provides a transaction checklist, use it — it is more important than a generic list remembered from training. A client's checklist may identify required documents, responsible party, due date, status, and follow-up instructions.
Document Statuses
Received, Missing, Pending, Sent for Signature, Signed, Needs Review, Superseded, N/A — used according to the client's definitions.
Status Does Not Equal Interpretation
A document marked "Needs Review" — the VA may record that status if instructed, but should not interpret the document and decide what it means legally. A document marked "Signed" means the client's process has identified it as signed; it does not authorize the VA to determine whether the signature makes the agreement legally effective.
Document Checklist
A simple checklist may contain: Document, Responsible Party, Due, Status, Date Received, Notes.
Build a Document Checklist
Include at least eight document or information items, responsible party, due date where supplied, status, date received, and notes. Identify at least two items that require follow-up.
| Document | Responsible Party | Due | Status | Date Received | Notes |
|---|
Transaction Folder Organization
Transaction documents should be organized so the people supporting the transaction can find what they need.
├── Contract & Agreements/
├── Disclosures/
├── Inspections/
├── Financing/
├── Title & Closing/
├── Amendments & Addenda/
├── Communications/
└── Tracking/
The actual folder structure should follow the client's SOP.
Why Organization Matters
Poor organization can create problems — final.pdf, final2.pdf, final-new.pdf, final-really-final.pdf makes it difficult to know which version is current. Transaction support requires more than putting files into folders — it also requires version awareness.
Version Control
A document may be current, superseded, draft, awaiting signature, or signed. If multiple versions exist, do not simply choose the one that looks newest — follow the client's process for determining the current or approved version.
Superseded Documents
A superseded document may still need to be retained. Do not delete transaction documents simply because a newer version exists, unless the client specifically authorizes that action and the client's process permits it.
Naming Conventions
If the client provides a naming convention, follow it — for example: 1234-Oak-Street-Purchase-Agreement-Signed.pdf, 1234-Oak-Street-Inspection-Report.pdf, 1234-Oak-Street-Amendment-01-Signed.pdf. These are examples only; the client's actual convention takes priority.
Organize a Fictional Transaction Folder
For a folder containing agreement, disclosures, inspection, financing document, title document, amendment, communication, and tracking file — identify correct folder, current version, superseded version, unclear version, and any file requiring clarification.
Milestones & Deadlines
Transactions involve dates — contract dates, inspection dates, financing milestones, document deadlines, signature deadlines, follow-up dates, closing date. The exact dates and requirements come from the transaction and the client's process.
Authorized Deadline Sources
A deadline should come from an authorized source: client-approved transaction tracker, client-provided milestone schedule, transaction system, authorized document or workflow, or another source identified by the client's SOP. Do not independently interpret a contract to calculate legal deadlines.
Example
| Milestone | Date | Source |
|---|---|---|
| Inspection | September 12 | Client tracker |
| Financing update | September 18 | Client tracker |
| Closing | September 25 | Client tracker |
The VA may track these dates according to the client's instructions. A date recorded in a client-approved tracker is an administrative tracking date — the VA should not independently treat it as a legally calculated deadline unless the client's authorized process has already established that date. But if the VA reads a contract and concludes "the inspection deadline must actually be September 13," that is contract interpretation — the VA should not independently make that determination.
Deadline Tracking
A simple milestone tracker can contain: Milestone, Date, Source, Status, Owner, Follow-up.
Date Conflicts
If two authorized records show different dates, do not choose one — apply the verification process. Identify conflicting dates, sources, required verification, current status, and next action.
Build a Milestone & Deadline Tracker
Include contract milestone, inspection, financing, document deadline, signature deadline, closing, and follow-up. For each, record date, source, owner, status, and follow-up action.
| Milestone | Date | Source | Status | Owner |
|---|
Missing Documents & Follow-up
A transaction can slow down when a required document is missing. The VA's role is to identify the missing item, track it, and follow up according to the client's process.
Identify
What is missing?
Assign
Who is responsible for providing it?
Record
Document the item and expected date.
Follow Up
Send or prepare the appropriate follow-up.
Update
Update the tracker when the status changes.
Escalate if Needed
If the item is overdue, the responsible party is unclear, or the issue requires a professional decision, follow the client's escalation process.
Follow-up Queue
A useful queue may contain: Item, Responsible Party, Due, Status, Last Follow-up, Next Action. This prevents pending work from disappearing into email threads.
Follow-up Does Not Mean Pressure
Professional follow-up is clear and factual — for example: "Following up on the inspection report requested for 1234 Oak Street. The tracker shows it as due September 12. Please let us know when it is available." The VA should not make threats, legal claims, or promises about what will happen if the document is not provided.
Build a Follow-up Queue
Review a fictional transaction containing five missing or pending items. For each: identify the missing item, the responsible party, due date, current status, last follow-up, next action, and whether escalation is needed.
| Item | Responsible Party | Due | Status | Next Action |
|---|
Transaction Status Tracking
A transaction status tracker gives the team a quick view of what is happening. Possible status labels include On Track, Waiting, Needs Attention, At Risk, Completed — these are examples; the client may use different definitions or labels.
Status Must Be Supported
A VA should not label something At Risk simply because it feels concerning. For example: "Closing is September 25. The client has identified a required document as overdue and has instructed the VA to mark overdue items as At Risk" — that can support an At Risk status. But "I think the closing might be difficult" is an opinion. The VA should not turn personal concern into an official transaction status without support.
Transaction Status Tracker
A tracker may contain: Item, Owner, Due, Status, Last Update, Next Action, Notes.
Status Is a Snapshot
A transaction status can change — Waiting → Received → Completed, or On Track → Needs Attention → Completed. Record the status according to the client's process and update it when new information arrives.
Assign Status Using Client Definitions
Review a fictional transaction tracker. Identify what is completed, what is waiting, what needs attention, what is at risk, and what requires follow-up.
Transaction Communication
Transaction communication should be clear, factual, and actionable. The general email structure from Module 2 still applies: clear subject, greeting, purpose, relevant details, action needed, deadline when applicable, professional closing.
Transaction Communication Types
Missing documents, follow-ups, transaction status, escalations.
Template 1: Missing Document / Follow-up
Should include what document or item is needed, property or transaction reference, expected date if applicable, action requested, contact or next step.
Subject: 1234 Oak Street: Inspection Report Follow-up
Hello [Name],
Following up on the inspection report for 1234 Oak Street. Our tracker shows the document as pending.
Please send the report when available, or let us know if there is an updated expected date.
Thank you,
[Name]
This is a template structure. Use the client's actual tone, naming conventions, and process.
Template 2: Transaction Status Update
May include Completed / Pending / Follow-up / Needs Clarification / Needs Client Decision / Issues-Escalations. This structure connects directly to the Standard Status Report Template from Module 2.
Do Not Make Professional Claims
Avoid: "The transaction is legally cleared." "The buyer definitely qualifies." "The contract allows us to extend the deadline." Those require professional authority or interpretation. A VA can report what the approved tracker says — "The tracker shows the financing milestone as pending" is administrative reporting.
Draft Two Transaction Templates
Draft two transaction-specific communication templates using the Module 2 email structure. Retain these as part of your Transaction Support Tracker portfolio evidence.
Exceptions, Conflicts & Escalation
Transactions often contain situations that cannot simply be processed as routine tasks — conflicting dates, missing documents, unclear instructions, outdated document versions, conflicting transaction information, professional decisions, unclear responsibility, overdue items. The decision framework from Module 1 applies.
ACT
The task is clear, supported, and within the VA's role.
CLARIFY
The instruction is incomplete or ambiguous.
VERIFY
Information conflicts or may be outdated.
ESCALATE
The issue requires professional judgment, authority, legal interpretation, or expertise outside the VA's role.
Example: Conflicting Closing Dates
Transaction tracker: September 25. Another authorized record: September 27. Do not choose one — VERIFY. Document the conflicting dates, the sources, what needs to be confirmed, and current status.
Example: Unclear Instruction
The client writes: "Please handle the amendment." That instruction does not explain what administrative action is required — CLARIFY. Do not assume the client wants the amendment reviewed, interpreted, signed, or submitted.
Example: Professional Decision
The client asks: "Do you think we should accept this inspection result and move forward?" — ESCALATE. The VA may organize the inspection report or record the client's decision after it is made, but should not make the transaction decision.
Example: Missing Document
The checklist clearly identifies a document, the responsible party is known, and the client has instructed the VA to follow up — ACT. The VA can follow up and update the tracker.
Running Exception & Escalation Log
Add transaction exceptions to the existing course-wide log — do not create a separate Module 6 escalation log. A useful entry may contain: Date, Issue, Decision, Reason, Next Action, Status.
Six Transaction Situations
Confidentiality in Transactions
Module 1 introduced the standing information-handling principle:
If client information is not yours to share, don't share it.
The same principle applies to transactions. Transaction files can contain sensitive information, including financial information, identification information, signatures, addresses, financing information, personal contact information, transaction documents, and private communications.
You do not need to memorize a complicated privacy policy. The habit is: know what information you have, know where you are allowed to put it, know who you are allowed to share it with.
Use Only What You Need
If a task requires one piece of information, do not copy an entire sensitive document into another system simply because it is convenient. Use only the information necessary for the task.
Authorized Storage
Store transaction information only where the client has authorized you to store it. Do not move transaction files into personal storage, personal email, unauthorized messaging apps, unapproved cloud drives, or unapproved AI tools.
Authorized Access
Only access information you are authorized to access. Do not browse through unrelated transaction files simply because you have access to the folder. Access is not the same as permission to use information for any purpose.
Sharing
Do not send transaction documents to people who are not authorized to receive them. If you are unsure whether someone should receive information: clarify or escalate.
AI and Transaction Information
Transaction documents can contain sensitive financial and personal information. Do not paste transaction documents, personal information, credentials, or other confidential material into an AI tool unless the client has explicitly permitted that use and the tool or workflow is approved. If you need AI assistance with a transaction task, use fictional or non-confidential information for practice whenever possible.
The VA's Responsibility
A support VA should treat transaction information carefully even when the client has not repeated the confidentiality instruction. The Module 1 principle continues to apply.
Five Transaction-Information Scenarios
For each, determine whether the action is appropriate, what information should be used, where it may be stored, whether sharing is authorized, and whether clarification or escalation is needed.
- Saving the client's transaction documents to your personal Google Drive "just to be safe."
- Pasting the full purchase agreement into a free AI tool to summarize it quickly.
- A friend of the buyer asks you to send them the inspection report.
- Forwarding a status update to the lender who is already part of the authorized transaction team.
- Emailing yourself a copy of the closing disclosure to review at home on a personal account.
Applied Activity: The Transaction That Needs Attention
You are supporting Sarah Mitchell, in Austin, Texas. The property is 1234 Oak Street, Austin, TX — currently under contract. The client's transaction tracker shows a closing target of September 25.
Please clean up the transaction folder and tracker before I review it. Check the documents against the checklist, follow up on anything missing, and make sure the dates are correct. Please don't make any changes that require my decision. Let me know what needs my attention.
Transaction Checklist
| Item | Responsible Party | Due | Status |
|---|---|---|---|
| Purchase Agreement | Buyer / Seller | Completed | Signed |
| Seller Disclosure | Seller | September 10 | Received |
| Inspection Report | Inspector | September 12 | Missing |
| Financing Update | Lender | September 18 | Pending |
| Title Documents | Title / Escrow | September 20 | Received |
| Amendment 1 | Buyer / Seller | September 16 | Signed |
| Closing Disclosure | Lender / Closing Team | September 22 | Pending |
| Final Closing Documents | Closing Team | September 24 | Missing |
Transaction Tracker
| Milestone | Date | Status | Source |
|---|---|---|---|
| Inspection | September 12 | Missing | Client tracker |
| Financing Update | September 18 | Pending | Client tracker |
| Amendment 1 | September 16 | Signed | Client tracker |
| Closing Disclosure | September 22 | Pending | Client tracker |
| Closing | September 25 | On Track | Client tracker |
Second Date Source
A separate transaction document contains: Closing Date: September 27. The client tracker says: Closing Date: September 25. No instruction explains which date should be treated as current.
Transaction Folder
├── Contract & Agreements/
│ ├── Purchase-Agreement-Signed.pdf
│ ├── Amendment-01-Signed.pdf
│ └── Amendment-01-Draft.pdf
├── Disclosures/
│ └── Seller-Disclosure.pdf
├── Inspections/
│ └── [empty]
├── Financing/
│ └── Financing-Update.pdf
├── Title & Closing/
│ ├── Title-Documents.pdf
│ └── Closing-Disclosure-Draft.pdf
├── Communications/
│ └── Sarah-Email.pdf
└── Tracking/
└── Transaction-Tracker.xlsx
The Amendment-01-Draft.pdf appears to be an older version of the signed amendment. The folder also contains Financing-Update.pdf — the tracker says the financing update is still pending, and you do not know whether the file is the current approved financing update or an earlier document.
Additional Information
Sarah's email does not specify who should be contacted about the missing inspection report, whether the Financing-Update.pdf is the current document, whether the September 25 or September 27 closing date is correct, or whether the final closing documents have been requested. These gaps are part of the exercise.
Your Task
- Review the transaction checklist.
- Review the transaction folder.
- Identify missing documents.
- Identify misplaced or questionable files.
- Identify outdated or potentially outdated versions.
- Identify conflicting dates.
- Identify the financing-document discrepancy.
- Determine which items can be acted on.
- Determine which items require clarification.
- Determine which items require verification.
- Determine which items require escalation or client decision.
- Organize the transaction folder.
- Update the document checklist.
- Build or update the milestone and deadline tracker.
- Create a combined missing-document and follow-up queue.
- Prepare the transaction status tracker.
- Draft the two transaction-specific communications.
- Add appropriate issues to the Running Exception & Escalation Log.
- Prepare a final transaction status report using the Standard Status Report Template.
- Apply the transaction confidentiality principles throughout the exercise.
The exact wording of your response may differ from the answer guide — what matters is whether it demonstrates the correct workflow and judgment.
Knowledge Check
10 questions. You can retry as many times as you like.
Portfolio Evidence
The items below are components of the single Transaction Support Tracker portfolio artifact — not separate certification submissions.
Transaction Folder, Document Checklist & Milestone/Deadline Tracker
A clean transaction support workspace demonstrating that you can organize transaction documents, distinguish current and older versions, identify missing documents, track transaction milestones, record authorized dates, identify conflicting information, and document unresolved issues.
Combined Missing-Document & Follow-up Queue
One combined queue: missing items, pending items requiring follow-up, responsible party, due date, current status, last follow-up, next action, escalation status where applicable.
Transaction Status Tracker
Using client-defined status categories — On Track, Waiting, Needs Attention, At Risk, Completed — applied per the supplied client definitions, not personal judgment.
Two Transaction-Specific Communication Templates
Retain the two templates created in Lesson 6.7 — Missing Document / Follow-up, and Transaction Status Update. Do not create four new transaction communication templates.
Running Exception & Escalation Log
Add the appropriate Module 6 issues to the existing course-wide log — conflicting closing dates, uncertain document version, unresolved financing-document status, unclear follow-up responsibility, professional decisions requiring client attention. This is a cumulative course artifact; do not create a separate Module 6 escalation log.
Final Transaction Status Report
Using the Standard Status Report Template — Completed, Pending, Follow-up, Needs Clarification, Needs Client Decision, Issues/Escalations, Next Actions.
The strongest portfolio evidence is organized, traceable, and easy for another person to review. The goal is not to demonstrate that you can independently manage a real estate transaction — the goal is to demonstrate that you can provide dependable administrative support within a client's transaction workflow.
Quick Glossary Update
Continue building the Real Estate Support VA Quick Glossary introduced in Module 1. Consider adding terms introduced in this module:
Where a term or process may vary by state, brokerage, transaction type, or client, note that variation. The Quick Glossary remains a required learning artifact, but it is not part of the certification portfolio.
Assessment Focus
- Transaction workflow understanding
- Document organization
- Checklist management
- Milestone tracking
- Deadline tracking
- Missing-document management
- Follow-up
- Transaction status
- Communication
- Exception handling
- Act / Clarify / Verify / Escalate
- Confidentiality
- Version control
- Professional boundaries
- Documentation
Tools & Industry Context
Google Drive, Google Docs, Google Sheets, Gmail, Google Calendar when scheduling or deadline reminders are relevant. Industry systems may include transaction management platforms, brokerage systems, e-signature systems, title or escrow systems, lender systems, MLS or other real estate systems — included as industry context. You do not need paid transaction-management software to complete this module. The course focuses on the workflow: Document → Track → Follow Up → Verify → Communicate → Escalate. The specific software may change from client to client.
Not Taught in This Module
Contract interpretation, legal advice, negotiation, licensed transaction coordination, independent transaction coordination as a professional role, financing decisions, loan qualification, property valuation, appraisal, inspection interpretation, title or legal interpretation, professional real estate decisions, sales, advanced transaction management. Transaction coordination is included only as administrative support — the course does not train the learner to independently act as a Transaction Coordinator.
Completion Standard
You have completed Module 6 when you can take a transaction folder and tracker and: understand where the transaction sits in the workflow, organize documents using the client's structure, maintain a document checklist, identify missing and pending items, recognize outdated or uncertain document versions, track milestones and deadlines from authorized sources, identify conflicting dates without guessing, manage follow-ups, maintain transaction status using client definitions, communicate transaction status clearly, apply Act/Clarify/Verify/Escalate, document exceptions in the cumulative log, handle transaction information responsibly, and recognize when a matter requires professional judgment or authority.
The goal is to become a dependable administrative support VA who can help keep transaction work organized, visible, and moving without taking over decisions that belong to the client or another qualified professional.