Every answer names its source.
The document, the page and the passage. A citation the checker cannot verify is flagged on the answer, never hidden.
Solutions
Utilities and energy operators
Licence returns, audits
and board packs from one evidence base.
For the regulatory affairs team at an electricity, water or gas operator: the return, the register and the regulator's question from one evidence base, without pulling engineers off the network.
| Name | Status | |||
|---|---|---|---|---|
grid-maintenance-contract.docx Document · 90% confident | Suppliers | Confidential | Routed | |
Supplier agreements register Dataset · 95% confident | Suppliers | Confidential | Routed | |
Staff and department roster Dataset · 95% confident sensitive domain 'personnel': restricted route (owner + explicit grant only), review required | Personnel | Restricted | Needs review | |
Payroll summary by department Dataset · 70% confident domain 'expenses' → cfo, data_studio | Expenses | Confidential | Needs review | |
Old grid services maintenance schedule Dataset · 95% confident | Suppliers | Confidential | Routed |
5 of 12 files shown: those the router placed. The other 7 matched no domain and wait for a person to choose one.
Data Room · inventory · Product components, synthetic files
The evidence base
The files you already hold, classified, with their route and their review flag.
The Data Room indexes the documents, spreadsheets and exports your teams already keep. Each row carries its domain, its sensitivity tier and whether it was routed to a Desk or held for review.
What the regulator can check
Three things a regulator can check for themselves.
Every read is permitted, and logged.
A member sees only what they may see, in every answer and every run. The audit log shows who asked, and when.
Every export carries its sources.
A workflow run records every document it read and holds for approval. The return leaves with its sources on record.
Today
The return is assembled by hand, every time.
One evidence base, and the return is built from it.
By hand
TodayWith iQ Pulse
What changesBy hand
Preparation by hand
Every audit and licence return pulls staff off the network to dig through files.
With iQ Pulse
Audit-ready by workflow
The audit checklist runs over the sources you select, records them, and holds for approval before export.
By hand
Scattered knowledge
Licence conditions, outage records, tariff filings and board papers live in different systems.
With iQ Pulse
Board packs with lineage
The figure in the board summary traces to the row that produced it.
By hand
Answers that depend on who was asked
Whether the organisation is compliant should not be a question with three answers.
With iQ Pulse
Cited answers
The document, the page and the passage behind every answer. An unverifiable citation is flagged, never hidden.
The workflows
Three workflows, from the licence to the board pack.
Shipped workflows, run over the documents you choose, with an approval step before export.
Extract obligations
Over licence conditions and regulations, with every source the run used on record.
Compliance DeskPrepare audit checklist
Over the sources you select, with an approval gate before export.
Compliance DeskCreate board summary
Over the month's financials you select, held for approval; the variance drilled to its department and the board pack are the CFO Desk's own.
CFO DeskWhich conditions of the operating licence require a report or return to the regulator, and how often?
The operating licence requires the following reports or returns to the regulator:
- Transmission Losses Reporting: Transmission losses must be reported quarterly, and the losses must not exceed a ceiling of 6.50% .
- Planned Outage Notices: Notices for planned outages must be lodged with the regulator at least 21 days in advance .
These conditions ensure compliance with performance standards and operational transparency.
Sources
Knowledge Desk · answer with citations · Product components, synthetic files
The answer
The question the auditor asked, answered with the clause behind it.
Ask across the licence, the filings and the registers. Each answer cites the document and the page it came from, and says so when it cannot.
Every return, every office
Licence compliance reportingTariff and rate filingsIncident and outage reportingBoard packsSupplier and procurement reviewsRegulatory changeAsset and maintenance recordsAudit evidence
The Desks
The Desks utilities teams reach for.
Before procurement asks
The four questions a utilities purchase turns on.
- Where is our data hosted, and can it stay in our jurisdiction?
- Region-pinned storage for Enterprise customers is on the roadmap and not yet shipped. Ask where your data is hosted before you sign and we will answer in writing.
- Can it run on our own infrastructure?
- Enterprise plans can run in your own cloud or on-premise, by arrangement. Every other plan runs on the hosted service.
- Does it connect to our document system?
- Uploads on every plan. Google Drive from Starter, S3 and Google Drive on Pro, SharePoint and Confluence on Enterprise. The CFO Desk's accounting connectors come with Pro and Enterprise.
- What does procurement get?
- Security questionnaires, penetration test reports, SOC 2 documentation and other security artefacts on request, from one address. Encrypted at rest (AES-256) and in transit (TLS 1.3), hosted with a SOC 2 attested cloud provider.
Next step
Answer the regulator
with the evidence attached.
Bring a licence condition and the question the auditor asked. We will show you the answer, its evidence and the approved export it becomes.
Security
Encrypted at rest (AES-256) and in transit (TLS 1.3), hosted with a SOC 2 attested cloud provider. Your data never trains a model.
Security page