Right fit
When is this review useful?
When a real asset, portfolio, renewal, refinancing, acquisition, claim or due-diligence file contains a number, report or public trace that a reviewer must decide whether to trust, request or leave unresolved.
Review fit and scope / GB Grid evidence
Will a public-duty review close an evidence gap in your file?
Before commissioning a review, establish whether it fits the decision in front of you, what will change in the file, what you will receive, and what LFR will still refuse to conclude.
What the scoped review is designed to establish. A second-look measurement record: what named public sources can support under defined procedures, what remains unresolved, what they do not establish, and which evidence should be requested next. The written scope defines what can actually be issued. It is not an asset verdict.
Fit
Start with the decision, not the technology.
Not a fit
When is this not the right review?
Not for a market opinion, asset rating, failure or revenue prediction, or an internal engineering diagnosis. If the decision requires a health, safety, warranty, credit or underwriting conclusion, this review does not supply it.
Review owner
Who normally uses the file?
A technical asset manager preparing for renewal or refinancing; a risk engineer or technical underwriter reviewing a BESS book; or a lender and due-diligence reviewer deciding which owner-held records to request.
Entry input
What do you need from me first?
Start with the decision context, approximate basket size and relevant review date. Authorisation, confidentiality and output scope are agreed before LFR receives an asset or BMU list.
File outcome
What will be different when the review is complete?
The result is not another dashboard view. It is a review file that separates what the public record can support from what still needs evidence.
Map coverage
Record which authorised assets can be represented in the available public sources, which cannot, and where identity or source capability is insufficient.
Test cross-source coherence
Check whether another public source or channel changes, supports or leaves unresolved an apparent inconsistency before it is carried forward.
Build the request
State what remains open, what it does not establish, and the minimum owner-held record needed to resolve the question.
Important. An unresolved relationship between checked public records is not an asset finding. It is a reason to ask a bounded evidence question.
The offer
What can we scope today?
Quarterly pilot
What is the pilot designed to deliver?
The frozen pilot design includes a monthly Portfolio Status Sheet and Drift Map; an Evidence Request Queue and boundary records for open items; one to three Duty Trajectory Profiles where scoped; a close-out memo; and a recompute/hash appendix.
Working rhythm
How is the pilot designed to run?
The pilot design uses monthly review points and a 30-minute review call. The actual cadence and available outputs are confirmed in the written scope after coverage, identity and delivery-gate checks; this page does not promise an unscoped turnaround time.
Price boundary
What does it cost?
Fixed-scope owner-side pilots are priced from £15,000 per quarter, depending on basket size and review depth. The written proposal identifies which outputs have passed the relevant delivery gates and are included in scope. Insurer-side book reviews are scoped separately.
Pilot stage
What is the pilot testing?
Whether this evidence boundary fits the reviewer’s actual workflow: which questions became worth asking, what remained invisible, and where evidence should be requested earlier.
Delivery maturity. Exact named outputs are confirmed only after coverage, identity, product-routing and delivery-gate checks. The written scope, not this page, is the delivery commitment.
Practical objections
What else should I know before commissioning it?
Coverage
Which of my assets can you actually see?
The coverage stage is designed to classify assets as represented, not represented, identity-unresolved, or lens-insufficient. Whether a named coverage output can be issued is confirmed during scoping. LFR does not turn missing public coverage into a conclusion about the asset.
Bounded null
What if the checked public records support no further observation?
That remains a usable result: which sources and windows were checked, what observation thresholds, revision-noise, resolution or coverage limits applied, and why no further public inference or owner-evidence request was justified.
Your data
Do I need to hand over SCADA, BMS or revenue data first?
No. The entry review starts from public grid records and an authorised asset list. Owner-held data is requested only where a specific public question needs it; the default evidence route can run directly from the owner to its reviewer.
Naming
Will you publish my asset names?
No. Public pages are anonymous or aggregate. Named assets appear only in a client-authorised private review of that client’s own basket.
Claim traceability
How can I inspect what the report says?
Each reportable claim admitted to final delivery must be traceable to its source record, time boundary, retrieval record, hash trail, frozen method version, claim boundary, and inspection or recompute path. The delivery file anchors what was handed over; the appendix exposes the trace available for that claim.
No verdict
What will this review not tell me?
It will not score asset risk or infer internal condition. It records which relationships between the checked public records are supported, which remain unresolved, and which owner-held records would be needed to resolve them. Read the full boundary →
Next step
Start with a fit check, not a full commitment.
Send the decision context, approximate basket size and review date. LFR will first establish whether the public-source coverage, identity route and claim boundary can support a useful scoped review. If they cannot, the pilot should not be proposed.
No asset list is required in the first email. Authorisation scope, confidentiality, data route and output scope are agreed before named asset information is received.