Your Transaction Coordinator Opens Monday With 41 Files. Overnight Agents Now Hand Her 6 Exceptions Instead.

It is 8:15 on a Monday morning at a three-office brokerage outside Raleigh. Dana, the transaction coordinator, has not taken her coat off yet. Dotloop is open on one monitor, the MLS on the other, and there are 41 files sitting in some version of "under contract." Six of them close Friday. She does not yet know which six are the ones in trouble.

Nobody puts this job on a recruiting flyer. And yet the file review is exactly where a brokerage gets fined by its MLS, cited by the state real estate commission, or held up at a closing table with a wire deadline ticking.

The 8:15 pile is a liability list, not a to-do list

Open any transaction coordinator's checklist in the United States and you find roughly the same two dozen items, whatever software the office runs on: fully executed purchase contract on the state association or state commission form, a buyer representation agreement dated before the first showing, seller's disclosure notice with every page initialed, the lead-based paint disclosure on anything built before 1978, agency or intermediary disclosure, the wire fraud advisory, the third-party financing addendum with the right number of days on it, the earnest money receipt from the title company, the inspection amendment, a W-9 for any referring agent, and the commission disbursement authorization the title company will not fund without.

Miss one and nothing happens for three weeks. Then it all happens at once, usually at 4:40 p.m. on the day of closing, with an agent calling the managing broker's cell from the title company parking lot.

The workaround every brokerage pretends is fine: the coordinator triages by closing date. Files closing this week get looked at; files 30 days out get looked at when they become files closing this week. So a missing initial on page 4 of a seller's disclosure sits undiscovered for four weeks, and the fix has to be chased through an agent at a listing appointment, a seller in another state, and a title company that closes at five.

What actually changed: agents that keep working after the office lights go off

An overnight back-office agent is software you give a standing goal to — "review every open file against our broker checklist" — that works through your transaction folders while the office is closed and leaves behind a sorted queue with the exceptions already flagged for a human to sign. That is the whole idea, and until this year it did not really work.

The change is not that the software got smarter at reading a contract. It is that it can stay on task for hours without a person babysitting it. Claude Cowork landed on 12 January 2026, built for people who are not developers: you hand it a goal and it moves across your apps and files and comes back with finished work. ChatGPT Work followed on 9 July 2026 on GPT-5.6, and its whole pitch is that it accepts a goal and runs on its own for hours before returning finished work. Claude Opus 4.6 got roomy enough to take an entire transaction folder at once — contract, addenda, disclosure packet, email thread — instead of slices.

For a brokerage, "runs on its own for hours" is the whole story. Forty-one files is not a two-minute reply. It is six hours of patient, boring comparison work — and that can now happen between 6:30 p.m. and 7:45 a.m.

flowchart TD
  A["6:30pm — office closes, 41 files open"] --> B["Agent reads the Dotloop and SkySlope folders"]
  B --> C["Compares each file to the broker checklist"]
  C --> D{"Every required document executed and dated?"}
  D -->|Yes| E["File marked clean, CDA drafted for broker signature"]
  D -->|No| F["Exception written: missing initial, wrong deadline, unsigned page"]
  E --> G["7:45am queue: 35 clean, 6 exceptions, ranked by closing date"]
  F --> G
  G --> H["Coordinator works exceptions, managing broker signs"]

Tuesday morning, replayed with the queue already sorted

Dana opens her laptop at 8:15. Instead of 41 folders she has one page. Thirty-five files are marked clean and dated. Six carry exceptions, ranked by closing date, each written in the office's own language rather than in software-speak:

• 412 Oakhurst — seller's disclosure notice: page 4 initialed by one seller, property is titled to both. Closes Thursday.
• 7 Camden Ct — built 1961, no lead-based paint disclosure in the folder at all. Closes in 19 days.
• 1180 Fairbanks — third-party financing addendum says 21 days, contract execution date makes that deadline yesterday. Nothing filed.
• Unit 306 Warehouse Row — earnest money receipt from title never came back; contract says three days, it has been six.
• 88 Pine Ridge — MLS still shows Active, contract executed Friday afternoon. Your MLS wants a status change inside two business days.
• 1442 Sequoia — commission disbursement authorization drafted, needs the managing broker's signature; referring agent's W-9 is missing.

