Carry the acquisition assumptions into the first operating review

Keep the acquisition model beside the first operating report. I want to know which assumptions survived contact with the property, which changed, and who owns the next check.

- Sasha Deneux

The Take: The first operating review belongs in the acquisition workflow

JLL's September 24 guide to real estate AI asks when a firm should buy software, extend what it has or build its own. My test for any of those options would include a handoff that gets less attention than the first demonstration: the transition from acquisition assumptions to operating results.

An acquisition model has a reason for each important input. An asset-management report has a result for a particular period. Put those documents in separate systems and the team can spend the next meeting reconstructing what it originally expected.

I would make that reconstruction part of the workflow before calling it complete. Preserve the approved model version, map its categories to the operating report, and show where the definitions differ. A revised budget should be available beside the original case, with its own date and explanation.

Consider an insurance assumption accepted before closing. The first invoice may cover a different period or include charges the model placed elsewhere. A larger number is a reason to investigate. It does not, by itself, explain the variance.

This is where I want an assistant to be precise. Which document supplies the actual? Which assumption supplies the comparison? What remains unresolved? The person reviewing the property should be able to disagree with the explanation without having to rebuild the evidence behind it.

The buying decision should include that revision exercise. A convincing first draft tells you less about the operating handoff than a changed input that the system carries through correctly.

The Teardown: Carry one approved assumption into the first review

Start with a practice property, an approved acquisition model and one operating period. Use documents your team is permitted to process. Keep the original files and the accepted interpretation together.

Freeze the comparison. Name the acquisition-model version and the dates covered by the operating report. If the team has also approved a revised budget, give it a separate column. That keeps a new forecast from silently replacing the expectation you are trying to examine.

Map the categories. Write down how the model's rental income, reimbursements, repairs and other categories correspond to the operating statement. Check cash versus accrual treatment and reporting periods. Mark a missing line as missing until the reviewer resolves it. The rent-roll reconciliation practice guide is a useful starting exercise for checking the income inputs.

Show the variance before explaining it. In a purely fictional monthly example, rent is $2,000 below the comparison case and repairs are $1,000 above it, with every other line unchanged. NOI is therefore $3,000 lower. That arithmetic does not establish why either line changed.

Attach the evidence to the explanation. A delayed receipt, a concession and a vacancy can affect income differently. Ask for the relevant ledger or lease reference. For repairs, inspect the work order and accounting treatment before calling the difference temporary. Keep an unsupported explanation as a question assigned to someone, not a conclusion in the summary.

Follow one correction through. Change an input in the practice report and verify the variance table, narrative and action list together. The new explanation should reference the new evidence. The old assumption should remain available in the history. Check that an unanswered question stays unanswered when the prose is regenerated.

The review output can be short: the accepted comparison, the material differences, the evidence checked and the next action with an owner. Record the corrections required to reach that output. Those corrections tell you where the workflow still needs work before more properties enter it.

Signal

Three September reads to bring into the next workflow review:

• September 24: put the operating responsibility in the technology decision. JLL's build-or-buy guide frames the choice around more than the ease of generating software. My application: ask who maintains the reporting handoff when a source format or model assumption changes.
• September 9: inspect how the data comes together. CBRE's portfolio-savings account describes connecting information from several real estate functions before looking for further actions. This is CBRE's account of its own engagement. For our purposes, the useful pilot question is whether a proposed action can be traced back across the source reports.
• September 9: keep a market thesis separate from a property input. CBRE's office-demand research examines how AI could affect office employment and space demand. Treat that research as context for questions about tenant exposure. It does not establish a rent, renewal or occupancy assumption for the particular building you are reviewing.

From NextAutomation

We build underwriting and reporting workflows around a team's source documents, models and review decisions. Book a conversation and bring a redacted example of a handoff that keeps creating rework. The underwriting model-builder pack gives you a structure for organizing the inputs.

Keep the original assumption available. Give the new evidence somewhere to land.

Next week: cleaning an owner list without merging unrelated owners.

- NextAutomation Team