For Developers

Project creation defaults capacity to kW with an explicit MW option. Overview, Documents, Findings, and Report share current results: completed document checks provide a partial report immediately, while a current completed packet review replaces overlapping results. This is not utility approval or submission eligibility. Site-plan cards offer Attach DWG; the published utility/process policy determines whether it is required.

If cards or Overview show Findings unavailable, refresh before relying on their counts. A background read failure is not a clean review and cannot silently replace current applicant results with an older utility report.

Background updatesCopy Anchor Link

The permission-aware live-update rollout is gated. Once enabled, organization-wide access uses one private channel, while project-scoped access receives only permitted project topics. Document and project readers also refresh periodically. Temporary failures retain displayed information; confirmed loss of access clears it. Retry updates refreshes data without restarting processing. See live-update status.

Salesforce pilot boundaryCopy Anchor Link

The implemented Salesforce utility connector is disabled and does not replace a developer's submission channel. Its captured utility-internal results do not become available through applicant access, and source-managed evidence cannot be edited through ordinary project controls.

Who Is This For?Copy Anchor Link

Project developers preparing interconnection applications for submission to utilities. For supported document and application roles, GridWonk reviews the submission against source-backed utility requirements so teams can identify and correct gaps before utility review.

You can select optional files in Create Project. The compact drop area closes after selection; Add files reopens it, and removal controls stay beside the filenames. Choose up to 12 PDF, PNG, JPEG, or DWG files (30 MB each, 120 MB total), or one ZIP alone. Invalid additions leave accepted files in place. Upload starts after the project is created, with permissions and ZIP availability checked in Documents. Capacity means the AC (alternating current) nameplate rating; Capacity help expands the unit definitions.

What You GetCopy Anchor Link

• Deficiency detection — For supported utilities, Packet Review checks accepted document roles and evidence from the current documents against the effective-analysis requirement tier and flags gaps
• Compliance scorecards — Pass/fail status for each requirement category (site control, technical specs, insurance, fees)
• Role-specific checks — Deterministic evaluators check supported application fields, evidence, and cross-document rules
• Requirement provenance — Each finding card shows the requirement, source document, page, and cited text. Explain this finding explains that saved finding using its original requirement and source evidence after checking your access. It distinguishes utility text from common practice; publication alone is not human approval. The older remediation route remains transitional and its revalidation action still uses the legacy compliance pipeline
• Developer-first packet check — Work from a named project, review the exact current packet, correct detected deficiencies, and rerun before using the utility's required submission channel
• Source-backed utility research — Read active procedure documents with a plain-language Role (what the document covers) and Source (who issued it)

When you ask about a finding, the assistant keeps it selected for follow-up questions and retries. Use Clear finding to change topics, or choose another finding. Changing user, organization, or project clears that selection. If the exact saved source cannot be verified, the assistant states the limitation instead of guessing or substituting today's requirements. It explains the rule and its applicability; it does not re-read your drawing or decide whether your application passes.

Getting StartedCopy Anchor Link

1. Create or join a developer workspace — Verify your email and complete onboarding, or accept your team invitation. If registration is unavailable, use the access contact shown in the app.
2. Navigate to the Interconnection Console — Select your target utility from the dropdown. Authorized synthetic test utilities carry a Synthetic badge and identify their canonical requirements source.
3. Research requirements — Browse procedure documents and customer-released requirements without creating a project
4. Upload draft files when useful — Drag and drop documents for digitization while you are still organizing the application
5. Create or select a project when you are ready to validate — Enter a project name, capacity, and distribution/transmission track. If the utility publishes more than one interconnection program for that track, a Program dropdown appears and a choice is required — the review then runs against that program's rules. GridWonk handles the internal reference; you do not need a utility application number. For a synthetic selection, GridWonk keeps research on the canonical utility and re-checks the active applicant's reciprocal pairing before routing the test project.
6. Review the packet where available — Attach working files and confirm their document roles. For supported utility, state, and program combinations, the developer console automatically starts the applicant packet check once required evidence is ready; utility screening is performed from the utility organization context. Use Review Actions for a deliberate manual run or rerun. Existing projects outside supported coverage explain that automated review is not yet available. Customer-release approval of the reference requirements is a separate state and does not itself block Packet Review.
7. Correct and rerun — Fix cited issues, replace affected files, and let the automatic checks advance again, or use Review Actions → Run Review Again when a deliberate rerun is needed. Returning to Review after changing roles or confirmations refreshes its readiness row.
8. Prepare the GridWonk package — A completed review is decision support, not utility approval or proof of delivery
9. Submit only when ready — If the utility accepts packets in GridWonk, Submit Project explicitly shares a frozen package and its pinned packet report. Private review remains available before submission. Otherwise use the utility's required external portal, email, or other channel
10. Prepare a revised package when needed — If the utility sends a notice, select Start Response in the shared toolbar above any project view, replace the affected files, run another applicant self-check, and select Resubmit Project when the revision is ready. The new immutable package returns to Pending; the receiving utility starts its review with Screen Selected or an authorized integration. The application then shows Screening before work starts and Screened when complete. A failed start or run restores the prior status once no other utility review is active; your applicant self-check cannot perform this utility transition

