GB Grid Evidence / Evidence Requests

When should you ask for a record that is not public?

First establish what the public records included in the review leave unresolved after the stated checks, why the answer matters to the decision, and the smallest additional record that could test the remaining question.

The review concerns the evidence path between the public record and the claim being relied on—not the asset in isolation. An unanswered public-record question is not an asset finding and does not automatically justify asking for non-public records.

The rule

The public record can raise a question. The decision under review determines whether that question needs to be resolved.

This is how LFR decides whether a bounded evidence request is justified. It does not assume that every comparison is available in every case. Repeated appearances across overlapping review windows are not automatically independent evidence and do not by themselves justify a request.

What exactly remains unresolved?

State the question without turning a difference, silence, or missing record into an explanation about the asset. If the records cannot yet be linked by identity, time, or quantity, stop at that limitation; do not describe them as inconsistent.

Are the records about the same thing and time?

Confirm the object, event window, units, direction, and what each record actually records.

Which exact records were used?

Keep the records as retrieved, with their visible versions, known revision behaviour, retrieval times, and hashes. A later copy is not automatically a certified final version.

Can the public record narrow or resolve it first?

Check the unit's own earlier public record. Where a valid comparison is available, check the same-period regional or system context. Then ask whether reporting rules, instrument changes, or another comparable public source supports the proposed interpretation, limits what it can mean, or leaves the question unresolved.

Does the answer affect a real decision?

Name the claim or decision that depends on the answer. If none does, leave the question open and do not manufacture a request.

What is the smallest additional record that could test the question?

Ask only for the specific non-public record capable of testing the remaining question. Do not request a broad internal-data pack by default.

Examples

What a bounded request can look like

Each example begins after identity, time, retrieval, instrument, and relevant public-channel checks. The examples do not establish that a problem exists. The same public pattern does not automatically select the same evidence request.

Accepted-action cadence

The checked sequence still leaves a decision-relevant question

Open question. After checking the unit's own history, available same-period regional context, and the rules of the dispatch record, the accepted-action sequence still leaves a specific question that matters to the decision.

Minimum record needed. The narrowest record capable of testing whether the public accepted-action sequence has a corresponding owner-held dispatch or control sequence over the same window.

Declaration / settlement record

A declared capability and a settlement-metered record still leave a question unresolved

Open question. After confirming identity and time, the participant-declared capability and settlement-metered record still leave a specific comparison unresolved.

Minimum record needed. Whichever declaration, submission, meter-mapping, or availability record directly tests the remaining question—not all of them by default.

Registry / record identity

The records still cannot be linked to the same public identity

Open question. After checking the public identity link, the registry state and other public records still cannot be reconciled.

Minimum record needed. The authoritative identity or mapping record that directly tests the link. Commissioning or registry-update history is requested only where the unresolved question concerns timing or status.

Providing or withholding a requested record does not change the public-record observation. Non-response is not treated as a finding, confirmation, or an adverse inference about the asset.

Why the question matters

The same public question can matter for different reasons

Changing the reviewer does not change the underlying observation. It changes which decision, if any, requires the question to be resolved.

Underwriting / renewal

Which statements in the renewal file are publicly checkable?

Separate what the public records support from asset condition, loss history, and owner-held evidence.

Credit / portfolio monitoring

Which operating assumptions can be compared with public records?

Public comparison does not establish revenue, DSCR, residual value, or creditworthiness.

Acquisition / refinancing / DD

Can identity, public operating records, declared capability, and service scope be reconciled?

A source-by-source evidence checklist before technical conclusions.

Counterparty review

Which public questions require direct clarification?

Bounded reconciliation questions before relying on a public interpretation.

Discuss whether a review fits

Send the asset scope, the claim being relied on, and the decision it informs. LFR will first confirm which public records are available, what identity link can be established, when the records were retrieved, and what they can support.

info@lfrfrequency.com →