Utilities & energy
PUC tariff filing redline — proven, not just marked up.
A tariff sheet was revised, and someone has to show — and be able to prove — exactly what changed. Public utility commissions expect redlined tariff pages: the closest cousin of insurance SERFF practice. Redlineo produces that exhibit, and every output carries its own proof.
Same primitive, PUC vocabulary
The analogous filing, the analogous rate table.
-
The filing
Tariff sheets filed with a PUC
Tariff sheets filed with public utility commissions — PUCs expect redlined tariff pages, the closest cousin of SERFF practice. The strikeout/underline exhibit this tool produces is exactly that artifact, and the full redline is what you file. And the practice is not US-only: energy, water and telecom regulators across Europe, Canada and Australia require tariff filings with revised schedules — the same spreadsheet-heavy comparison.
-
The rate table
Rate schedules in spreadsheets
Rate schedules live in workbooks. Drop the approved and revised versions: the print areas become a paged Word redline mirroring the printed tariff pages, or a colored Excel review copy for reviewers who work in the spreadsheet. Rows and columns re-synchronize, so one inserted row shows as one inserted row.
What carries over unchanged
Every proof and report primitive comes with it.
- ✔Verified redlines. Accepting every change reproduces the revised tariff; rejecting every change restores the approved one — re-checked on every run and stamped ✔.
- ✔The certificate. SHA-256 fingerprints of the exact input files, recomputable by anyone with
sha256sum. - ✔A report with links. Every change numbered — none truncated — each line a click-to-jump link; rate impact computed for changed cells.
- ✔Excerpts on demand. "Changed content only" trims the output to the changed tariff pages, every omission explicitly marked; the full redline stays the filing artifact.
- ✔Metadata scrubbed. No leaked author names, company fields, editing time or revision fingerprints on any output.
- ✔The DMS round-trip. Compare versions straight from Alfresco and save the reviewed output back — integrity-verified before it is filed.
application.yaml. Adapting it to a utility's schedule numbering and commission conventions is a configuration exercise, not a new product.
Next
Built on the practice regulators built SERFF around.
The insurance filing workflow is the flagship — see the SERFF use case for the fully worked example, or the feature set in detail. Related domains: banking disclosures, standards bodies.