{"id":68,"date":"2025-10-05T16:25:54","date_gmt":"2025-10-05T16:25:54","guid":{"rendered":"https:\/\/provasoftware.com\/?page_id=68"},"modified":"2026-10-26T08:21:44","modified_gmt":"2026-10-26T08:21:44","slug":"about","status":"publish","type":"page","link":"https:\/\/goprova.com\/nl\/about\/","title":{"rendered":"About"},"content":{"rendered":"

\nAbout Prova\n<\/p>

\nWho you would be buying from\n<\/h1>

\nA straight account of why we built this, what we know about the problem, and what it would actually mean to work with us. Including the parts most suppliers leave off this page.\n<\/p><\/div><\/header>

\nWhy we build this\n<\/h2>

\nMost organisations running buildings already hold all the information. It is just scattered. The asset register is a spreadsheet. The certificates are in a shared drive. The agreement with the contractor is in somebody's inbox. The invoice is in the finance system. Each one is correct on its own, and none of them agree with each other.\n<\/p>

\nThat is survivable right up to the moment somebody asks a question with consequences attached. An insurer asks when the panel was last inspected. A regulator asks who signed off the remedial work. A tenant asks why the same unit has failed three times this year. The information exists. Proving it takes days, and the proof gets assembled by hand, from four places, by whoever remembers where to look.\n<\/p>

\nWe did not think that needed a better spreadsheet. We thought the record of what happened should be a by-product of doing the work, rather than something reconstructed afterwards under pressure.\n<\/p>

\nSo that is what Prova is. The job, the cost and the evidence stay attached to the same record, as the work happens. When the question comes, the answer is already there.\n<\/p><\/div><\/section>

\nWhat we know\n<\/h2>

\nWe laten ons liever beoordelen op het product dan op een brochure. Dit is wat er al in zit, en wat dat zegt over hoe wij over het probleem denken.\n<\/p>

\nCompliance is jurisdictional, not generic\n<\/h3>

\nRegulatory coverage in the product today includes UK health and safety obligations, German DGUV requirements for electrical installation and machinery maintenance, and per-country statutory inspection cycles. An obligation means something different in each country, and the system treats it that way.\n<\/p><\/article>

\nMulti-country was the starting point, not a later port\n<\/h3>

\nEvery address carries its own jurisdiction, timezone and coordinates. Business calendars are holiday-aware per jurisdiction. Spending limits and approval workflows work across currencies, and B2B invoicing supports the reverse charge mechanism.\n<\/p><\/article>

\nObligations change, so they are yours to edit\n<\/h3>

\nObligation categories are defined and edited by you. A requirement we have not already covered is a configuration change you make yourself, not a development request and a place in somebody's queue.\n<\/p><\/article>

\nOne platform, not a suite of separate tools\n<\/h3>

\nFacility management is our main product and it is where our development effort goes. Project management sits alongside it. Both run on the same records, the same permissions and the same audit trail.\n<\/p><\/article><\/div>

\nThat is the experience on offer: depth in a specific problem, and a system designed from the start by people who expected to be asked hard questions about it.\n<\/p><\/div><\/section>

\nWhat that means for you\n<\/h2>