A working guide to where an in-house real estate legal team's hours go, and how to get them back. Separate the reading from the deciding, measure it in your own numbers, write your positions down, and know what to build first. The lawyer decides on every page.
Switchboard · withswitchboard.com · Book a call: withswitchboard.com/book-a-call
A working guide to where an in-house real estate legal team's hours go, and how to get them back. Separate the reading from the deciding, measure it in your own numbers, write your positions down, and know what to build first. The lawyer decides on every page.
From Switchboard. We map how a team actually spends its week, then build the software around the reading.
A working guide to where an in-house real estate legal team's hours go, and how to get them back. Written for the lawyer who runs the team.
Which part of the week is reading and which part is deciding, what the reading costs in your numbers, how to write your positions down, and how to test any tool on a real lease.
Run your numbers first. Then read with your own team in mind. Every section has a piece you answer. The curve tells you your next move.
The parts of this page you fill in, as a file your team can open on Monday: the calculator, a positions document template, and the two-week first-read audit with its totals wired to the calculator. A one-page guide comes in the same download.
Four sliders: leases you touch, the share on the tenant's paper, hours per first read, and the cost of that hour. The output is hours, and hours turned into a number your COO or CFO already understands.
Four inputs: leases you touch, the share on the tenant's paper, hours per first read, and the cost of that hour. The output is hours, and hours turned into a number your COO or CFO already understands. The interactive page runs it live; the numbers below are what a typical team gets.
On a typical team: 12 leases and amendments a month, half of them on the tenant's form, four hours of first read each.
The four-hour figure is RSM's benchmark for abstracting one real estate lease, plus an hour of review. Your own numbers go into the calculator on the interactive page, or into the first tab of the workbook.
The calculator priced one loop, the first read. It is the biggest of four loops that every in-house real estate legal team we talk to runs, whatever the asset class and whoever the tenants are. Tenant paper comes in and someone reads it against the company's positions. Leasing asks what was agreed to years ago, and the answer is spread across the lease, two amendments and an old email thread. A dispute, an estoppel or a CAM reconciliation lands, and the work starts with finding what both sides actually signed. Underneath all of it sit the renewal windows and consent deadlines that cost real money when they slip.
In every one of those loops, the reading takes most of the hours and the deciding takes the last few minutes. The drawing below has the shape of it, and the calculator above has your numbers.
The widths are the shape of the work, not a measurement of yours. The teal end needs a lawyer. The blue part needs a reader.
Your turn. Which loop took the most hours at your company this quarter?
None of this is a real-estate-only problem, and the industry-wide numbers say why it's getting heavier.
Read together: the team isn't getting bigger, the reading is the biggest block of hours that doesn't need a law degree, and the teams that moved got hours back with a lawyer still in control. That is the case for moving. What follows is how, without handing a single decision to software.
Think of the paralegal who reads the whole file and leaves a tab on every page you need to see. Nobody lets the tabs sign.
General counsel tell us the same thing: leases are too bespoke, and the liability too high, to hand any of it to software. Agreed, for the judgment. Nobody should let a model decide what the company will sign. But "software" covers two very different jobs.
So picture a piece of software built for your team and nobody else's. You hand it a tenant's lease and the positions your company holds. It reads all 84 pages, marks every place the tenant departs from what you've written down, and shows you the page each mark came from. Then it stops. That is a system: a reader that stops at the line.
A review layer built for your team, drawn. It reads all 84 pages of the tenant's form and leaves a tab on every departure from your positions. The tabs stop at the line. The lawyer starts there, and nothing to the right of the line is software's to touch.
Now look at the four hours before the decision. Finding every clause where the tenant's form departs from your positions. Pulling the operative text of section 8 after three amendments. Checking a tenant's estoppel redline against what the file actually says. None of that is a judgment call. All of it has to happen before one can be made.
The line between the two is the most useful thing a legal team can draw. On one side, work a system can do and show its sources for. On the other, work only a lawyer can do, and only a lawyer should.
"Leases are too bespoke, and the liability is too high, to hand any of this to software. I sign off. I carry it."
The system never decides. It reads and flags. Every redline still goes through a lawyer. What it removes is the four hours of page-turning before the lawyer gets to decide anything. And every flag cites the page it came from, so you check the source, not the software.
1 of 8 · You draw the line
A positions document is the one page every first read gets checked against. For each lease term tenants push on, it says what the company will agree to, what it will not, and the fallback it offers before walking away. Many legal teams carry it in two attorneys' heads: ask what the company gives on a CAM cap and you get an answer, ask for the document and you get a pause.
Writing it down is the first step, and everything after it depends on it. It is what lets a new attorney redline a tenant's form without asking anyone. It is what keeps redlines consistent across the team. And it is the ruler any software would read against: without it, a system has nothing to compare a lease to, and the first read stays a lawyer's job by default.
Below is what one looks like, three rows of it. Then you can watch what a system does with those three rows when a tenant's form arrives. The workbook's second tab is the template for writing yours.
Three rows from a positions document, and a fourth left open. Yours will differ; the shape won't. Note the assignment row: a deemed-consent clause is a clock, and this document is where you decide how it runs.
Now watch it read. Pick a clause from a tenant's form and see what a system checks it against, and what it hands the lawyer.
We will
We won't
Fallback
Forty seconds or four hours for that call: the difference is which of four Mondays your team is living.
Every in-house real estate legal team sits somewhere on this four-stage curve, and no stage is a judgment on the team; most of the field is on the first two. The drawing shows the same tenant lease being handled four ways. Then mark the Monday that sounds like yours and the card answers with your next move, which is never "buy everything."
Every in-house real estate legal team sits somewhere on this four-stage curve, and no stage is a judgment on the team; most of the field is on the first two. The drawing shows the same tenant lease being handled four ways. Find the Monday that sounds like yours. Each stage carries its next move, and it is never "buy everything."
The same tenant lease arrives in all four. In the first it waits for the one person who knows the positions. In the last, the flags are on the pages before the lawyer opens it. The cards below say which Monday is yours, and what the next one takes.
Monday looks likeThe positions are known, not written. Leases live in a folder. Dates live in a calendar and in one paralegal's memory. Every first read starts from page one.
The next moveWrite the positions down: for each term tenants push on, what you will give, what you won't, and your fallback. One page, this week. Nothing else on the curve works until it exists.
You've outgrown it whenA new attorney can redline a tenant's form without asking anyone what the company will accept.
Monday looks likeA positions document and a review checklist exist. The lease system belongs to accounting and legal is a data supplier to it. The first read is still four hours of a lawyer's Monday.
The next moveMeasure the reading: two weeks of logging minutes reading and minutes deciding, per document. That number is what gets the next stage funded.
You've outgrown it whenYou can answer "what did we agree to" from a record, not from a hunt.
Monday looks likeEvery lease family is one resolved record: the operative text of each clause, citing its document and page. Dates and the notices behind them come off that record. So does the first draft of an estoppel.
The next movePut the first read on the same record. The positions document is the ruler; the system does the comparing and returns the flags.
You've outgrown it whenAn estoppel is a draft to sign, not a document to assemble.
Monday looks likeTenant paper arrives and a redline with ranked flags is waiting. Each flag names the position it departs from and the page it sits on. The lawyer starts at the flags and decides. Every deviation agreed to is logged.
The next moveDepth. The same record now serves consents, disputes and notices. The deviation log starts showing which positions you actually hold.
You're doing it right whenEvery flag can show the page it came from, and no decision has ever been made by the system.
You climb this curve one loop at a time, and stage 4 is only reachable from stage 3. Software reading against positions nobody wrote down is noise. Software reading against a resolved record and a written document is a redline.
Two things to do before you talk to anyone, including us. Both cost nothing, and both leave you with something: a number nobody in the company has seen, and the seven questions that tell you in ten minutes what you are being shown.
For two weeks, every document that gets a first read gets a row: what it was, how many pages, who read it, minutes reading, minutes deciding. The split between those two minutes columns is the finding, and it's the number that starts a budget conversation.
Four rows of a real week, drawn from the four loops. The two minutes columns are the whole point. After two weeks, add them up and the sliders at the top of the page stop being defaults.
Most of what a real estate legal team gets shown falls into four categories: lease abstraction, which reads the leases you already signed; lease accounting, which belongs to the controller; lease drafting, which speeds up your own form; and generic contract review, built for NDAs and MSAs. Each is good at its job. None of them reads the paper you didn't draft against the positions you hold, and these seven questions are how you find that out in the first ten minutes of any conversation.
Ask us the same seven. The answers are the review layer described above, and a Jumpstart is where you check them on your own paper.
What the first read costs your team, with the inputs you set. Adjust them any time and this follows.
That is what the first read costs while nothing changes. Below is where software built for your team would land in the four loops, then what working with us on it looks like.
Where custom software lands in your week. Pick a loop; the one you said takes the most hours is already open.
Switchboard maps how a team's week actually runs, then builds the software around the reading. Custom software, with AI where the reading is and a lawyer at every decision. We build the review layer, the software that reads a lease against your positions and hands the lawyer a redline with the flags already on it, around your own paper.
The way in is the AI Jumpstart: fixed scope, fixed price, two to four weeks for one workflow. For a legal team that workflow is almost always the first read. We ask for read access to how the work runs today, and workshops with the lawyers who do it. Nothing migrates and nothing in production is touched. If you build with us afterwards, the same team carries it through the AI Deployment Studio, as a project or a retainer.
The person marks the two weeks your team carries; the spark marks the four steps we hand back. Your current folder, calendar and lease system run untouched the whole time.
Everything above is yours. The map, the audit, the prototype, the plan, whether or not you build with us. And your positions document is the ruler all of it measures against.
Twenty minutes. No deck. A conversation about which loop takes the most hours at your company, and what mapping it would look like. Bring whoever owns the budget. Book a call: withswitchboard.com/book-a-call
This playbook also lives as an interactive page, with a calculator for your own numbers and a downloadable workbook: the calculator, a positions document template, the two-week audit sheet, with a one-page guide. withswitchboard.com/playbook/legal-real-estate
Twenty minutes. No deck. A conversation about which loop takes the most hours at your company, and what mapping it would look like. Bring whoever owns the budget; two weeks of your team's own minutes does the talking.
Book a call