Documentation Using GridPreview
Reading a report
Interpret findings, citations, limitations and downloadable reports.
On this page
The seven report sections
| Section | What to look for |
|---|---|
| Summary | The most important supported findings and their implications |
| Grid | Separate published consumption and feed-in context |
| Site | Address-linked building facts and modeled solar context, where available |
| Options | Conditional actions grounded in the evidence, not engineering promises |
| Rules | Retrieved official guidance and its scope |
| Plan | Questions and next steps for the operator, owner or installer |
| Verification and limitations | Checks, source gaps, assumptions and unresolved uncertainty |
The writer is instructed to consolidate repeated limitations without dropping distinct caveats. Model compliance is checked, not assumed; the existence of a section is not itself proof that all its claims are supported.
Understand the result status
- Completed: no blocking gate failed and the output was not marked partial for source gaps.
- Partial: the report has incomplete source coverage. It can still pass all gates on its supported statements and truthful disclosures.
- Blocked: at least one required quality check failed. The saved candidate is not a validated report.
- Failed: execution did not produce a normal final report, for example after a provider or runtime failure.
- Cancelled: the job was stopped; cancellation is not successful validation.
A passing report is evidence-checked research, not an approval, safety certificate, connection offer or guarantee.
Follow the citations
Section citations identify the source records associated with a section. Structured factual claims also carry their own exact evidence references. A source somewhere in the section does not automatically support every sentence in it.
Review checks the claim’s actual references. If a sentence mentions both an address and modeled roof surfaces, citing only an address record is insufficient. The correct response is to separate the assertions and cite each properly, not attach every source indiscriminately.
Read dates correctly
An evidence record can have several dates:
retrievedAt: when the system fetched the record.observedAt: when an explicitly live observation was made.publishedAt: a supplied or verified publication timestamp.effectiveAt: the date the source fact is effective, where established.
Retrieving an old dataset today does not make its underlying fact current. Cached building records retain their original retrieval and observation times. A page’s “checked” date is not automatically a legal effective date.
Export a PDF
The PDF endpoint renders a dedicated, server-side A4 report from the saved input, output, configuration version and checks. It does not print the application dashboard or silently rewrite the analysis.
Sources and provenance start on a new page. Repeated provenance can be grouped only when its dates, status and limitations match, while original reference identities remain intact. Blocked, partial or unchecked reports are not presented as validated PDF reports.
Downloads are private and owner-scoped. See API reference for the endpoint.