SYSTEM 06 OF 14 DELIVER WELL
Transaction.
Keep promises from contract through closing without relying on anyone's memory.
Put each contract-to-close commitment where its source, owner, and next action can be verified.
View all 14 systems01 / READ
The Transaction chapter
Start with the reason this system matters before choosing another tool or cadence.
We had a listing in a market that was not especially strong for sellers. The home had been priced above what buyers were willing to pay, so it sat for a while. The seller eventually accepted less than she had hoped for and was close to the minimum she felt she could take. Then the inspection came back with a substantial list of requests. She felt she had already given enough. It looked as though the deal might fall apart.
Then the buyer's broker sent us the inspection response along with the inspection report. That mattered. As I understood the forms governing our transaction, the way those documents were delivered changed our position in the negotiation. We were able to hold to the minimum price my seller needed rather than make the additional concessions the buyer had requested. The transaction stayed together.
I do not tell that story as a clever technicality or as a rule to apply to every inspection. The buyer's broker was not trying to hurt their client, but I believe the way the documents were handled cost that buyer negotiating leverage. A detail that looked procedural affected the clients on both sides. What I learned was that the paperwork was not separate from the negotiation. In that moment, the paperwork was the negotiation.
That is why Transaction is not administrative work after the “real” work is done. The agreement, current forms, deadlines, delivery, handoffs, and next owner all matter. When something is unclear, stop and verify it. Do not rely on memory or assume someone else has it handled.
Start by finding the next promise
At acceptance, put the signed documents in the brokerage's transaction system. Read the actual agreement and confirm the people, milestones, deadlines, and responsibilities. Name the owner of each next move, including who will explain it to the client. Set reminders early enough to act. A coordinator can manage details, but the agent still needs to know what has been promised.
Tell the client what comes next, what they may need to do, and when they will hear from you. Then review upcoming milestones, missing information, and unanswered questions before they become surprises. If something changes, say what you know, what you do not know yet, who is working on it, and when you will update them again. Do not promise an outcome you cannot control.
If a deadline, document, or contract question is unclear, verify it with the current forms and the right people before acting. A checklist cannot interpret an agreement. If a problem threatens a milestone, raise it early through the brokerage's process and record what was decided and communicated. At closing, confirm the final handoff and any unanswered questions. Then make sure Follow-Up carries the relationship forward. Buyer or Seller still owns the client relationship; Transaction keeps the contract-to-close work from slipping.
Review the handoff, not just the closing date
On an ordinary day, the team should be able to see the next milestone, owner, due date, open question, and last client update. The client should know the next step and whom to ask. Each week, count upcoming milestones with no owner or early reminder. Pair that with whether promised client updates and answers arrived when you said they would. Closing on time does not prove the client felt informed. A delay does not automatically mean the system failed. But repeated late surprises mean a handoff needs to change.
The goal is to stop using memory as the only safety net. The actual contract and brokerage workflow remain the source of truth. The Field Guide helps the team run and improve that process without copying the transaction into another tracker.
02 / START
Start Here This Week
One useful first pass in the tools you already use.
Starting condition: a contract-to-close milestone can sit in someone's memory without a clear owner or early reminder.
This week's result: the next milestone in one current transaction has a verified source, owner, reminder, and client update plan.
- Open one current transaction in the brokerage-approved platform. If none is active, inspect the approved workflow with a clearly fictional practice case; do not create a live deadline from a sample.
- From the signed documents and approved process, identify the next actual milestone and the people affected. Verify the date rather than copying an illustrative timeline.
- Name the action owner, the earlier reminder, and who will explain the next step to the client. Record these in the approved system.
- Check for one missing document, answer, or handoff that could affect the milestone. Escalate it through the brokerage's normal path if needed.
The next milestone in one current transaction has a verified source, owner, reminder, and client update plan.
Check marks are for this visit only. Make the real changes in your existing tools.
03 / FIELD GUIDE
Contract to Close Promise Check
Configure, use, and improve the existing workflow. This page does not become another database.
Job: keep actual contract commitments, responsibilities, and client updates visible until closing. Users: agent, transaction coordinator, and authorized brokerage team. Trigger: acceptance, every milestone change, regular look-ahead review, and closing handoff. System of record: signed documents and brokerage-approved transaction platform. This tool is a configuration and exception check, not a duplicate transaction file.
BUILD
The workflow around actual documents
| Rule to configure in the approved platform | Your brokerage process or owner |
|---|---|
| Who verifies the signed agreement and current addenda before dates are entered? | |
| Where do actual milestones, deadlines, owners, and early reminders live? | |
| Who checks that a delegated task was accepted and completed? | |
| How are missing information and deadline risks escalated? | |
| What is the client update cadence, and who sends the next update? | |
| How are final handoff, open questions, and post-close relationship ownership confirmed? |
Example rule, not a contract timeline: the agent or designated coordinator verifies the next milestone against the executed agreement, assigns an owner, and places an early reminder in the approved platform. A sample day-zero or thirty-day schedule is never the source of a legal deadline.
RUN
A look-ahead and exception review
At acceptance, check documents, parties, dates, and first client update. At each regular review, open the transaction platform and look ahead to the next actual milestones. Work the exceptions below there; do not recopy every transaction into this guide.
| Exception to surface | Decision and record needed in the approved system |
|---|---|
| Milestone lacks a verified source, owner, or early reminder | Verify the document, assign the owner, and set the reminder. |
| Required document or answer is missing | Name who obtains it and by when; tell the client what affects them. |
| Partner or delegated task has no acknowledged handoff | Confirm receipt and next action with the responsible party. |
| Deadline or outcome is at risk | Escalate through brokerage process; record decision and next update time. |
| Client update promised but not sent | Send an accurate update or revise the promise with a clear reason. |
| Closing or possession handoff remains unclear | Confirm with the appropriate parties before declaring the file complete. |
| Fictional exception | Owner | Next action and due date | Client update plan |
|---|---|---|---|
| Appraisal timing not confirmed | Transaction coordinator | Ask lender for status by Tuesday | Agent updates client Tuesday, including uncertainty |
LEARN
From repeated surprises
| Review period | Repeated exception or late surprise | Where the handoff failed | One workflow change | Owner/date to verify change |
|---|---|---|---|---|
| Fictional example | Partner updates arrived after client asked | No owner for status check | Add named weekly partner check to approved workflow | Coordinator / next transaction |
After closing, compare what the team expected with what actually caused uncertainty. Was the date entered late, the owner missing, or an external answer simply unavailable? Change the process only for a pattern you can identify. Do not score a team from closing speed alone or use this worksheet to interpret contracts.
