Every compliance claim, tested against its evidence

A renewable owner with about 100 plants in the US and Canada kept its NERC and regional compliance status in two lists, maintained by hand and in good faith. Both lists said most claims were complete. Behind them sat tens of thousands of files in plant folders.

Nobody had checked, plant by plant and standard by standard, whether any of those files said what the standard requires. The owner's own manual passes covered a dozen or two plants at a time. The head of compliance needed a defensible picture of the gaps for a multi-year budget, and a full engineering audit would have taken longer than he had.

Each NERC standard that applies to a plant has requirements, and for each one the owner must be able to show that it complies. A list that says complete is not evidence. An auditor asks for the document, the page and the date that prove the claim, and expects the document to be current.

Our review counted a document as supporting a claim only when it was dated, stated the required result for that plant, sat inside its re-verification cycle, and no later settings or equipment change was on record. A claim counts as documented when our review found such a document or the owner's own tracker records one.

We took every claim the owner's own lists made: about 1,900 claims across about 70 operating plants and 50 standards and regional items. Then we read every document in the compliance, study and procedure folders against each requirement. More than 23,000 documents were opened and read in full, including scans, spreadsheets, emails and archives.

Each claim received one of four verdicts: supported, out of date, not enough, or nothing on file. Every verdict comes with a one-sentence citation naming the document, the page and the date, so a reviewer can open the file and check the line. About 25,000 citations were written. A second, independent reader checked every quoted excerpt against its page before anything shipped.

Then we folded in the owner's own tracker, read exactly as the owner wrote it, so that every claim shows what either source holds.

With the owner's own tracker folded in, about 45 percent of the claims across the fleet have a document on record. The rest name the gap to close.

The most common reasons a document fell short: a requirement with no document speaking to it, a related document that did not state the required result, an undated document, a consultant summary filed without its source, a template filed as a record, and a study superseded by a settings change.

A handful of items had no document on record at any plant. Event reporting and the transmission coordination standards were the best documented, with a document on record at nearly every plant.

The review went from approval to a delivered workbook, memo and executive summary in about two days. Within three weeks the verdicts and their evidence links were loaded into the owner's compliance record, where the proof for any claim can be produced in seconds.

Five weeks later the review re-ran against 23,000 files, the owner's own tracker was folded in, and the record was refreshed in one afternoon: about 70 plants, 11,000 requirement statuses and 14,800 evidence links, each status carrying the reason behind it. Across the fleet, 45 percent of the claims now name a document; the rest name the gap to close.

Done by hand, the same review comes to about 3,000 hours by our estimate: two experienced analysts for nine months, doing nothing else.

Every gap states the reason and the fix: file the post-change study, date the undated document, replace the template with the completed record, or confirm the evidence exists elsewhere.