Three of those six also arrive with a drafted email to the right person — the agent, the co-op agent, the title closer — sitting unsent. Dana is not composing from scratch at 8:15. She is approving or rewriting.

The 88 Pine Ridge line matters more than it looks. A late status change is the most common MLS violation in residential brokerage, and MLSs fine for it. Whether your schedule says $100 or $500, you are paying it for forgetting a two-click job on a Friday afternoon.

The arithmetic on one transaction coordinator

Assumptions, all illustrative — put your own numbers in the same shape:

The $1,500 is the least interesting number in that table. The interesting one is 59 hours a month of coordinator capacity. At roughly 35 open files per coordinator, that is the difference between hiring a second transaction coordinator at your next growth spurt and not hiring one — the hire you were going to make in a panic in April, when the spring listing surge pushes your open file count well above January's, and lay off in November.

How you prove it: for one month, log every exception the agent finds and the day of the contract it found it on. If the queue surfaces on day 3 what you used to find on day 26, you have your answer.

Where you keep a human, and where you keep the broker's signature

Three lines are worth drawing in permanent ink.

First, the commission disbursement authorization gets drafted by software and signed by a licensed broker. The CDA is the instruction that moves money to your agents and your house account. Let the agent prepare it and reconcile it against the ALTA settlement statement; do not let it be the last thing that touches it.

Second, anything that is a judgement call about representation stays with the managing broker. "Is this addendum sufficient" and "did this agent disclose properly" are licensed judgements with a state commission at the end of them, not checklist items. The agent should flag and stop.

Third, it cannot fix a file that was never built. If your agents dump documents into the folder haphazardly, the agent will faithfully report chaos every morning. Fix the intake habit first.

One more honest limit: handwriting. Initials on a scanned page and a repair amount written in the margin of an inspection amendment are still where these systems make their mistakes. Treat handwritten changes as automatic exceptions and read them yourself.

The Monday-sized first step

Do not start with 41 live files. Take your broker file-review checklist — the real one your compliance reviewer uses, not the one in the policy manual — and pick the six items that generate the most late-week fire drills. Point an overnight agent at last quarter's closed files and ask it to find every instance of those six missing or wrong. The money has already moved on those, so nobody is under pressure and you can judge the accuracy honestly. If it catches things your team missed, run it forward on live files.

Frequently asked questions

Will this work if we run SkySlope and our back office is on Lone Wolf?

Yes, and that split is the normal case rather than the awkward one. The agent reads the transaction folder where the documents live and reconciles against the back-office ledger where the money lives — precisely the job people do by hand today, tabbing between two windows. What matters is that access to both is granted deliberately, not by handing over a shared password.

Our compliance reviewer is part-time and reviews files only after closing. Does this change that?

It should. Post-closing review tells you what went wrong after you can no longer fix it — useful for training, useless for the file. An overnight review moves the same checks to day 2, when a missing lead-based paint disclosure costs one email instead of delayed funding. Keep the post-closing review; just stop letting it be the first one.

What happens with the files that are quiet — no activity for two weeks?

Those are the ones this catches best, and they are the ones humans triage last. A file with no document activity, no MLS status change, and an option or financing deadline inside seven days is the highest-risk file in the office and the least likely to be looked at. Ask the agent to surface silence, not just errors.

Do we have to tell our agents this is running?

Tell them. An agent who discovers a system has been reading their transaction folder unannounced will assume the worst about why. Frame it as it actually is — exceptions land on the coordinator's desk, not on a scoreboard — and add it to the independent contractor agreement or office policy manual at your next update.

A related note, since it is the other half of the same morning: a lot of what lands on the coordinator's desk arrives as a phone call — the co-op agent chasing a signature, the title closer confirming a figure, the buyer asking when the walkthrough is. CallSphere builds AI voice and chat agents that answer a brokerage's phone line and web chat around the clock, book appointments, and capture leads, so those calls arrive as logged, routed messages rather than as thirteen voicemails competing with the exception queue. It does not review your files — that is the overnight agent's job — but it stops the phone from undoing the sorting.