The PAM-PM data handoff: why it breaks down and what to do about it

At the centre of Swiss institutional real estate sits a relationship that is simultaneously the most information-intensive and the most operationally fragmented: the interface between the property asset manager (PAM) and the property manager — the régie or Verwaltung — who operates the buildings.

The PAM sets strategy, manages investor relationships and produces regulatory reporting. The PM executes operations: leasing, maintenance, tenant management, service charges. Between them flows an enormous amount of data — rent rolls, vacancy reports, income statements, capex actuals, lease data — that the PAM needs to do its job and that the PM generates as a byproduct of doing theirs.

This handoff is where institutional real estate data governance most frequently breaks down. Understanding why it breaks down is the first step toward fixing it.

The format problem

The most common explanation for PAM-PM data problems is "the régie doesn't send data in the right format." This is usually accurate but incomplete. The more precise statement is that the régie sends data in the format that their system produces, which is not the format the PAM's model requires, because nobody established a common specification for what "the right format" means.

A mid-sized Swiss real estate fund with six régie partners may be receiving rental income data in six different structures: different account codes, different treatment of VAT, different conventions for vacant units, different definitions of the reporting period. Each quarter, someone on the PAM team converts these six formats into one model. The conversion logic is not documented. It lives in an analyst's head or in a comment cell in a spreadsheet. It changes without notice when the régie changes their reporting convention — or when the analyst leaves.

The timing problem

Quarterly batch delivery is the norm. Property managers close their accounts, run their reports and deliver data to the fund manager on a schedule that ranges from two to six weeks after quarter-end. For a fund with multiple régie partners and staggered delivery schedules, the data consolidation exercise stretches further into the quarter — meaning that by the time the fund manager has a complete, validated picture of Q1, Q2 has already started.

This timing gap has practical consequences for investment decisions. Asset-level vacancy trends, capex overruns, and lease events are visible to the régie in real time but reach the fund manager weeks later — filtered through a quarterly batch process. A lease that expires at quarter-end may not appear in the fund manager's consolidated view until six weeks later.

The Remit PAM/PM Forum in January 2026 identified this timing gap as one of the primary frustrations expressed by both sides of the relationship. PAMs want earlier visibility; PMs argue they need the time to close accounts accurately. Both perspectives are legitimate. The solution requires infrastructure that allows for earlier delivery of preliminary data without compromising the accuracy of final figures.

The accountability problem

When a number in a report doesn't match expectations, the correction cycle begins. Who owns the error? The régie that delivered it, the analyst who loaded it, or the model that processed it? In the absence of a documented data trail, this question is often impossible to answer definitively — which means it tends to be answered by organisational dynamics rather than evidence.

This accountability gap is not just inefficient — it is a governance risk. For FINMA-regulated fund managers, the ability to trace every number in investor and regulatory reporting back to a documented source is an expectation, not a preference. When the data pipeline is manual, undocumented and split across email attachments and shared drives, that traceability does not exist.

What structural solutions look like

The PAM-PM data relationship cannot be fixed by asking régies to change their systems or by hiring more analysts. It requires infrastructure changes at the PAM level that impose structure on the relationship without requiring operational change from the PM.

The first structural change is a defined data specification: a documented schema that specifies exactly what data the PAM requires from each régie, in what format, on what schedule, with what validation rules. This specification should be agreed with each PM partner at the start of the relationship and reviewed annually. It transforms the data handoff from an informal expectation into a defined service specification.

The second structural change is automated ingestion and validation. When régie data arrives, it should be checked automatically against the defined schema before it enters the PAM's reporting model. Discrepancies are flagged at ingestion — not discovered when reading the report. The audit trail of what was received, when, from whom, and whether it passed validation becomes the documentary record of the data governance process.

The third structural change is a shared view. The most advanced PAM-PM relationships in the Swiss market are moving toward a model where both parties have access to the same data in the same system — allowing régies to see how their data appears in the fund manager's model and flag discrepancies before the PAM's deadline rather than after. This requires the PAM's data platform to offer a structured interface for PM data entry or review, not just a one-way delivery mechanism.

What changes when the infrastructure works

When PAM-PM data infrastructure works as described, several things improve simultaneously. The quarterly consolidation cycle shortens because data arrives in a known format and is validated automatically. The error correction cycle reduces because discrepancies are caught earlier and at source. The audit trail becomes documentary rather than testimonial. And the relationship between PAM and PM improves because misunderstandings about data — which are a significant source of friction in many of these relationships — are resolved by reference to the agreed specification rather than by negotiation.

The Remit Forum articulated this as "earlier visibility of budgets and a shift toward rewarding measurable outcomes rather than inputs." From a data infrastructure perspective, this translates to a model where the PAM and PM share a common operational data layer rather than exchanging quarterly batches across an informal interface.