What Happens When Your Best Leasing Attorney Leaves

Sarah has been with your company for 15 years. She built the lease templates. She knows why every clause is phrased the way it is. She remembers the dispute in 2015 that caused you to revise the co-tenancy language. She knows which fallback positions are acceptable and which are non-negotiable.

Sarah gives two weeks' notice.

The Template Archaeology

The retail lease template has 47 clauses. Sarah knows the history of 40 of them:

• Which provisions were added after disputes
• Which came from outside counsel recommendations
• Which reflect business decisions that may no longer apply
• Which are genuinely mandatory vs. "we've always done it this way"

Without Sarah, the template becomes an artifact without explanation.

The Negotiation Playbook

Sarah knows the hierarchy of fallback positions:

• "Start here, but we can go to X if pushed"
• "This is our final position, don't negotiate beyond it without approval"
• "This looks important but we actually don't care about it"
• "This seems minor but we lost $200K because of it once"

Without Sarah, junior attorneys either hold firm on everything (losing deals) or give away things they shouldn't (creating risk).

The Relationship Context

Sarah knows that the CFO cares deeply about CAM caps but is flexible on TI timing. She knows that the head of leasing wants fast turnarounds and will accept more risk for speed. She knows which property managers need extra hand-holding on lease administration.

Without Sarah, the new attorney starts from zero on every internal relationship.

The Immediate Scramble

"Did Sarah leave any notes?"

She left a folder. It has 200 files with names like "Retail_notes_2019" and "Call with John re assignment." It would take weeks to make sense of them. There's no time.

The Conservative Overcorrection

Without knowing which positions are truly important, the replacement attorney treats everything as important. Deals slow down. Tenants get frustrated. The leasing team complains.

The Gradual Drift

Six months later, the replacement is comfortable. They've developed their own style. Their own preferences. The templates have subtly shifted. Some changes are improvements. Some are not. Nobody knows which.

The Invisible Gaps

Two years later, a dispute arises. The clause that would have protected the company? It was in Sarah's template. The current version doesn't have it. Nobody remembers removing it. Nobody remembers why it was there.

Ask yourself:

• If your most senior leasing attorney left tomorrow, how long until someone could fully replace them?
• How much of your lease drafting process exists only in people's heads?
• Could a new hire understand why your templates are structured the way they are?
• Do you have documented fallback positions, or just institutional memory?

If the answers concern you, you have key-person risk.

The alternative to key-person risk is externalized knowledge, encoding what your best people know into a system that persists:

Structured Templates

Not just documents, but documents with embedded logic and context:

• Why each clause exists
• When to use each variation
• What the fallback positions are
• What history led to current language

Documented Decision Trees

When the system presents clause variations, your organization's guidance is encoded alongside them:

• "Standard clause appropriate for most tenants"
• "Enhanced protection, use when credit is below X"
• "Added after [specific situation], do not remove without GC approval"

Institutional Memory in the Platform

The knowledge isn't in Sarah's head. It's encoded in the system your team built. When Sarah leaves:

• Your templates remain intact and explained
• Your fallback positions are documented
• Your history is preserved
• The replacement can be productive in weeks, not years

Key-person risk isn't about Sarah. It's about any organization where critical knowledge exists only in individual heads. The solution isn't to prevent people from leaving. It's to ensure that when they do, the knowledge stays.