The Federal Energy Regulatory Commission's Form 1 — the annual report of major electric utilities, licensees, and others that section 304(a) of the Federal Power Act and 18 CFR Part 141 require each major electric utility, licensee, and other public utility subject to the FERC's jurisdiction to file annually with the Commission by April 18 of the year following the calendar year being reported — produces one of the most comprehensive publicly accessible records of customer-side electric-utility operational and financial activity in the United States. The FERC eLibrary public document system returns the Form 1 filings from approximately one hundred and ten major electric utilities that exceed the major-utility threshold (one million megawatt-hours of total annual sales or one hundred megawatt-hours of annual sales for resale or two hundred megawatt-hours of annual gross interchange out or five hundred megawatt-hours of annual wheeling for others), and the Form 1-F filings from non-major utilities and the FERC Form 3-Q quarterly filings provide complementary coverage of smaller utilities and quarterly reporting periods. The filings are submitted in the FERC's eForms XBRL-tagged format that enables programmatic extraction of the utility identifications, the schedule classifications, the filing dates, and the schedule-content disclosure narratives. Together with the related FERC Form 60 service-company filings, the FERC Form 714 transmission-system-data filings, and the FERC Order No. 890 Open Access Transmission Tariff filings, the FERC Form 1 archive is the largest publicly accessible source of customer-side product mentions in the energy-management, transmission-operations, asset-management, and regulatory-compliance technology sectors in the US electric-utility industry — and almost none of it is being systematically extracted as social proof by the energy-management, transmission-operations, asset-management, and regulatory-compliance companies whose products are being mentioned.
The under-extraction is not because the archives are inaccessible. The FERC eLibrary system publishes the filed documents in real time, the eLibrary search interface allows full-text and metadata queries across the filing corpus, and the FERC eForms system provides the structured-data extracts that enable programmatic processing of the XBRL-tagged elements. The under-extraction is because the energy-utility social-proof workflow has not been constructed to handle the highly regulated and quasi-judicially adjudicated disclosure source format — the FERC Form 1 filings read as operational and financial reporting documents rather than as product endorsements, and the adjacent Form 60 service-company filings and Order 890 tariff filings read as regulatory-compliance documents rather than as customer outcomes. This guide formalizes the four-stage extraction workflow that converts the archives into citable customer outcomes, the discrimination between the major-jurisdictional-utility axis and the non-major-utility axis, and the attribution-safe quoting framework that meets the FERC's Standards of Conduct under 18 CFR Part 358, the North American Electric Reliability Corporation's Critical Infrastructure Protection (CIP) reliability standards' confidentiality framework, and the state-level public-utility-commission marketing-restriction frameworks that apply at the retail-distribution end of the supply chain.
Why the FERC Form 1 archive is under-extracted as social proof
The FERC Form 1 filings are the most counterintuitive social-proof sources in the US electric-utility technology sector. The filings are submitted by major electric utilities as required regulatory disclosures under the Federal Power Act and the FERC's implementing regulations, and the surface content is the operational and financial reporting record — the comparative balance sheet schedules in pages 110-113, the statement of income in pages 114-119, the statement of retained earnings in pages 118-119, the statement of cash flows in pages 120-121, the notes to financial statements in pages 122-123, the electric operating revenues schedule in pages 300-301, the sales of electricity by rate schedules in pages 304-305, the electric operation and maintenance expenses schedule in pages 320-323, the depreciation and amortization of electric plant schedule in pages 336-338, the regulatory commission expenses schedule in pages 350-351, the research, development, and demonstration activities schedule in pages 352-353, the distribution of salaries and wages schedule in pages 354-355, the common utility plant and expenses schedule in pages 356-357, the amounts included in ISO/RTO settlement statements schedule in pages 397-398, the purchased power schedule in pages 326-327, the transmission of electricity for others schedule in pages 328-330, the transmission of electricity by others schedule in pages 332-333, the transmission lines added during year schedule in pages 424-429, the substations schedule in pages 426-427, the electric energy account schedule in pages 401-402, the monthly peaks and output schedule in pages 401-402, the steam-electric generating plant schedule in pages 402-403, the hydroelectric generating plant schedule in pages 406-407, the pumped storage generating plant schedule in pages 408-409, the generating plant statistics schedule in pages 410-411, and the other electric utility plant schedules. The technology platform names — the specific energy-management system, the specific outage-management system, the specific advanced-metering-infrastructure platform, the specific distribution-management system, the specific transmission-asset-management platform, the specific demand-response platform, the specific work-order-management platform, the specific regulatory-compliance reporting platform — are not directly named in the financial schedules themselves; the platform mentions appear in the notes to financial statements that disclose the major information-technology asset additions and depreciation periods, the research, development, and demonstration activities schedule that describes the technology investments in progress, the distribution of salaries and wages schedule that identifies the operating-technology departments, and the supplementary materials that utilities file alongside the primary Form 1 schedules.
The surface read of the FERC Form 1 archive is therefore neutral — the filings document the utility's operational and financial activity without editorializing about any vendor. The under-extraction is the failure to recognize that the FERC Form 1 disclosure is the regulatory-anchor evidence that supports the technology-platform mentions in the adjacent operational and reliability disclosures. The Form 1 archive documents the utility's major-utility status, the utility's revenue and load metrics, and the utility's continuous-disclosure-compliance history; the notes to financial statements document the technology platforms the utility has capitalized as utility plant; the research, development, and demonstration schedule documents the technology investments the utility is testing for future deployment. The extraction workflow that joins the FERC Form 1 data with the adjacent disclosure documents produces a social-proof asset that documents both the product deployment and the utility's regulated-utility status — the adjacent disclosure establishes the product mention, the Form 1 archive establishes the utility's regulatory-anchor status, and the joined record establishes the citable customer outcome that the energy-utility-technology company can use as social proof.
The FERC Form 60 service-company filings are the second source. The Form 60 is the annual financial and operating report that holding-company-affiliated service companies file under 18 CFR Part 366, and the Form 60 includes the service-company expense schedules and the affiliate-transactions disclosures that document the centralized technology services the service companies provide to the holding-company affiliates. The Form 60 filings include narrative descriptions of the service companies' centralized operational and IT infrastructure, the third-party technology vendors the service companies engage, and the technology platforms that support the centralized-services workflow. The Form 60 filings are extractable as social proof of the technology platform's role in the holding-company-system's centralized operational infrastructure; the surface-read approach misses the proof because the filings are framed as service-company financial-and-operating disclosures rather than as customer success stories.
The two sources are complementary because they cover different stages of the utility's operational relationship with the technology platform. The Form 1 archive covers the operational and financial output of the utility's regulated activities — the revenues, expenses, and asset additions the utility has reported using the platform-enabled operational infrastructure. The Form 60 archive covers the centralized service-company infrastructure that produces the operational outputs across the holding-company-affiliated utilities — the platforms the service company has deployed to enable the centralized-services workflow. The extraction workflow that handles both sources produces a social-proof asset library that covers both the operational-output axis and the centralized-infrastructure axis — and the library reads as more credible than a marketing-constructed social-proof library because the source materials are public FERC regulatory filings that the prospective customer can independently verify against the eLibrary system.
The four-stage extraction workflow
The extraction workflow consists of four sequential stages that convert the source archives into citable customer outcomes. The workflow is designed to maintain the legal and reputational safety of the extracted content; the staged construction prevents the premature publication of content that has not been verified for the attribution-safe quoting requirements that FERC-regulated, NERC-regulated, and state-PUC-regulated marketing must meet.
Stage 1 — Source-archive identification and corpus construction
The first stage identifies the source archives relevant to the energy-utility-technology company and constructs a corpus of source documents for extraction. The FERC eLibrary search index is queried by the docket-class filter (FA — Form 1 annual report, FB — Form 1-F annual report, FC — Form 3-Q quarterly report, FD — Form 60 service-company annual report, EL — electric rate filings, ER — electric tariff filings, OA — Open Access Transmission Tariff filings), the utility-type filter (investor-owned utilities, federal power-marketing agencies, public-power utilities subject to FERC jurisdiction, RTOs and ISOs, transmission-only utilities), and the platform-mention filter (the company's product names, the company's parent organization name, the company's product-category terms); the query returns the filings that mention the company's products in the notes to financial statements, the research, development, and demonstration activities schedule, the distribution of salaries and wages schedule, or the supplementary materials that utilities have filed alongside the primary Form 1 schedules.
The corpus construction is the foundation of the extraction workflow because the corpus determines the upper bound of the extractable customer mentions. The corpus should be constructed broadly in the first iteration — all Form 1 and Form 60 filings within the past three years, all utility types and jurisdictions relevant to the company's product, all platform-mention queries the company has documented — to maximize the recall of the extractable mentions, and then narrowed in subsequent iterations to focus on the highest-yield sub-corpora that produce the most citable mentions.
Stage 2 — Product-mention extraction with structured-attribute capture
The second stage extracts the product mentions from the corpus and captures the structured attributes that support the attribution-safe quoting framework. The extraction is performed on the notes to financial statements, the research, development, and demonstration activities schedule, the distribution of salaries and wages schedule, the regulatory commission expenses schedule, the amounts included in ISO/RTO settlement statements schedule, and the Form 60 service-company expense schedules — the documents that contain the narrative descriptions of the technology platforms utilities have deployed. The extraction identifies the product name, the utility name (including the holding-company parent affiliation where applicable), the deployment context (the major-utility status, the FERC jurisdictional class, the service territory, the customer count from the matched schedules, the rate-class composition), the outcome (the operational-process benefit the platform enables, the regulatory-compliance benefit the platform supports, the financial-reporting benefit the platform provides), and the source-document citation (the FERC eLibrary accession number, the docket number, the filing date, the schedule-page reference, the Form 60 reference where applicable).
The structured-attribute capture is the workflow's protection against the attribution-safe quoting requirements under the FERC's Standards of Conduct under 18 CFR Part 358 and the state-PUC marketing-restriction frameworks. The extracted mentions are stored as structured records with the FERC accession number as the anchor; the citation allows the workflow to reconstruct the original context of the mention when the marketing team uses the mention in a social-proof asset. The citation also allows the workflow to detect mention-context decay — when a utility's Form 1 has been updated to remove the mention, when the utility has been acquired or has consolidated, when the utility's major-utility status has changed, when the utility's service territory has materially changed, when the holding-company structure has materially reorganized — and to retire or update the mention before it becomes inaccurate.
Stage 3 — Attribution-safe quoting framework application
The third stage applies the attribution-safe quoting framework to the extracted mentions. The framework consists of five constraints that the social-proof asset must satisfy. The mention must accurately attribute the product to the utility that filed the disclosure — the social-proof asset must not aggregate mentions across utilities in a way that suggests a single utility made claims it did not in fact make. The mention must accurately attribute the deployment context to the source document — the social-proof asset must not represent a major-utility deployment as a non-major-utility deployment or a transmission-only-utility deployment as a vertically-integrated-utility deployment. The mention must accurately attribute the outcome to the deployment context — the social-proof asset must not represent the utility's overall reliability or rate-case-outcome performance as attributable to the platform when the platform supports only a subset of the utility's operational infrastructure. The mention must cite the source document — the social-proof asset must link to or otherwise reference the FERC eLibrary accession number. The mention must respect the utility's brand-use preferences and the utility's FERC-Standards-of-Conduct and state-PUC marketing restrictions on third-party-attribution marketing — the social-proof asset must not represent the utility as endorsing the product company if the utility has not in fact endorsed the company in a form authorized under the FERC and state-PUC restrictions.
The five constraints are the workflow's compliance with the FERC marketing-affiliated-transaction rules under 18 CFR Part 358, the NERC CIP reliability-standards confidentiality framework that protects bulk-electric-system reliability-related information from disclosure, and the state-PUC consumer-protection-marketing-restriction frameworks that apply at the retail-distribution end of the supply chain. The constraints are also the workflow's protection against the utility's potential challenge to the social-proof asset — the utility's challenge is most likely to succeed when the asset misrepresents the deployment context, the outcome, or the utility's endorsement, and the utility's regulatory exposure under its own continuous-compliance and Standards-of-Conduct obligations may motivate the utility to assert the challenge if the asset implies an unauthorized endorsement.
Stage 4 — Social-proof asset construction and continuous-monitoring framework
The fourth stage constructs the social-proof asset from the extracted mentions and establishes the continuous-monitoring framework that maintains the asset's accuracy over time. The asset construction selects the highest-yield mentions from the structured-attribute records and combines them into a social-proof asset format — the customer success story, the deployment case study, the testimonial wall, the proof-point statistics, the comparison page reference, the platform-adoption-by-utility-type heatmap — that the energy-utility-technology company uses in its marketing. The construction respects the five attribution-safe constraints and includes the source-document citation in the asset itself.
The continuous-monitoring framework tracks the source documents over the asset's deployment period and detects the mention-context decay that requires asset updates. The framework re-queries the FERC eLibrary search index at each new annual Form 1 filing window (April 18 each year for the calendar-year-preceding filings) to identify operational and financial updates that affect the utility's major-utility status, re-queries the Form 60 archive at each new annual Form 60 filing window to identify centralized-services updates, re-queries the Order 890 OATT filings to identify transmission-tariff updates that affect the utility's regulated operations, and updates or retires the asset when the source documents change in ways that affect the mention's accuracy.
The major-utility versus non-major-utility discrimination
The major-utility axis and the non-major-utility axis are the two analytical axes the extraction workflow must discriminate. The major-utility axis captures the approximately one hundred and ten utilities that exceed the major-utility threshold (one million megawatt-hours of total annual sales or the other thresholds in 18 CFR Part 141.1) and must file the comprehensive Form 1 with all schedules — the axis is the high-volume coverage axis of the workflow because the Form 1 schedules contain the deepest narrative content about the utilities' operational infrastructure. The non-major-utility axis captures the smaller utilities that file the Form 1-F simplified annual report or the Form 3-Q quarterly report — the axis is the supplementary coverage axis of the workflow because the smaller-utility filings contain less detailed narrative content but capture utilities outside the major-utility-coverage scope.
The discrimination is critical for the attribution-safe quoting framework because the two axes have different regulatory contexts. The major-utility axis is the most reliable for high-content product mentions because the Form 1 schedules require the comprehensive narrative disclosures that contain the platform mentions; the workflow can rely on the major-utility data as the anchor for the high-yield social-proof asset. The non-major-utility axis is suitable for breadth-of-deployment mentions because the smaller utilities cover a wider geographic and customer-class footprint than the major utilities; the workflow must apply additional context to non-major-utility mentions to avoid misrepresenting the utility's operational scale or service territory.
The attribution-safe quoting framework
The attribution-safe quoting framework consists of five constraints that the workflow applies to each extracted mention. The constraints reflect the FERC's Standards of Conduct and the state-PUC marketing-restriction frameworks.
Constraint 1 — Utility-level attribution accuracy
The first constraint requires that the mention accurately attribute the product to the utility that filed the disclosure. The constraint is straightforward in single-utility contexts but requires care in holding-company contexts — when the mention appears in a Form 60 service-company filing, a holding-company-consolidated disclosure, or a multi-utility joint-deployment disclosure, the constraint requires that the social-proof asset attribute the mention to the specific utility entity that the disclosure identifies as the user of the product, not to the holding-company parent or the service-company affiliate as a whole.
Constraint 2 — Deployment-context attribution accuracy
The second constraint requires that the mention accurately attribute the deployment context to the source document. The constraint guards against the most common attribution error — representing a transmission-only-utility deployment as a vertically-integrated-utility deployment or a service-company-centralized deployment as a utility-specific deployment. The constraint requires that the social-proof asset preserve the document-type context of the source — the Form 1 schedule context is the operating-utility context, the Form 60 schedule context is the centralized-service-company context, the Order 890 OATT context is the transmission-tariff context, and the asset must not blur the distinctions.
Constraint 3 — Outcome attribution accuracy
The third constraint requires that the mention accurately attribute the outcome to the deployment context. The constraint guards against the most subtle attribution error — representing the utility's overall reliability or rate-case-outcome performance as attributable to the platform when the platform supports only a subset of the utility's operational infrastructure. The constraint requires that the social-proof asset attribute the outcome at the granularity the source document supports — the platform-supported workflow rather than the utility's overall reliability, the platform-supported process step rather than the utility's overall operational result, the platform-supported regulatory benefit rather than the utility's overall regulatory standing.
Constraint 4 — Source-document citation
The fourth constraint requires that the mention cite the source document. The constraint provides the verifiability anchor that the prospective customer uses to independently verify the social-proof asset against the FERC eLibrary system. The constraint requires that the social-proof asset include the FERC eLibrary accession number, the docket number, the filing date, and the schedule-page reference for each cited mention; the citation may also include the schedule-name and the specific passage that the social-proof asset relies on, which strengthens the verifiability anchor.
Constraint 5 — Utility brand-use and FERC-Standards-of-Conduct restriction respect
The fifth constraint requires that the mention respect the utility's brand-use preferences and the FERC's Standards of Conduct and state-PUC restrictions on third-party-attribution marketing. The constraint guards against the legal-and-reputational-risk error — representing the utility as endorsing the product company if the utility has not in fact endorsed the company in a form authorized under the FERC's Standards-of-Conduct restrictions, the state-PUC consumer-protection rules, or the utility's own marketing-affiliated-transaction policies. The constraint requires that the social-proof asset clearly distinguish between the utility's regulatory disclosure (which is publicly extractable as factual record) and the utility's endorsement (which requires the utility's separate express authorization under the FERC's and state-PUC's restrictions on third-party-attribution marketing).
Operational implementation considerations
The operational implementation of the four-stage extraction workflow requires several technical and organizational considerations. The FERC eLibrary search index supports machine-readable querying through the public search interface, and the workflow can be automated with a corpus-construction script that queries the index by the docket-class filter, the utility-type filter, and the platform-mention filter and that downloads the matching filings for extraction. The product-mention extraction can be performed with a combination of regular-expression matching on the platform-mention vocabulary and named-entity-recognition processing of the schedule narrative descriptions; the named-entity-recognition processing requires training data that the company can construct from a hand-annotated sample of its own filings corpus.
The structured-attribute capture requires a database schema that supports the FERC eLibrary accession number as the anchor identifier and that captures the utility name, the deployment context, the outcome, and the citation as structured attributes. The continuous-monitoring framework requires a scheduled re-query mechanism that runs at each new annual Form 1 filing window (April 18) and Form 60 filing window and that detects the mention-context decay through comparison of the current and prior filings. The attribution-safe quoting framework requires a marketing-team review process that applies the five constraints to each extracted mention before the mention is approved for use in a social-proof asset.
The conversion to citable customer outcomes
The FERC Form 1 archive contains hundreds of utility-years of filings that mention technology platforms used by US electric utilities in their operational, financial, and regulatory-compliance activities. The extraction workflow that this guide formalizes converts the archive into the citable customer outcomes that energy-utility-technology companies can use in their social-proof construction. The conversion is bounded by the attribution-safe quoting framework that protects the company against the FERC's Standards-of-Conduct restrictions, the utility's regulatory exposure to unauthorized-endorsement representations, and the company's own reputational risk if the social-proof asset misrepresents the utility's deployment.
The conversion is also bounded by the FERC Form 1 archive's regulatory-disclosure character — the archive is a record of operational and financial reporting activity, not a record of customer endorsements, and the social-proof asset must preserve the regulatory-disclosure context in its presentation. The energy-utility-technology company that respects the regulatory-disclosure context constructs a social-proof asset that the prospective customer reads as a factual record of platform deployment by a FERC-jurisdictional electric utility; the company that ignores the regulatory-disclosure context constructs a social-proof asset that the prospective customer reads as an unauthorized endorsement representation and that the utility may challenge under the FERC's Standards-of-Conduct restrictions or the state-PUC consumer-protection rules.
Closing framework
The FERC Form 1 archive is one of the largest publicly accessible sources of customer-side product mentions in the US electric-utility technology sector. The extraction workflow that this guide formalizes converts the archive into citable customer outcomes that energy-utility-technology companies can use in their social-proof construction. The workflow consists of four stages — source-archive identification and corpus construction, product-mention extraction with structured-attribute capture, attribution-safe quoting framework application, and social-proof asset construction with continuous-monitoring framework — and the workflow's effectiveness depends on the company's commitment to the attribution-safe quoting framework and the continuous-monitoring framework that maintain the asset's accuracy over time. The energy-utility-technology company that implements the workflow systematically converts the under-extracted archive into a social-proof asset library that the prospective customer reads as more credible than a marketing-constructed social-proof library because the source materials are public FERC regulatory filings that the prospective customer can independently verify against the FERC eLibrary system.