For Alaska electric co-ops, utilities & telecom providers
Rural Alaska utilities carry the regulatory and reporting load of much larger organizations on a fraction of the staff. We build agents that draft the filings, structure the field reports, and keep members informed during an outage.
Built in Anchorage · we publish our source code · no long-term lock-in
Written by Kristian Baer, Northtek · Anchorage, Alaska · Updated 2026-08-21
The short answer
It gives a six-person office the administrative output of a much larger one. Regulatory filings, federal grant reporting, and member communication are all document-heavy, deadline-driven, and rule-bound, and they compete for the same handful of people who also handle billing and dispatch. An agent drafts the filing from your operational data, assembles the grant report from the same records, and drafts member notifications during an outage using the information the field crew is already sending. It does not operate equipment, it does not switch anything, and it does not make restoration decisions. It removes the paperwork that currently keeps your operations manager at a desk instead of in the field.
The operating reality
A rural Alaska co-op files with the same regulators, reports on the same federal programs, and answers to the same members, with an office that fits in one room.
Filings, grant reports, member service, and dispatch often share the same three people. Every deadline competes directly with operations.
Broadband and energy infrastructure funding comes with reporting obligations that continue for years after construction ends, long after the project team has moved on.
Members in a village want to know what happened and when power returns. Silence during an outage does more lasting damage than the outage itself.
Pole, line, and equipment records live across paper maps, spreadsheets, a GIS layer, and the memory of a lineman who is close to retiring.
Six workflows we build
Chosen for offices where the same person handles the filing and the phone.
01
02
03
04
05
06
First 30 days
For most co-ops that is either the recurring regulatory filing or a federal grant report, both of which pull the same person away from running the utility.
We work backward through your most recent submission and identify which sections were reassembled from scratch and which were essentially unchanged from the prior period.
It pulls current-period data, drafts the recurring sections in your established structure, and flags anything that differs from the prior period in a way that looks like an error.
It drafts the next filing while your team prepares theirs normally. You compare both before deciding whether to rely on it.
What you own at day 30
A filing assembly agent connected to your operational data, a side-by-side comparison against a filing your team prepared, the source code and configuration, and a runbook your office manager can follow when the general manager is out.
What we built, in the open
A large utility has a regulatory affairs department to check the filing. You have a general manager doing it at night. That changes what the software has to do: it cannot merely produce a draft, it has to make the draft checkable quickly by someone who is already out of hours.
A verification gate that flags figures a source record does not support, so review is a targeted pass rather than a full reread of everything the system produced.
A language built so an agent's steps are readable. When a filing figure is questioned months later, how it was derived is recoverable.
Our own memory server, which is why member data and asset records can stay inside your existing tenant rather than moving to a vendor platform your board never approved.
Public with commit history. A small co-op has less room than anyone to absorb a vendor whose claims cannot be checked.
Scope, stated up front
A small office cannot absorb a system that oversteps. Three boundaries that keep this useful rather than risky.
It never touches operations
No SCADA, no switching, no restoration decisions, nothing in the operational control path. Documents, reporting, and communication only.
It does not sign your filing
A drafted filing is a draft. Your general manager reviews and certifies it, and we will not build a workflow that lets anything file automatically.
Old records limit what is possible
If a line section only exists on a paper map in a drawer, the agent cannot answer questions about it. We will tell you what portion of your records is actually usable before you count on it.
Where your data goes
Member data and regulatory filings carry obligations a small office still has to meet. Four commitments we put in the agreement.
That is the size where it matters most. A large utility has a regulatory affairs department. You have a general manager doing it at night. The gain is proportionally larger, and the build is smaller because there are fewer systems to integrate with.
Yes. Program reporting is structured, recurring, and driven by data you already collect, which is exactly the profile that automates well. It assembles the package and flags gaps. Your team still reviews and certifies every submission.
Member records can stay inside infrastructure you control and are never used to train a model. For a small utility that usually means running inside your existing cloud tenant, which we set up as part of the build rather than as an upcharge.
That is normal and it is workable. We index what is machine-readable and report honestly on what is not. Scanned maps from the 1970s have a real error rate and we will tell you which parts of the estate you can trust rather than presenting a confident answer built on a bad scan.
No. Billing systems, outage management systems, and GIS all stay. We build the layer that reads from them and drafts the documents and messages people currently write by hand.
The pattern holds. Outage communication, field work orders, federal program reporting, and asset records are the same problems with different equipment names.
We will show you which sections an agent would have drafted and which ones still need your general manager. Sixty minutes, no cost.
Anchorage, Alaska · info@northtek.io · (907) 903-4353