For utility + energy operators
The utility planner that doesn't need a dedicated compliance team.
Describe the change — firmware update, relay replacement, SCADA point addition — and the plan comes back naming the evidence artifacts your auditor will expect. Is this asset classified as Bulk Electric System (BES)? Does it trigger a NERC CIP-010 baseline change? Does it touch your Electronic Security Perimeter (ESP)? Surfaced automatically. Works for large utilities that already have compliance teams and for smaller co-ops that need the scaffolding without hiring a dedicated NERC CIP analyst. Full compliance-tracking modules ship in the Professional tier (Coming Soon).
The regulations you’re accountable for
If you operate Bulk Electric System (BES) assets, these are non-negotiable. We bake them into the plan rather than leaving you to reconcile two systems.
- NERC CIP-010 — Configuration change management — the planner treats baseline config as a tracked entity.
- NERC CIP-005 — Electronic Security Perimeter — change impact on ESP flagged at scoping.
- NERC CIP-007 — System security management — patch + access change requirements surfaced.
- FERC Order 2222 — DER aggregation — relevant for any change touching aggregated resource participation.
What generic PM tools miss
Generic PM tools don't know what a Cyber Asset is, let alone whether a firmware update on a relay requires a baseline change record vs a routine maintenance note. Copilot will cheerfully generate a plan that misses the CIP-010 hook entirely.
If you run a dedicated compliance team, they're already stretched — adding another system slows them down. Your ops teams need structured project planning that gets the CIP vocabulary right day-to-day without a compliance handoff on every change.
If you're a co-op or smaller utility without that team — you need this scaffolding even more. The planner asks the asset-classification question up front, names the evidence artifacts, and makes the audit-trail export format something your regional entity auditor will recognize.
What changes when you use ChangePilot
Items below are tagged Available today or Coming Soon so you know exactly what ships in v1 vs what’s on the Professional-tier roadmap.
Plain-English scoping that speaks the CIP vocabulary
Type “firmware update on the SEL-421 line differential relay” and the planner pulls out the asset + the scoping questions (asset classification, dependent systems, baseline-change context) a CIP analyst would ask up front — not the generic ones a task manager would. Available today. (Dedicated CIP-005 / CIP-007 / CIP-010 workflow gates ship in the Professional tier — Coming Soon.)
Audit-trail PDF that holds up for an internal review
Every status change, every approval, every evidence upload — one-click PDF export with user + timestamp + justification + linked artifacts. We don't claim to ship a NERC-CIP-templated audit packet (the workflow modules will), but the underlying project record is signable + exportable today.
Built for the day-to-day changes, not just the quarterly audits
Team tier ($49/mo) is unlimited projects. Compliance suites built for the quarterly audit are heavyweight for the daily firmware patch or relay swap — so the small stuff lives in spreadsheets, and that's where the next finding comes from. ChangePilot is for the routine changes that need structure but not enterprise-grade overhead. Available today.
Coming Soon: full CIP-aware change workflow + lessons feedback loop
BES asset classification as a typed entity, ESP/EACMS impact flagged at scoping, evidence-chain templates a regional entity auditor would recognize, lessons-from-prior-changes surfaced at capture — these ship as the Compliance + Change Management modules in the Professional tier. v1 customers get structured planning + the CIP vocabulary in the planner today; the workflow modules layer on when they ship.
Try it — here’s a prompt that works for your world
Firmware update on the SEL-421 line differential relay protecting the 230 kV Cottonwood-Juniper circuit. Upgrading from R114 to R119 per vendor security advisory. Relay is a Medium Impact BES Cyber Asset inside an ESP. Change touches CIP-005 (firmware source + verification), CIP-007 (patch management), and CIP-010 (baseline config). Need pre-change baseline snapshot, signed change record, post-change validation against protection test plan, and rollback procedure on file.
Paste this into /screener/actions and compare the result to what Copilot gives you for the same prompt.
Test it with a CIP change you're planning.
Paste a real CIP-010 candidate. The plan we generate should name the right evidence artifacts. If we miss one your auditor cares about, tell us — getting this vertical precisely right is the difference between a curiosity and a buy.
Other industries we know
Don't see your industry? The planner works for any operationally-serious team — construction, agriculture, services, even multi-department HR rollouts. Try it free.