By Keith Dunham, Founder & CEO of Empower Transactions.
Most broker-owners put compliance review at “a few minutes a file, it’s a checklist.” We run that checklist for a living, and in July 2026 we clocked it. Across 3,816 compliance files, our reviewers spent 0.97 labor-hours per file. Not a few minutes. About an hour.
Broker compliance review is the step where someone reads a closed or closing transaction file against the state’s required documents and the brokerage’s own standard, and returns what is missing, unsigned or out of date to the broker of record. This piece puts the numbers behind that step in one place, with the method: what it costs in labor, how much of it one reviewer gets through in a day, and why the checklist a broker imagines is not the checklist that exists.
Key takeaways
- A broker compliance file took 0.97 labor-hours in July 2026 (3,816 files; compliance line only; one month). That works out to about 179 files per full-time reviewer per month.
- A reviewer handled a median of 113 documents and 17 transactions a day across 633 reviewer-days this summer. The logs are self-reported, so read it as the shape, not the decimal.
- A transaction carried 6.19 documents on average (n = 628). The reading is minutes; the hour is everything around it.
- Of the 309 required-document entries our manifest currently carries, 66 percent are conditional, meaning they apply only when something else in the file is true, and only 6.5 percent are federal. Four states are codified so far; that is what has been standardized, not where the work runs.
- For a brokerage closing 80 sides a month, compliance is roughly half a full-time person before recruiting, ramp or coverage. At 30 sides it is a sixth of one, which is why it ends up nobody’s job.
How long does broker compliance review take per file?
0.97 labor-hours per file. That is the July 2026 figure from Empower Transactions’ own time clock: every hour booked to the broker-compliance line, divided by every compliance file completed in the month.
Before using it, know what it is and what it is not. First, it is one complete month and one service line, not a blended number across transaction coordination or intake, which run differently. Second, one implausible timesheet was left in rather than trimmed, because trimming it would have flattered the number; excluding it gives 0.79 hours a file. Somewhere between those two is the honest range, and 0.97 is the conservative end.
Turned around, 0.97 hours a file is about 179 files per full-time-equivalent reviewer per month, counting a full-time month as 173 working hours (2,080 a year). A broker sizing an in-house seat can use that directly: divide monthly closings by 179 and you have the fraction of a person the review consumes before anything else that person does. The larger version of that decision is worked through in Scaling a Brokerage Without Hiring Admin Staff.
How many documents does a reviewer get through in a day?
A median of 113 documents across 17 transactions. The mean is a little higher, 121 documents and 19.7 transactions, pulled up by heavy days.
That comes from a different instrument than the hour figure and should not be multiplied against it. It is our reviewers’ end-of-day reports across 633 reviewer-days from June 3 to August 21, 2026: what each person logged touching, not what the system counted. A file that needs a second look on Thursday appears on Thursday’s count too. Read it as throughput, not as files closed.
What it does say is that the reading is not the bottleneck. A hundred-plus documents a day is a fast pace for anyone; if that were the whole job, an hour a file would not survive. The hour comes from what the documents trigger.
How many documents are in a transaction file?
About six. 6.19 documents per transaction on average across the same 628 reviewer-days that recorded both counts; 6.83 if you take the median of each day’s ratio instead. Which method you use matters less than the range: a transaction file is not a two-hundred-page binder, it is a contract, a handful of addenda, a disclosure or two and the paperwork the deal itself set off.
Six documents in about an hour is not a reading rate. It is what the chasing costs: the missing page, the wrong-year form, the agent who says it is coming, the second email, the third. The chasing is the labor.
Why is the compliance checklist not a checklist?
Because two-thirds of it is conditional.
Our requirement manifest currently carries 309 required-document entries: Texas 178 (the categories are laid out in Texas Transaction File Requirements), Missouri 51, Kansas 51, Florida 29. Four states are codified so far; that is what has been standardized to date, not where the work runs, and Empower Transactions operates nationwide. Of those 309 entries, 204 are conditional: they apply only when something else in the file is true. An HOA addendum when there is an HOA. A septic disclosure on septic. A backup addendum when there is a backup offer. Only 20 of the 309, or 6.5 percent, are federal and the same everywhere; the rest change at the state line.
The state line is the structural reason an hour is an hour. A reviewer is not ticking boxes; the reviewer is deciding, file by file, which boxes exist. And it is why a brokerage in one state trains against roughly 77 entries while a brokerage in six is looking at something closer to 460. That is a curriculum, not a checklist.
The honest limit on this one: none of the 309 entries has been signed off by an outside subject-matter expert. It is our manifest as we run it, and four states is a thin base for a per-state average. Treat it as the shape of the problem, not a certified count. Not legal advice.
What does this mean for a brokerage sizing its back office?
Run the arithmetic with your own closings.
| Closings a month | Compliance labor at 0.97 h/file | Share of one full-time reviewer (179 files/month) |
|---|---|---|
| 30 | about 29 hours | 0.17 |
| 50 | about 49 hours | 0.28 |
| 80 | about 78 hours | 0.45 |
| 120 | about 116 hours | 0.67 |
Read it this way. At 30 sides a month, compliance is a sixth of a person, which is why it becomes one more job for whoever already has five. At 80 it is half a person, which is the point where it starts slipping in a good recruiting month, because onboarding spikes exactly when recruiting works and file review has a closing date that does not move. And at any volume, the window is short: median time from intake to closing in our data is 21 days (n = 554), with a quarter of files closing inside 11. That is the window every exception has to clear in.
The seat this labor is measured against costs what it costs. The BLS median for office and administrative support occupations was $47,450 in May 2025; at the employer burden BLS reports for the category, a fully loaded seat lands near $69,100 a year before recruiting time, ramp or coverage (the full comparison is in In-House vs Outsourced Operations Cost). Whether that seat, half of it, or a per-file arrangement is the right answer is a margin decision, not a service decision, and the hour is the number that decision was missing.
Method
Labor-hours per file: Empower Transactions billing time clock, July 2026, broker-compliance line only; 3,683.2 hours booked against 3,816 distinct files completed. One complete month. Full-time month taken as 173 hours (2,080 a year). One implausible timesheet retained (conservative); excluding it, 0.79 h/file. Throughput: reviewer end-of-day reports, 633 reviewer-days, June 3–August 21, 2026; self-reported, not system-counted; a file touched on two days counts on both. Documents per transaction: same reports, 628 days recording both counts; 6.19 by aggregate ratio, 6.83 by median of daily ratios. Requirement manifest: 309 entries across four codified states as of August 2026; 204 conditional, 20 federal; none expert-ratified. Intake to closing: 554 usable date pairs of 721; 23 percent entered retroactively and excluded. Wage benchmark: BLS Occupational Outlook Handbook, office and administrative support occupations, May 2025 median; employer burden from the BLS Employer Costs for Employee Compensation series. What this does not prove: anything about accuracy, defect rates, or how these numbers compare to an in-house team’s. We did not measure those, and we will not publish them until we have.
What 0.97 hours a file means for staffing, including how many files one full-time compliance officer can cover, is worked out on real estate compliance officer.
Frequently asked questions
How long does broker compliance review take per file?
About an hour. Empower Transactions’ July 2026 time clock came to 0.97 labor-hours per compliance file across 3,816 files: one month, compliance line only, with one implausible timesheet left in. Excluding it, 0.79 hours.
How many files can one compliance reviewer handle in a month?
About 179 per full-time-equivalent reviewer at 0.97 hours a file. Divide your monthly closings by 179 for the share of a person the review consumes before recruiting, ramp or coverage.
How many documents are in a real estate transaction file?
About six on average, 6.19 documents per transaction across 628 reviewer-days in summer 2026, 6.83 by median of daily ratios. The count is self-reported at end of day.
Why does compliance take an hour if it is only six documents?
Because the reading is minutes and the follow-up is the hour: the missing page, the wrong-year form, the agent who has not uploaded, the second and third message. Two-thirds of required documents are also conditional, so the reviewer decides file by file which ones apply.
Are these numbers the same in every state?
The hour is Empower Transactions’ own blended figure and will vary by state and file mix. The requirement manifest is codified for four states so far (Texas, Missouri, Kansas and Florida), and Texas alone carries 178 of the 309 entries. Empower operates nationwide; four states is what has been standardized to date. Not legal advice.
What the review itself covers, per file, is described on Broker File Review.