Every job I have had in energy has involved the same painful week. A new rule drops, and someone has to read it, work out what it actually asks for, and write that down in a way a team can build. Usually that someone was me, and usually it took far longer than it should have.
So I built a tool to do the first pass. I call it RegOps. You give it a regulation as a PDF, and it reads the whole thing and hands back the documents I would normally write by hand.
What it produces
- An obligations register, so nothing in the rule slips through
- A traceability matrix that links each obligation to where it is handled
- A gap analysis, user stories and a test plan
So far it has read 253 pages across four Australian energy regulations and pulled out 402 separate obligations. Work that used to take a team a few weeks now takes me an afternoon.
Where it still needs a person
It writes a first draft, not the final word. The model is good at finding obligations and not so good at judgement. It does not know which ones carry real risk, which ones our platform already handles, or where the business wants to draw the line. That part is still mine, and I think it should stay that way.
The point was never to remove the person. It was to clear the boring part out of the way so the person can spend their time on the decisions that actually matter.
That prototype is also the reason the idea scaled. A version of the same pattern is now the basis for a compliance traceability app I built at Kaluza, covering a large share of Australia's energy rulebook, running on Kaluza's own infrastructure and reviewed the way any other production tool is.