About an hour of your team's time.

The honest version of what a rollout asks of you. Most of it is assembling files you already have; the part that needs an engineer is the part we do. If any of this looks heavier than you expected, say so on the scoping call and we will cut the first cluster smaller.

The data pack

Four things, sent by secure upload after the scoping call. Send them as they are — an incomplete asset register and a missing month of bills are findings, not blockers.

Twelve months of utility bills

Any DISCOM, any format — scans and photographs are fine. We need the full twelve so seasonality is visible.

Usually held by: Finance or facilities

Service and maintenance records

Whatever exists: handwritten logs, vendor PDFs, emailed reports. Gaps are useful information, so send them as they are.

Usually held by: Facilities or the FM partner

Asset register

Site, asset type, make, rating and install year where you have it. A spreadsheet is fine; so is an incomplete one.

Usually held by: Facilities or procurement

Site list with tiers

Which sites, in which cities, and how you classify them. This is what lets us cluster the analysis usefully.

Usually held by: Whoever owns the estate view

What you do not have to do

No IT project

The documentary phase needs no integration, no VPN and no access to your systems. Files arrive by secure upload.

No downtime

Instruments are fitted during service windows that were already scheduled. Nothing is taken offline for us.

One named owner

We need one person who can chase a missing bill. That is the single biggest determinant of how fast this goes.

Nothing confidential by email

Bills and service records go by secure upload after the scoping call, never as email attachments.

The timeline

Day 0Request submittedFive fields. No commitment attached.

Day 1–2Scoping callTwenty minutes. We agree the cluster and send the data-pack checklist.

Client-pacedData pack arrivesAbout an hour of your team's time to assemble.

+10–15 working daysBaseline reportNormalised, benchmarked, plausibility-checked, written up.

+1 weekWalkthroughForty-five minutes on outliers and reconciliation gaps.

From therePhased rolloutDigitise, operate, instrument, optimise — stopping wherever the economics stop.

Who owns what

EAMOT doesYou do

Normalise and benchmark every recordSend the records, gaps included

Flag outliers and reconciliation gapsTell us which sites you already suspect

Recommend where instruments pay backConfirm runtime and tariff assumptions

Fit and commission on a service visitGive branch access on the scheduled day

Re-check every repair at T+5–7Nothing — this one runs on its own

Where the numbers end up

See Attest →

Integration

Verified figures, by API

Scope 1, Scope 2 and energy intensity carry into whatever you already report through, with the method and measurement window attached to each figure.

Integration

Original alongside the extract

Every decoded record keeps the original scan and the original-language text next to the structured data, so an auditor can walk back to the source.

Integration

Role-based access

Branch, region and portfolio views for admins, managers and auditors — the audit committee does not need a facilities login.

Integration

Your ticketing or ours

Attest can run your ticketing, or sit above the system you already use. The verification gate is answered by the asset either way.

Start with what you already have.

Send us twelve months of bills, your service records and your asset register. We'll return a documentary diagnosis of your estate: where the outliers are, what each site costs, and where your own numbers don't reconcile.

About an hour of your team's time to pull together. Ten to fifteen working days for us to return. No hardware, no capex, no commitment.