The property record is the operational center of any commercial real estate transaction, yet most teams build it to serve only one side of the market. A record designed exclusively for landlord representation misses the comparative lease economics a tenant adviser needs. One built purely for occupier work lacks the leasing velocity and rollover data a landlord team depends on. Learning how to structure a property record that serves both landlord and tenant rep work means understanding the distinct questions each side asks — then designing a single data architecture that answers both without forcing either team to re-enter information or maintain shadow files.
Why a Single Property Record Fails Most Teams
The common failure mode is building the property record around a transaction type rather than around the asset itself. When an adviser inherits a record from a predecessor or a different practice group, they typically find fields that are either over-specified for one workflow or empty because the original author never anticipated a different use. The result is a record that is authoritative about one dimension of the asset and silent about everything else.
Landlord teams tend to populate floor-by-floor availability, asking rent by suite, escalation schedules, and parking ratios. Tenant teams tend to populate market comparables, effective rent calculations, and submarket vacancy trends. Neither set of fields is wrong. The problem is that they are rarely held in the same record, which forces every new engagement to begin with a data-gathering exercise that duplicates work already done elsewhere in the firm.
The fix is not to merge every possible field into one enormous form. Overly complex records slow down adoption and produce inconsistent data. The fix is to identify the shared core — the fields that every transaction type relies on — and then build lightweight, role-specific extensions on top of that core. A landlord adviser and a tenant adviser should be able to open the same record, navigate to their relevant layer, and find the information they need without wading through fields that don't apply to their current engagement.
The Landlord-Side Extension Layer
Once the core is solid, the landlord extension layer captures everything needed to manage and market the asset as an owner or owner's representative. The primary fields here are available suites with square footage, contiguous availability, and the date each suite became or will become available. Accuracy on suite-level availability prevents the worst kind of landlord embarrassment: showing a prospect a space that has already been leased.
Asking rent belongs in the extension layer with a distinction between gross asking rent and net asking rent, because quoting the wrong basis to a tenant's adviser wastes everyone's time and signals poor record hygiene. Tie the asking rent to the effective date of the quote, because rent levels in a leasing campaign move with market conditions and with the landlord's lease-up progress. A dated rent field is a defensible record; an undated one is a liability.
Tenant mix data — existing tenant names, suite numbers, lease expiration dates, and any rights to renew or expand — belongs in the landlord layer. This data drives rollover analysis, which tells a landlord team where their exposure concentrates and where their pipeline opportunity lies. A floor plate with four leases expiring in the same quarter requires a very different marketing posture than one with staggered expirations spread over three years.
Capital expenditure history is another landlord-side field that is frequently absent from property records until a due diligence request forces someone to reconstruct it. Tracking roof replacements, HVAC upgrades, elevator modernizations, and their associated costs within the property record means the landlord team has an asset narrative ready for investor presentations and can respond to tenant questions about building quality without searching through project management files.
Leasing commissions paid, expressed as a dollar amount or as a percentage of aggregate rent, complete the landlord layer. Some teams resist recording commission data in the property record because it feels like deal economics rather than property data. It is, in fact, both: commission rates signal competitive leasing market conditions, and tracking them by suite and by lease term lets a brokerage team benchmark its deal economics against historical norms within the same building.
The Tenant-Rep Extension Layer
The tenant-rep extension layer answers a fundamentally different set of questions: does this building meet our client's requirements, and on what terms can we negotiate occupancy? The first field group here is the requirement alignment score — a structured comparison of the tenant's stated criteria against the building's verified attributes. If a client needs 24-hour HVAC at no surcharge and the building charges for after-hours air, that is a scored misalignment that should be recorded before the building advances on a shortlist.
Comparable lease data belongs in the tenant-rep layer, referenced at the submarket level. This means capturing recent transactions in the same submarket — their size, lease term, net effective rent, and tenant improvement allowance — so the adviser can benchmark any landlord proposal against market reality. These comparables are sourced from subscription data services or confirmed with counterpart brokers; they should be cited in the record with their source, not entered as unattributed figures.
Effective rent calculation is the central financial field in the tenant-rep layer. Effective rent converts a lease proposal — asking rent, free rent months, tenant improvement allowance, and escalation schedule — into a single annualized number that allows apples-to-apples comparison across buildings with different economic structures. A hypothetical example: a ten-year lease at a hypothetical $45 per square foot asking rent with twelve months of free rent and a hypothetical $80 per square foot tenant improvement allowance produces a materially different effective rent than a ten-year lease at a hypothetical $42 per square foot with no free rent and a hypothetical $40 per square foot allowance, even though the second option has the lower asking rate. Recording the full effective rent calculation in the property record, with all assumptions labeled as hypothetical where they are not yet confirmed, keeps the tenant team and the client on the same analytical footing.
Lease net present value analysis extends effective rent into time value of money terms. A tenant choosing between two buildings with similar effective rents may find that one option produces a meaningfully lower NPV when escalation rates, occupancy cost savings, and move-related capital expenditures are present-valued at the client's discount rate. Capturing the NPV model in the property record — with the discount rate, escalation assumptions, and term clearly disclosed — creates a defensible audit trail for the recommendation.
Connecting Lease Economics to the Property Record
Lease economics fields should live inside the property record rather than in standalone spreadsheets that become disconnected from the underlying property data. The practical reason is traceability: when a client asks why a building was recommended or rejected, the adviser needs to show not just the conclusion but the inputs that produced it. If the financial model lives in a separate file, the connection between the property's physical attributes and the economic analysis is implicit rather than explicit, which makes the recommendation harder to explain and impossible to audit.
Linking the economic model to the core record also disciplines the data entry process. If a tenant adviser enters an asking rent from a landlord proposal directly into the property record's tenant-rep layer, that figure is tied to a specific building, a specific floor, and a specific date. If the same figure lives only in a spreadsheet, it has no provenance — the next person who opens the file cannot tell whether it was an asking rent, an effective rent, a net rent, or a gross rent, or when it was confirmed.
Structuring Availability and Timing Fields
Timing fields are among the most mistreated elements of a property record. For landlord work, the critical timing fields are lease expiration date, notice period for renewal or termination, and any rights that allow a tenant to expand into adjacent space. These fields determine when the landlord team has a marketable opportunity and how much lead time they have to fill it.
For tenant-rep work, the client's critical date is typically the lease expiration date in their existing space, backed out by the minimum time required to execute a relocation. If a tenant's lease expires in eighteen months and market conditions require twelve months to identify, negotiate, and complete a build-out, the adviser's search window is already narrow. Recording the client's constraint in the property record — specifically, in the requirement linked to the building being evaluated — creates an explicit time-budget field that keeps every stakeholder aware of the timeline.
Holdover risk is a timing field that belongs in both layers. For the landlord, a tenant in holdover is occupying space that cannot be marketed with certainty. For the tenant's adviser, a client in holdover is typically paying a punitive holdover rate — often one hundred fifty percent of base rent or higher, though the exact multiple varies by lease and jurisdiction — while the new space is being completed. Embedding a holdover flag in the property record, with the holdover rent multiple confirmed from the existing lease, turns an abstract risk into a priced obligation that can be factored into the economic case for moving quickly.
Sourcing and Citation Standards for Property Records
A property record is only as reliable as its sources, and unreliable property records produce bad deals. Every factual field in a property record should carry a source reference: the name and date of the document, the page or section where the fact appears, and whether the fact was verified by direct inspection or accepted from a third-party representation. This is not bureaucratic overhead; it is the minimum standard for a professional advisory practice.
For core fields like rentable square footage, the source should be either a measured survey report with a date and surveyor's name or the building's BOMA certification documentation. Using marketing materials as the sole source for square footage is a known risk; landlord marketing brochures frequently cite approximate figures, and measurement basis discrepancies between BOMA 2017 and earlier standards can produce material differences in usable area for a tenant.
Zoning data should reference the applicable municipal zoning ordinance or the jurisdiction's official zoning map, with the access date recorded because zoning classifications can be amended. For tenant-rep work, noting the difference between current zoning and any pending rezoning applications is especially important when a client's intended use is at the edge of what the current classification permits.
Comparable lease data for the tenant-rep layer must carry source citations from whatever data service or broker confirmation produced them. Citing "market knowledge" as a source is insufficient for a client-facing analysis. If a comparable came from a subscription data platform, record the platform name and the date it was pulled. If it was confirmed by a counterpart broker, record the broker's name and the date of the conversation.
Workflow Routing: Who Owns Which Fields
Field ownership is a governance question that most firms avoid until a record becomes corrupted by conflicting entries. The practical answer is to assign field ownership by role rather than by individual, because personnel turnover is constant in brokerage. The core fields are owned by whoever has primary responsibility for the property record — typically the lead adviser on the most recent or most active engagement. The landlord-layer fields are owned by the leasing team assigned to that property. The tenant-rep layer fields are owned by the requirements team assigned to the client searching in that submarket.
When the same adviser operates in both landlord and tenant-rep capacities — which is common in smaller markets — the same person owns all layers, but the distinction between layers still matters because it structures the adviser's thinking. A landlord-hat observation and a tenant-hat observation about the same building are different analytical acts, and recording them in separate layers prevents them from contaminating each other.
This matters for a commercial real estate CRM discipline because relationship records and property records are rarely independent: the same contact may be a landlord on one record and a prospect on another.
Review cadences should be defined in the workflow governance, not left to individual discretion. A property record for an active landlord listing should be reviewed at minimum monthly against market conditions. A property record for a building under active tenant evaluation should be reviewed at every significant milestone in the requirement process — after the first tour, after the initial proposal, and after each negotiating exchange — because each of those events can change a field value that is relevant to the client's decision.
Scoring and Shortlisting Inside the Record
A scoring framework embedded in the property record converts subjective impressions into documented decisions. For tenant-rep work, the scoring matrix compares each building against the client's stated requirement criteria, weighted by the client's own priorities. If a client weights proximity to rail transit at forty percent of the location score, that weight should be recorded in the requirement, not held in an adviser's memory.
The score itself is less important than the narrative that accompanies it. A building that scores seventy-two out of one hundred on a hypothetical scoring matrix means nothing without the explanation of which criteria it met, which it failed, and why it was kept on the shortlist despite failing them. Recording that explanation in the property record creates the advisory narrative that clients need to make confident decisions.
For landlord work, scoring logic runs in reverse: the landlord team scores prospective tenants against the asset's requirements. Credit quality, use compatibility, and lease term requirements can all be systematized into a tenant screening framework that is applied consistently across prospects. Embedding this framework in the property record means every member of the leasing team applies the same criteria, reducing the risk that a marginal tenant is accepted because the person handling the inquiry applied a different standard than the team lead would have.
Maintaining the Record Through the Transaction Lifecycle
A property record is not a one-time data entry exercise. It is a living document that evolves from initial research through lease execution and into portfolio management. The fields that matter most change at each stage, which is why record structure needs to accommodate lifecycle tagging: a field can be marked active, superseded, or pending confirmation as the transaction progresses.
During the proposal stage, the asking rent in the landlord layer and the effective rent calculation in the tenant-rep layer are both provisional figures subject to negotiation. Marking them as provisional rather than confirmed prevents a future team member from treating a quoted figure as an agreed term. When the letter of intent is executed, the agreed economic terms should be entered with a confirmed tag and a date, replacing or supplementing the provisional figures.
During the lease execution stage, the record should capture the final lease economic terms — base rent, escalation schedule, free rent period, tenant improvement allowance, and commencement date — against their sources in the executed document. For tenant-rep work, capturing the final economics alongside the initial proposal allows the adviser to demonstrate the value of the negotiation by showing the movement from initial ask to final agreement.
After execution, the property record transitions from a transaction tool to a portfolio monitoring tool. Critical dates — lease commencement, rent commencement, renewal notice deadlines, expansion option deadlines, and lease expiration — become the primary fields of interest. Tracking these dates with named owners and assigned priorities ensures that an option deadline is never missed because the responsible adviser was on vacation or had left the firm.
The Connection Between Property Records and CRM Origination
Property records and relationship records should not be managed as separate databases. The same contact who provides a comparable lease figure for a tenant-rep engagement may be the leasing contact for a building on the landlord side. If the property record and the contact record live in different systems, the connection between them is maintained only in someone's memory, which is an unreliable architecture.
When a new requirement comes in from an existing client, the adviser should be able to navigate from the client contact record to the properties that have been evaluated for that client and from each property record to the contacts associated with the building — the leasing agent, the ownership contact, and the previous transaction history.
Ensuring Record Portability Across Practice Groups
One final design principle deserves attention: the property record must be portable across practice groups without losing its integrity. When a landlord representation engagement concludes and the asset is sold, the new owner may come to a different practice group within the same firm for asset management or investment sales advice. If the property record from the leasing engagement is locked inside the leasing team's system, the investment sales team starts from zero. That is a failure of information architecture that costs firms real money in duplicate research and missed context.
Portability does not mean that every field is visible to every user. Access levels should match the sensitivity of the data: commission economics visible to senior advisers and practice leaders; client-specific requirement scores visible to the assigned team and their management; general property core fields visible to anyone in the firm who might advise on the asset. Structuring access by role and by field sensitivity allows the record to be broadly useful without exposing confidential deal economics or client information inappropriately.
The goal of a well-structured property record is to make the next engagement smarter than the current one. That is the standard against which every property record design decision should be measured.
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.