A portfolio has two audiences that a single-site estate does not: the buyer doing due diligence, and the tenant being charged. Both of them ask questions at the level of one building, which is usually the level the records were never kept at.
Due diligence turns into a fire drill
A building goes to market and somebody has to reconstruct its compliance position and maintenance history from three systems and a filing cabinet, under a deadline set by somebody else.
In Prova
The compliance position of any building is a screen rather than a project. Each cell carries the certificate pinned to it, and each certificate carries the job and the photographs that produced it. The pack is assembled by reading, not by rebuilding.
Costs will not split the way the service charge needs
Spend arrives as contractor invoices covering several buildings. Splitting it per building, and per trade, to work out what is recoverable is a manual exercise repeated every quarter.
In Prova
Costs attach to the work order as lines and roll up by building and by trade, with the invoice attached to the line. Consolidated expenditure for a set of buildings is a query rather than a reconciliation, and finance can trace every figure back to a job.
A quote becomes an invoice at a different number
Work quoted at 2,400 euro invoices at 3,150. Six months later nobody can say who agreed the difference, or whether anybody did.
In Prova
Updating a recorded cost writes an official correction rather than overwriting. The original figure stays visible alongside the new one, with who changed it and when, so every variance has an author and a date.
Approvals stall when somebody is on leave
An overspend needs sign-off from a country manager who is away for a fortnight. The work waits, or somebody approves it informally and the audit trail is broken.
In Prova
Spending limits escalate up the reporting line automatically. When the next approver is unavailable it falls back to the designated approver above the building rather than stopping, and the route it took is recorded.
A building belongs to more than one grouping
The same asset sits in a fund, a region, a size band and a use class. A folder hierarchy forces you to pick one, so the other views get maintained by hand in a spreadsheet.
In Prova
Portfolios are ownership groupings somebody decides; segments are rule-based and pick buildings up on their own. A building sits in both at once, and an acquisition joins its segments the moment it matches the rule, with nobody maintaining a list.
A cross-border portfolio behaves as if it were in one country
Scheduled work lands on local public holidays, equipment accrues running hours on days the site was shut, and reporting periods do not line up with local practice.
In Prova
Each building carries its country, its timezone and its business calendar. Local public holidays stop machine hours accruing on the equipment inside it, and scheduled work respects local working days without anybody configuring it per site.