A building's energy identity lives in scanned PDFs, and it's wrong about one site in four. Ensite reads every agreement, diagram and permit, verifies the numbers against each other and the grid, and gives you one record you can plan capacity against.
A portfolio's energy identity (contracted capacity, transformer ratings, permit status) lives across scanned PDFs, signed letters and a spreadsheet someone inherited. Nobody owns it end to end, and the platforms selling portfolio energy intelligence assume it's already correct. It isn't. On our own rollout, a quarter of sites carried wrong basic data, and four-fifths of the rework traced back to it.
Every capability you'll hear about (Sources, Register, Reconciliation, Grid Passports) is one part of a single loop, not four separate destinations.
Ensite reads the unstructured documents wherever they already live: data rooms, DSO letters, the owner's own spreadsheet. No migration, no re-filing.
Part of SourcesEvery decision-driving field is typed into the Register with an evidence trail: which document, which page, which line it came from.
Part of RegisterEvery field is checked against every other source that claims to know it: the owner's register, the signed documents, public DSO and TSO data. Most tools stop at extraction and trust what they read first.
Part of ReconciliationEvery conflict is ranked by cost of error and put in front of a person to resolve, never silently picked for you.
Flagged for reviewThe result is one continuously maintained record per asset: a Grid Passport you can hand to a lender, a DSO or your own board.
Part of Grid PassportsThis is also why a headroom number means anything. Anyone can compute what a site can carry, if the data going in is clean. The reason almost no one can is that it isn't.
A wrong headroom figure doesn't just cost time to fix: it burns a grid-application cycle. Submit a capacity request built on a stale or wrong number and the DSO's queue doesn't forgive it: months lost, and a data-centre or fleet-electrification plan stranded behind it. The fix isn't more caution before every submission, it's a record that was verified before the number ever left the building.
Know what every site can carry, before capital moves.
Electrify on schedule: the data won't be the delay.
Retire the hand-maintained register, keep the judgment.
Cambio, Deepki, Measurabl and ProptechOS all sit above the data: dashboards and reporting that assume the underlying record is already clean. Ensite sits underneath, it produces and verifies the data they consume.
Every figure is checked against public DSO and TSO data as the source of truth, not just against itself.
Every figure is cited to the exact page it came from: the signed agreement, the diagram, the permit. Nothing is asserted without a source you can open. When two documents disagree, Ensite surfaces the conflict for a person to resolve instead of picking one silently, and shows an evidence-quality score per field.
Nowhere new. Ensite reads your data rooms, shared drives and inbox where they already live (SharePoint, Outlook, Excel, Google Drive, Box and more) following your existing permissions. There's no migration project, and everything stays exportable.
Connecting your first sources takes under a day. Most teams see their own documents turned into a verified record inside the first demo, and the register keeps filling as more sources sync in.
No. It removes the filing and cross-checking, not the decision. Conflicts and low-confidence fields are flagged for a person to resolve, every change is traceable in the Audit Trail, and your team spends time on judgment calls instead of folder archaeology.
A grid-connection data product needs someone who's lived what a wrong headroom number costs in the field, and someone who can build extraction that actually works on a scanned single-line diagram. Ensite is built by exactly that pair.
Bring one site's documents. See the verified record in 30 minutes, no commitment.