If a packet review appears stuck, use Review Actions → Cancel Packet Review when your review permissions allow it. Completed current document findings stay available and remain separate from whole-project results. A provider request already running may finish in the background; the interface warns if its workflow stop cannot be confirmed. Follow Document troubleshooting before retrying rather than repeatedly starting another run.

The Create Project utility picker requires a released, full packet setup for the selected state and program. A normal utility choice defaults to private review without a receiving organization or a rollout environment variable. Authorized synthetic choices use a separately validated test pairing backed by a released utility. A utility inherited from Research must qualify too. The support check starts as soon as the dialog opens; choose another utility if yours is unsupported, or use Retry to run the check again when it could not be completed. Research keeps the full utility catalog; being listed there does not prove review support for a utility, state, or interconnection program. Contact support when utility setup is incomplete. An available choice does not guarantee exhaustive requirement coverage or utility approval. GridWonk submission remains unavailable until the utility accepts that state and program and has an active reviewer; private review does not send the packet. That check applies to the first Submit only: Resubmit Project after a deficiency notice is never blocked by it. See Private Reviews and Utility Submissions.

If one accepted PDF contains several document types, choose Documents → More actions → Split PDF. Eligible PDFs have 2–250 pages, and can already have a type or completed review. Check the previews, confirm complete non-overlapping ranges, and assign each resulting document a type. Only confirmation starts a split. On success, the original and its reviews remain historical while the new documents go through processing and review. Reopen the action for progress; after failure choose Retry split or Keep original. New reviews and submission stay paused until resolved. Existing organization feature controls and editable-project permissions apply; no new setting or re-upload is required.

Use the project's Upload Project Files control for one loose selection of PDFs, PNGs, JPEGs, and AutoCAD DWGs, or for one ZIP containing 1–12 supported files. A matching site-plan PDF and DWG can be selected together; GridWonk pairs them automatically only when the match is unambiguous and asks you to choose the site plan otherwise. GridWonk validates an entire ZIP before any file enters its normal document or CAD processor, so one unsafe entry rejects the whole ZIP. The ZIP never becomes a packet document. Do not select a ZIP together with loose files.

Finish or cancel unfinished uploads before submitting or resubmitting a project. An active, unexpired batch blocks package creation while its files are uploading, processing, or awaiting pairing. The refusal preserves your current documents and any earlier submitted packages.

The console offers a Cmd+K / Ctrl+K command palette for jumping between destinations; it stays available while a Review toolbar disclosure is open and steps aside only for a full dialog. Eligible developer organizations in the packet-review-checks cohort also receive Checks, which lists projects with completed checks; select a project there, use [ and ] to move through the queue, or choose Open project for its full workspace. The project views (Overview · Documents · Review · Activity) and the back-to-projects control sit in the top header, the review work area carries a collapsible findings panel plus a full-screen document mode, and opening Review temporarily collapses the sidebar (the automatic collapse is never saved as a preference; a manual toggle wins and persists). Leaving a project with the back-to-projects control clears the entire project address, including the project subview and the Review tab, so a copied link never points at a project view with no project; re-opening a project starts on Overview. Utility Research keeps the same developer-safe document and requirement visibility rules. The console also reports anonymized performance measurements (page speed and navigation timing) so slow screens can be found and fixed; project and document identifiers are stripped before anything leaves the browser.

