Why Occupier Account Records Break Down Before the Deal Does
Most commercial real estate teams lose deals not in negotiation but in the months before a proposal lands. The account record — the CRM entry that holds everything known about an occupier — is either a living file that supports origination and site selection, or a graveyard of stale contact names and a lease expiration date nobody has verified since the assignment closed. The difference between those two states is almost always structural: the fields exist, or they do not, and the right people update them, or they do not.
A well-designed occupier account record functions as the single source of truth for a tenant-rep or corporate real estate team. It answers the questions a senior adviser asks before picking up the phone: who is the real decision-maker this cycle, what space does the company occupy, when does the lease roll, and what changed since the last conversation? When those answers require three systems and two conversations to reconstruct, the team is already behind the landlord who has been tracking the same lease on a critical-date calendar for two years.
This article identifies the 8 fields every occupier account record should include, explains what each field enables, and shows how to make them actionable rather than archival. The list applies to tenant-rep brokerage teams, in-house corporate real estate functions, and occupier-side portfolio teams managing multi-market footprints. Every field described here corresponds to a real workflow decision, not a data hygiene preference.
Field 1 — Lease Expiration Date and Critical Milestones
The lease expiration date is the most obvious field and, paradoxically, the most often wrong. Teams pull the executed lease summary once, enter the date, and stop there. What they miss are the fields that make the expiration date meaningful: the notice-to-renew deadline, the date by which the tenant must exercise a renewal option to preserve its rights, and any contraction or termination option windows that open before the nominal expiry.
A lease expiration that is twenty-four months out is not a lead. A renewal-option exercise deadline that is nine months out is a conversation that needs to happen this week. The field should therefore capture at minimum the final expiration date, the first day of the notice period for renewal, and any early termination or contraction option trigger dates. Each date should carry a named owner — the person inside or outside the occupier organization responsible for the decision — so the record connects the timeline to the relationship.
Critical-date fields also discipline the team around what it does not yet know. If the renewal notice deadline is blank, that is not a data gap to paper over — it is a reason to re-read the executed lease or call the tenant's facilities contact. A blank field that surfaces a missing action is more useful than an estimated date that creates false confidence and causes a team to miss the window entirely.
Field 2 — Real Decision-Maker Contact, Not the Facilities Manager
Every occupier account has a primary contact and a decision-maker, and they are frequently different people. The facilities manager or office manager is often listed in the CRM because they are the person who picks up the phone. The CFO, COO, or Head of Real Estate who ultimately approves the transaction is listed nowhere, or appears as a stale LinkedIn import that has never been called.
The decision-maker field should capture the person who controls the real estate budget and signs the lease, their direct contact information, their reporting line, and the last date a substantive conversation occurred. Substantive means a conversation that produced information — a preference, a constraint, a timeline change — not a check-in that produced nothing. A commercial real estate CRM that distinguishes between logged activities by type makes this distinction possible.
The field should also capture who influences the decision-maker: the general counsel who reviews lease language, the CFO who approves net present value comparisons, and the operational lead who defines the space program. These are not separate account records but linked contacts within the same occupier account. When a transaction moves quickly and the team has no established relationship above the facilities level, the gap shows immediately.
Field 3 — Space Program and Headcount Assumptions
Space program data is where account records most frequently fail occupier teams and their advisers. The existing footprint is entered — say, 22,000 square feet on two floors in a Class A building — but the record carries no information about how that space is configured, how many people it currently houses, or what the company's headcount trajectory looks like over the likely lease term.
A space program field should include the current occupied square footage, the current headcount, the density assumption the company uses (whether by seat, by desk, by workpoint, or by some hybrid of assigned and unassigned), and the projected headcount range over a three-to-five year horizon. Those projections are not the adviser's guesses — they come from the occupier's own planning assumptions, which means the field doubles as a record of what the client told you and when they told you it.
Headcount assumptions also drive the financial analysis that defines a requirement. A company planning to grow from 180 to 260 people over a five-year lease term needs a different space program than one planning to hold flat while implementing activity-based working that reduces its density. The space program field is the input from which site selection criteria, target building sizes, and lease flexibility provisions all flow. Without it, the requirement is a square-footage range with no analytical foundation.
Field 4 — Budget and Effective Rent Tolerance
Occupier accounts that carry no financial field are relationship records, not transaction files. A budget field is uncomfortable to maintain because occupiers often resist disclosing budget parameters early, and internal teams sometimes view budget data as proprietary. Both of those facts are real, and neither changes the reality that an adviser who does not know the occupier's budget cannot run a meaningful market survey or protect the client from a proposal that looks attractive on headline rent but collapses under total occupancy cost.
The budget field should capture the occupier's all-in occupancy cost tolerance — rent, operating expenses, parking, and any capital contribution the occupier expects to make — expressed as a per-square-foot figure and as a total annual number. Where the occupier's planning uses a cost-per-head metric rather than a cost-per-square-foot metric, that should be recorded as well, because it reflects how the real estate decision will be evaluated internally.
Effective rent tolerance is the underlying calculation: the rent net of landlord incentives — free rent, tenant improvement allowance, and any rent abatement — expressed as an annualized figure over the lease term. A company that says its budget is $45 per square foot gross may be operating at a $38 per square foot effective rent once a significant TI package is applied. Lease analysis software that models effective rent against total occupancy cost makes this comparison explicit, but the starting point is a field in the account record that captures what the occupier actually said about its constraints.
Field 5 — Geographic Preference and Sub-Market Constraints
A geographic preference field sounds simple and becomes complicated immediately when a real requirement is examined. The occupier says downtown, but three of its key hires live in the suburbs and the leadership team wants access to transit. The stated preference and the functional constraint are often different, and the account record should hold both.
The geographic preference field should capture the occupier's stated preference by market and sub-market, any hard constraints that eliminate specific areas (a competitor's office in the same building, a proximity requirement to a client, a commute-time threshold for a defined employee population), and the reason for those constraints. Reasons matter because they are negotiable in ways that constraints stated without reasons are not. An occupier who says they will not go north of a particular corridor because of executive commute time has a constraint that might be answered by a transit analysis; one who says they will not go north because their largest client is south has a constraint that is not negotiable.
Site selection for multi-market occupiers adds another layer. A company making a portfolio decision across five markets has different geographic preference inputs for each market, and the account record should reflect that the Chicago requirement and the Dallas requirement have different commute patterns, different transit access priorities, and different sub-market cost structures. Site selection software that allows teams to define the brief and score property options against weighted criteria handles this at the property level — but the scoring criteria come from the geographic preference field in the account record.
Field 6 — Lease Structure Preference and Flexibility Requirements
An occupier who has lived through a pandemic-era contraction and carries the institutional memory of subleasing 40% of its space at a loss thinks about lease structure differently from a growth-stage company that has never signed a lease longer than three years. Lease structure preference is a substantive field that reflects the occupier's risk posture, not just its real estate preference.
The lease structure field should capture the preferred lease term, whether the occupier requires contraction or expansion options and at what points in the lease those options need to activate, whether the occupier is evaluating ownership (purchase or sale-leaseback) alongside leasing, and any covenanting constraints that affect the term a landlord will offer. A company with thin credit or an early-stage balance sheet may need a shorter term or a stronger TI package to compensate for the concession on term a landlord makes.
Flexibility fields are increasingly important for occupier accounts in markets where hybrid work schedules produce real uncertainty about long-term footprint. The account record should note whether the occupier is explicitly modeling a scenario in which it takes less space at renewal than it currently occupies, and whether contraction options in the new lease are a requirement or a preference. That distinction changes the market survey: some landlords will not grant meaningful contraction rights in a tight market, and knowing that a specific occupier requires them narrows the building universe before the first site tour.
Field 7 — Current Incumbent and Prior Transaction History
The 8 fields every occupier account record should include must contain a field tracking who represented the occupier last time and what the outcome of that transaction was. This is the field most likely to be omitted because it requires the team to record information that may reflect a prior relationship that was not retained. The absence of that history is more damaging than its presence.
Knowing that a competitor represented the occupier in its last lease renewal, and knowing the term, approximate size, and timing of that transaction, allows the current team to calibrate its approach. If the prior transaction closed eighteen months ago and was a five-year renewal, the space program question is already partially answered and the lease expiration date is calculable from the prior event. If the prior transaction involved a dispute over TI delivery that the occupier mentions in passing, that background shapes how the current team positions its project management capability.
Prior transaction history should also include any prior interactions this brokerage team has had with the account: meetings, proposals, requests for qualifications, and any prior engagements that did not result in a transaction. A team that presented credentials two years ago and lost to a competitor knows something about the occupier's selection criteria. A team that has never had a meeting knows it is starting from cold. The distinction drives different relationship strategies, and the account record is where that history lives.
Field 8 — Current Building and Landlord Intelligence
The final core field is the occupier's current building profile — the building address, the landlord or ownership entity, the building class and relevant physical specifications, and any known relationship dynamics between the occupier and its current landlord. This field connects the relationship record to the property record and enables the commercial real estate intelligence platform to support the next step: identifying comparable buildings, assessing whether the current landlord is likely to compete aggressively for a renewal, and building a market survey that starts from a real baseline.
Building intelligence includes the current lease's known terms to the extent the team has documented them: base rent, gross-up methodology, operating expense base year or stop, parking ratio, and any outstanding landlord obligations that remain unfulfilled. An occupier who has an open TI credit from the prior landlord or a pending repair obligation that was promised and not delivered brings that history into the renewal negotiation, and a well-maintained account record surfaces it before the conversation begins.
The landlord relationship field is the softer part of this data and is often the most strategically important. An occupier that has a poor relationship with its landlord because of a service dispute is more likely to relocate than one that values the relationship. An occupier whose landlord recently sold the building to a new owner may face an entirely different renewal dynamic than the one they anticipated. Those dynamics are not captured in the lease document — they live in the account record as relationship notes, and they inform every strategy conversation.
Connecting the Eight Fields Into a Working Account Record
Eight fields produce a working account record when they are connected, not when they are filled in isolation. The lease expiration date connects to the decision-maker contact because the notice deadline creates the reason to call. The space program connects to the budget because headcount growth changes the all-in cost calculation. The geographic preference connects to the current building because the incumbent location is the baseline from which all alternative scenarios are measured.
In practice, many commercial real estate CRM systems allow teams to define custom fields at the account level, but the fields mean nothing if the team does not have a shared discipline for maintaining them. Account records degrade when the person who gathered the information is also the only person who updates it. A well-designed account record has defined ownership for each field: the relationship manager owns the decision-maker contact and the last-conversation date; the transaction manager owns the space program and lease structure preference; the financial analyst owns the budget and effective rent tolerance.
Making the Fields Drive Origination, Not Just Administration
A CRM populated with eight fields for every occupier account does not automatically produce origination activity. The fields drive origination when the team uses them to identify which accounts have approaching critical dates, which accounts have space programs that suggest a requirement is forming, and which accounts have geographic preferences that match a specific building opportunity the team has identified.
An account with a decision-maker field that was last updated fourteen months ago, a lease expiration that is now eighteen months out, and a space program that shows the occupier has grown its headcount by 30% since the last conversation is not an archival record — it is a lead that has not yet been worked.
Common Reasons These Fields Go Unmaintained
The practical obstacle to maintaining eight substantive fields per account is time, and the practical solution is process discipline rather than a technology fix. Teams that import contacts from LinkedIn and call them accounts have thousands of records with one field populated. Teams that restrict account creation to relationships where at least four of the eight fields can be populated on creation have fewer records and more useful ones.
A second obstacle is team structure. Tenant-rep shops where each broker maintains their own contacts in a personal spreadsheet or email thread have no shared account record at all, and therefore no institutional knowledge that survives the departure of the broker who held the relationship. The account record is the mechanism by which relationship knowledge becomes organizational knowledge. That transition requires policy — what gets entered, by whom, within what timeframe after a conversation — not just a CRM license.
A third obstacle is the belief that incomplete records are worse than no records. In fact, a record with five of eight fields completed is useful because it shows the team exactly what it does not know and creates the agenda for the next conversation. The gap in the record is not a failure — it is a question that the next client interaction should answer, and the account record is where the answer gets stored.
How the Eight Fields Support Portfolio-Level Decisions
For in-house corporate real estate teams managing multi-market occupier portfolios, the eight fields function at both the individual asset level and the portfolio level. That query is not possible when the data lives in inconsistent formats across disconnected systems.
Portfolio-level decisions — whether to consolidate markets, which leases to renew versus relocate, where to run formal RFP processes versus direct negotiation with incumbents — require the kind of structured account-level data that the eight fields provide. A lease administration system can generate a critical-date report. An occupier account record that includes decision-maker contacts, space program assumptions, and lease structure preferences provides the strategic context the critical-date report cannot.
When the underlying account records are structured with the eight fields, the portfolio view reflects real organizational knowledge rather than a date pull from an abstracted lease database.
Applying the Eight Fields in Tenant-Rep Origination
Tenant-rep brokerage teams use the eight fields differently from in-house portfolio teams, but the structural logic is the same.
The eight fields create a structured agenda for each client interaction.
Effective origination in commercial real estate is relationship-driven but data-disciplined. The eight fields are the mechanism that makes that precision possible, and the account record is where that precision lives or dies.
About Advantai
Advantai is a commercial real estate intelligence and operations platform operated by ADVANTAGE AI LLC, a Delaware limited liability company. It connects client relationships, property research, documents and financial decisions in one workspace for commercial real estate teams — advisers and brokerage teams, occupier and facility teams, and portfolio teams. The platform covers CRM and origination, requirements and site selection, Property X-Ray (an interactive 3D building workspace), financial modeling and comparison, document intelligence, transactions and diligence, client collaboration, and portfolio strategy with critical dates. The optional Super Agent upgrade adds specialist, source-backed research and automated scenario analysis.
Get Started with Advantai
Ready to see your next move clearly? Go to advantaico.com, click Request a demo and tell us about your next project. Prefer to start with a single project? Visit advantaico.com/getting-started to plan your first one.