Account record
Utility profile
Legal name, jurisdiction, segment, parent, source-specific IDs and aliases where verified. Company delivery data needs reconciliation with the operating entity.
Proposed gas distribution research
A proposed research structure for utility profiles, program signals, timelines and account briefs.

Organization context
Parent totals require a gas scope check.
Account boundary
Resolve legal name, jurisdiction and source-specific IDs.
Participation route
Verify who sources the relevant work.
The connections are research questions. They are not a guaranteed purchase sequence or a real utility organization chart.
Proposed research architecture
A parent-company announcement is a useful starting point. The account record must identify the gas operating utility and jurisdiction before research can support a supplier decision.
Account record
Legal name, jurisdiction, segment, parent, source-specific IDs and aliases where verified. Company delivery data needs reconciliation with the operating entity.
Evidence record
A dated source, named program, documented scope and stage. The supplier interpretation stays separate from the agency or utility statement.
Decision record
Your offering, fit rationale, unresolved questions and next verification step. Qualification and procurement each require their own evidence.
Specify supplier category, utility segment, territory and evidence requirements. Separate gas programs from corporate totals.
Check reporting names, jurisdiction, aliases and operator IDs. Mark missing identifiers as unknown.
Read the source and later amendments. Preserve each publication date, period and status rather than replacing history.
Check implementation, procurement and qualification. Recommend a further check when evidence cannot support action.
| Stage | Evidence that may support it | What remains separate |
|---|---|---|
| Proposed | Application, draft plan or testimony | Approval, budget and purchase authorization |
| Approved | Effective decision or recorded municipal action | Implementation timing and procurement |
| Funded | Dated award or supported funding record | Remaining budget and supplier availability |
| Tendered | Current official invitation and scope | Eligibility, contract award and execution |
| Implementation | Dated execution or completion record | Any new supplier requirement |
Illustrative brief structure
This outline is a proposed deliverable format. It is not a completed utility brief or a promise of comprehensive public data.
Read one verified historical record ↗Supplier decision
Which dated program evidence supports our next account decision?
Connect only the documented scope to your offering. Mark technical fit and the buyer function as hypotheses until verified.
Retain missing procurement, implementation and budget fields as unknown. Name the next official record needed to support an action.
Initial scope would be agreed for selected US distribution accounts and supplier categories. No nationwide completeness, installed-vendor coverage or predictive safety score is claimed.
Documents can be amended, inaccessible or incomplete. Confidential specifications and sourcing invitations may not appear in the public record.
Review the source and freshness method ↗Define a research scope
Start with your offering, a defined utility segment and the account question you need to answer.