The console stays quiet while background updates are healthy, including successful periodic refreshes. After eight seconds, the header distinguishes Connecting live updates… from Live updates interrupted — reconnecting…. Some live updates are unavailable. offers Retry updates for incomplete refresh coverage. Offline and expired-session warnings remain visible; see live-update status.

Saved links remain subject to the active organization and current project visibility. If a project has been archived or is no longer available, GridWonk shows Project unavailable and Return to projects instead of mounting its Overview, Documents, Review, or Activity content. A failed availability check — for example a temporary connection problem — shows Couldn't load this project with Try again instead, so a transient error is never presented as a removed project.

Research access starts with the developer-safe view while GridWonk resolves your active organization. Developer organizations remain limited to active customer-usable records; authorized reviewer organizations then receive their historical review controls.

Developer Utility Research does not show deprecated or rejected procedure documents. Use the Role description to understand a document's purpose and the separate Source label to confirm who issued it.

How Developer Visibility WorksCopy Anchor Link

GridWonk keeps the developer's applicant self-check separate from a utility-authority review. When a verified utility workflow record exists, your organization can see its own submission lifecycle because GridWonk links the applicant organization to the shared submission record. In plain English:

• the utility owns the review row
• your developer org is linked as the applicant on that same row
• notices and resubmission history stay shared without making you the owner of the utility queue itself

Workflow CapabilitiesCopy Anchor Link

A queued or held utility notice is not yet a sent notice. Conflicting response or submission changes wait for delivery resolution and the application's final notice-sent update; contact the utility if progress remains held. Earlier immutable packages remain unchanged.

GridWonk combines one active assistant persona with purpose-built workflows and deterministic pipeline stages. A pipeline stage can run as part of screening without being a separate agent that users configure or call directly. When a project document is selected, GridWonk resolves the current logical version row for sanitized PDF viewing. That keeps Results and packet review tied to the current safe rendition instead of a caller-controlled raw file path.

What Requirements You See, And Their Review StatusCopy Anchor Link

The requirements you can browse are every published requirement for the utility except the ones a utility reviewer has explicitly rejected. Rejected requirements are removed on the server and never reach you.

Each requirement you see carries its own review status: approved means the utility's reviewers signed off on it; pending means it is still awaiting a current utility decision — including a requirement whose logic changed after a decision, which returns to pending re-review rather than disappearing. Nothing is hidden merely because a utility's review is unfinished; the surface reports that review progress separately (review_incomplete, partially_released) while still listing the requirements.

This is deliberate: a Packet Review deficiency report cites requirements from the same all-except-rejected set, so the list shows you what a report can raise, with pending items labelled honestly.

Packet Review uses the separate effective-analysis tier. Where Packet Review is supported and your project resolves to a real utility organization, an unfinished utility review does not by itself block a deficiency review. Serving requirements does not depend on a contract or subscription flag, although account access and normal project authorization still apply.

The effective-analysis tier also applies current-source safeguards. When current-procedure enforcement is enabled, analysis uses requirements that are:

• Validated by a reviewer
• Linked to a current usable procedure document
• Still tied to the same document text GridWonk read during extraction, when that check is available

If a utility is still under cleanup, you may see fewer analysis requirements or a message that no approved site-control requirements are available yet. That means GridWonk has not confirmed enough source-backed rules for that analysis mode. It does not mean the utility has no requirements.

Using the APICopy Anchor Link

For programmatic access, see the API Reference. The streaming agent API accepts JSON requests and returns Server-Sent Events (SSE) for real-time results.

Next StepsCopy Anchor Link

For an interrupted upload, a corrected PDF, a failed review or a combined drawing set, use Document troubleshooting. It explains when to Retry upload, Replace, Retry review or Split, and why completed document results are separate from a whole-project review and utility approval.

• Quick Start — Console workflow overview and keyboard shortcuts
• Help Center — Detailed feature documentation
• Applications — Submission stage vs review workflow status
• Notices — What happens after a utility sends a deficiency notice
• For Utilities — How utilities use GridWonk (useful context for developers)

Client-access notificationsCopy Anchor Link

The Console header includes a notification bell on desktop and mobile. If you also belong to a consulting organization, enabled new-grant alerts remain visible while another organization is selected. The alert's View client access link opens Consultant Access without switching your organization. See Access Grants.