Key takeaways
- Permits, grid connection studies and land rights each run on their own clock, in a different inbox.
- GeniOS connects utility letters, county notices, consultant promises and lease dates to the project milestone they threaten.
- The development head gets one piece of intelligence per risk, with one owner and a date.
- Items close only on proof, such as the filed response, and nothing is sent without approval.
The problem
A utility-scale solar, wind or battery project runs a dozen approval tracks at once. The grid connection request moves through the utility's studies, each with a deposit, a data request and a deadline. The county wants a conditional use permit and a public hearing. The state wants environmental surveys. Landowners want lease payments on time and an extension if construction slips. Any one can stop the project, and most run on email.
Picture a Tuesday. The interconnection engineer is on a site visit and the permitting lead is at a county hearing. A utility letter arrives: the application is deficient, the single-line diagram does not match the stated capacity, and the site control evidence covers only part of the land. Cure within ten business days or the request leaves the queue. It lands in a shared inbox, gets forwarded once, and sits.
Nobody is careless. The engineer assumes the consultant has it. The consultant promised a revised diagram in chat but knows nothing about the site control gap. Three weeks later the project is out of the queue, and its start date moves back a year or more.
Why it slips today
Developers already track these dates. The permit tracker is a spreadsheet refreshed before the Monday pipeline meeting. The utility portal shows status only to whoever logs in. Land dates sit in a contract folder. Consultant promises live in chat. Each tool is right about its own piece and silent about the rest.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Utility deficiency letter | Interconnection engineer | Forwarded, then waits behind site work |
| County hearing notice | Permitting lead | Conditions agreed aloud, never assigned |
| Lease extension date | Land manager | Not linked to the new construction date |
| Consultant promise in chat | One project engineer | Nobody checks that it was kept |
A dashboard can show a red milestone. It cannot say which unanswered letter made it red, or who should answer it. Broad risk and compliance monitoring has the same gap: the obligations are known, but the owner and the date are not.
The solution
GeniOS reads the email, calendar, chat, documents and project tools your team already uses, read-only to start. It forms the company's goals from its own decks and meetings, such as reaching notice to proceed by a set quarter, and checks every open permit and grid task against them.
- Cure periods and response windows. Utility deficiency notices and agency comments with a deadline, matched to who must answer.
- Promises with no proof. A consultant or engineer who said a revised study, diagram or survey would follow, and nothing has arrived. This is commitment tracking applied to a project file.
- Dates that collide. A lease or permit that expires before the new construction start, or a deposit due before the board approves the spend.
- Hearing conditions. Commitments made to a county at a public meeting that have no owner yet.
See it on the whiteboard
Here is how one deficiency letter becomes one clear action, in five steps from left to right.
Cedar Flats can lose its grid queue spot
How: file the fixed diagram and a full site control exhibit with the utility by Monday.
- Your tools. The letter is in email, the promise in chat, the lease date in a sheet.
- GeniOS thinks. It sees one situation: a cure due in six business days, a diagram that never arrived, and a site control gap tied to an ending lease.
- Intelligence. Maria, the development head, gets one note: what is at risk, what to send, who owns it and by when.
- Delegated. The diagram goes to the engineer, the cover letter to a drafting agent. Nothing goes to the utility until she approves.
- Goal moves. When the filed response appears, the item closes and progress toward notice to proceed moves.
How GeniOS thinks and plans
GeniOS does not treat each email as its own task. It connects the pieces into one situation. What happened: a deficiency notice with a ten business day window. The pattern: a diagram promised in chat has not arrived, and the same consultant missed a date last quarter. The impact: without a cure the project leaves the queue, and this year's notice to proceed goal moves out by a study cycle. The owner: the person accountable for the grid track, not whoever received the letter.
It then checks the goal and the calendar. Is a hearing or board meeting coming first? Does the fix need a lease exhibit from another team? From that it picks one next step, one owner and a date a few days before the real deadline, so there is time to review. Storing information is not the same as acting on it; see why a company brain is not enough.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. Delegate hands the work to a person, an AI agent or both. The engineer gets the diagram fix with the utility's comment attached. A Reply Drafter prepares the cover letter. A Scheduler can book a call with the utility's study engineer. Nothing reaches a utility, county or landowner until a person approves it.
The item closes only on proof: the portal confirmation for a cure package, the signed extension for a lease. "I sent it" is not proof that the utility received the right file.
When proof appears, the goal moves, and GeniOS learns which consultant needs an earlier reminder and which utility always asks for the same exhibit. Next time the note comes sooner and the draft is closer to final. Approvals stay with people; see human in the loop versus human on the loop for how that works.
How it reaches you
Intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and in the web dashboard. On a normal day there are a few items, each with a project, a date and an owner.
You no longer chase engineers for updates, read every utility letter to judge whether it matters, or rebuild the tracker before a review. You no longer decide which of forty open items to look at first, so the pipeline meeting can spend its time on decisions.
A worked example
The company, names, dates and numbers in this example are made up to explain the idea.
A 40-person solar and storage developer in Austin has eight projects in development. Its largest, Cedar Flats, is 120 MW of solar with 60 MW of storage. The board deck sets the goal: notice to proceed on Cedar Flats by the end of the third quarter, which releases a $9.6 million payment from its financing partner.
On 3 March the utility emails a deficiency notice. The diagram shows the wrong inverter count, and site control covers only two of three parcels. The cure period ends on 17 March. On 4 March Ravi, the electrical consultant, writes in chat that a revised diagram will come Thursday. Thursday passes. The land sheet shows the parcel 2 lease ends on 30 April, and no extension letter was sent.
On 9 March Maria, head of project development, gets one piece of intelligence: Cedar Flats can lose its queue position in six business days, the diagram has not arrived, and the exhibit needs parcel 2. File the full package by Monday 16 March.
Maria delegates the diagram to Ravi, asks the land manager to send the extension letter, and gives the cover letter to a Reply Drafter. The landowner signs on 12 March. Maria changes one sentence and approves. The package is filed on 16 March at 10:40. GeniOS sees the portal confirmation, closes the item and moves the goal from 35% to 50%. Otherwise the first to notice would have been the utility.
How to measure it
Look at these monthly to see whether paperwork still makes projects slip.
- Days from letter to filed response. For utility and agency letters.
- Cure periods met with time to spare. The share of response windows closed at least two business days before the deadline.
- Promises closed with proof. The share of consultant and engineer promises that ended in a delivered file, not a chased one.
- Milestone slips caused by paperwork. Dates moved by an unanswered letter or a lapsed lease.
Where it applies
These are application areas where this use case can apply, not a list of current deployments. The same pattern fits solar, wind, storage and transmission developers, independent power producers and the capital projects teams inside utilities: anywhere permits, studies and land rights run in parallel.
- Domains: Operations, Legal & Compliance, Finance
- Industries: Energy & Utilities, Real Estate & Construction
- Roles: Executives, Managers
Questions about permit and grid connection tracking
Does GeniOS file anything with the utility on its own?
No. It drafts and suggests, and a person approves every submission, letter and email before it goes out. GeniOS starts read-only on the sources you choose.
We already have a permit tracker. Why add this?
A tracker shows the dates someone entered. GeniOS reads the letters, chats and documents where new dates and promises appear first. Your tracker stays; it just stops being the only safety net.
Can it read utility portals?
It reads what reaches your team: emails, notices, attachments, and the documents and tools you connect. Portal confirmations that arrive by email count as proof.
How does it know which project a letter belongs to?
It matches project names, queue numbers, parcels and people across sources, the way an experienced developer would. When it is unsure, it says so in the note instead of guessing.
Status
Exploring This is an application area we are exploring with early customers. Book a call and we will walk through it on your own permits and letters.