Estate

Prova organises your estate as a tree. Buildings sit under portfolios you group by owner, fund or region, and each building holds its own units: floors, suites and rooms. Segments group buildings by rule rather than by hand, so you define the rule once, such as all offices above 5,000 square metres in Denmark, and membership keeps itself current as the estate changes. Every address carries its jurisdiction, its timezone and its coordinates, so a site in another country calculates its own dates correctly.

Most facility teams keep the estate in a spreadsheet that describes the buildings but connects to nothing else. In Prova the building is the centre of gravity: its equipment, its jobs, its certificates, its contractors and its costs all hang off the same record. That is what makes a portfolio-level question answerable in seconds instead of by emailing five site managers and waiting.

In practice

A new depot opens at Antwerp Dock 4, and one person creates it.

  1. The building is created with its address: Belgium, timezone Europe/Brussels, coordinates on the map.
  2. It is added by hand to the Benelux portfolio, because that is an ownership grouping somebody decides.
  3. The segment sites over 5,000 square metres picks it up on its own, because the rule matched. Nobody added it.
  4. The scope tree gains a building leaf under the Belgium node, so the Benelux manager can see it immediately. No grant was issued.
  5. The compliance matrix gains a row. Every Belgian obligation reads nothing on file until certificates are filed against it.
  6. The Belgian business calendar applies, so Belgian public holidays stop machine-hours accruing on the equipment inside it.

One person created one record. Five other parts of the system are now correct without anybody maintaining them. That is the argument for the building being the centre of gravity rather than a row in a list.

Illustrative walkthrough. Not a customer record.

Other Features

Permissions

Roles grant permissions resource by resource and action by action, denied by default, with six starter roles for facility management running from local manager to compliance officer. Scopes then decide…
Read more

Reliability

When a job closes on a breakdown, Prova captures the closure in a standard shape: problem, cause, remedy, severity and downtime. The vocabulary comes from a failure code catalogue your…
Read more

Contractors

Contractors and suppliers sit in one central register with their service agreements, their insurance policies and the expiry dates attached to both. When a contractor’s insurance policy expires, Prova stops…
Read more

Cost Management

Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building and by trade. Labour is valued at the rate in force…
Read more

Evidence

Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned, tagged, and stripped of EXIF metadata on upload. Documents are typed and anchored…
Read more

Assets

Every piece of critical equipment gets a record: chillers, lifts, alarms, pumps. Each asset carries its category, its warranty, its runtime meter and its complete service history. The asset sits…
Read more

Work Orders

The work order is the unit of work in Prova. A request becomes a job, the job is assigned to a person or a contractor, it is approved, and it…
Read more

Maintenance

A maintenance plan defines a cadence, such as quarterly or the first Monday of the month, and Prova materialises it into dated occurrences across a rolling eighteen-month horizon. When an…
Read more

Next step

See how to optimise your workflow and save money.

Thirty minutes on your own estate: your buildings, your obligations and your numbers. We will show you where the time and the money are going.

Book a demo