Quick Start

Account and processing availabilityCopy Anchor Link

When registration is enabled, create or join a workspace, complete email verification, and accept the current terms and privacy policy. Utility affiliation is reviewed separately. The public plugin binds your own sign-in to one workspace when its rollout is available.

Trial and prepaid workspaces use supported project packet intake and review within their processing allowances. Standalone legacy digitization, unrestricted assistant chat, and native DWG processing are unavailable for those workspaces.

Background updatesCopy Anchor Link

During the gated permission-aware rollout, brief interruptions and successful periodic refreshes stay quiet. The header distinguishes connecting, actual reconnect attempts, offline status, and unavailable updates. Retry updates does not reload the page or start a new processing job; expired sessions offer Sign in. Existing tabs need a refresh after activation. See the exact messages.

Choose Your PathCopy Anchor Link

• For External Users — Customers, partners, and coding agents connecting through the UI, CLI, API, or MCP
• For Developers — Validating interconnection applications before submission
• For Utilities — Integrating GridWonk into review workflows
• For Consultants — Managing workflows across multiple clients

Start with the external guide for API, CLI, MCP, or partner setup. GridWonk platform admins also see a protected internal-operator guide in their docs navigation. If you need workflow-specific product context, use the developer, utility, or consultant guides.

Console Workflow OverviewCopy Anchor Link

The GridWonk console supports both research and project work:

1. Select Utility and Program — Choose your utility from the dropdown in the header; a program chip or the skippable program step lands you on the interconnection program you care about, and the header then reads Utility › Program. Authorized synthetic test utilities are labeled Synthetic and name the canonical utility whose requirements they use.
2. View Documents — See the program’s reviewed source documents in order, each with its Role (what it covers), which programs it feeds, and how many published requirements cite it; All programs shows every document grouped by role.
3. Confirm Current Sources — Developer organizations see customer-usable active records; authorized reviewer organizations also receive historical review controls.
4. Review Published Requirements — Read the selected utility's versioned Packet Intake requirements, review status, and source links without creating a project.
5. Prepare Draft Files — Collect the supported files for your packet. Trial and prepaid workspaces upload through the project intake flow after project creation.
6. Create or Select a Project — Before validation, choose a project or create one with a project name, capacity, and distribution/transmission track. You do not enter a utility application number here. A synthetic selection is re-authorized on the server and routes only to its reciprocally paired test utility.
7. Review the packet where available — For supported utility, state, and program combinations, eligible projects automatically advance from document checks to packet review after their required evidence is ready. Use the compact Review Actions menu for a deliberate manual run or rerun and to open review history. The developer console defaults to the applicant self-check; utility teams screen from their utility organization context. Existing projects outside supported coverage explain that automated review is not yet available.

Research can stay projectless. Durable outputs such as validation results, deficiencies, scorecards, reports, and remediation status are project-scoped.

The Create Project utility picker requires a released, full packet setup for the chosen state and program. By default, a normal utility choice does not require a receiving organization for private review. Authorized synthetic choices use a validated test pairing backed by a released utility instead. A Research selection must also qualify before you can create a project. 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 if it fails. Utility Research keeps the full catalog; packet review coverage depends on the utility's supported state and interconnection program. Contact support for incomplete utility setup. Availability does not guarantee exhaustive coverage, utility approval, or permission to submit a packet; formal submission requires the utility's accepted intake lane and active reviewer.

Create Project can include optional documents. Valid selections collapse to a file count and removable list; use Add files to add more. Invalid additions leave accepted files in place. Create and upload starts upload on Documents only after the project exists. On a short screen, scroll the form; its title and action buttons remain visible.

Project capacity defaults to kW, with an explicit MW selector. Current document checks immediately populate findings and a partial report while the full packet review is outstanding. A partial report is neither utility approval nor proof that the packet is ready to submit. Existing site-plan cards offer Attach DWG; utility/process policy determines whether that companion is required.

Completed current document findings stay visible during running, failed or cancelled packet reviews, labeled as individual-document results. Authorized reviewers can use Review Actions → Cancel Packet Review without deleting those findings. Read any cancellation warning: a provider request already running may finish in the background. See Document troubleshooting before retrying a stuck review.

In a developer organization, the star on each Utility Selector row watches that utility for requirement changes. The project header does not carry a separate watch control because the subscription belongs to the utility, not the currently open project.

Inside a project, the Overview, Documents, Review, and Activity views switch the workspace. Those view controls and the back-to-projects control sit in the top header. The review work area carries a collapsible findings panel and a full-screen document mode, and opening Review temporarily collapses the sidebar to its icon rail — the automatic collapse is never saved as your preference; only your own toggle persists. Cmd+K (Ctrl+K on Windows/Linux) opens a command palette that jumps to any destination — including the Utility Research views — plus the project views and review tabs. It stays available while a Review toolbar disclosure such as readiness or the document switcher is open, and steps aside only for a full dialog.

The console does not spend permanent header space on healthy connections or successful periodic refreshes. Sustained interruptions show the connection or recovery message described above. Retry updates refreshes data when coverage is incomplete; it does not restart processing.

Research access starts in the developer-safe mode while GridWonk resolves the active organization, so a reviewer workspace does not briefly expose broader history before its permissions are known.

Developer Utility Research shows active distribution documents only; the status filter, level toggle and refresh control are reviewer tools. Deprecated and rejected sources never appear for developers.

Source-Backed OutputsCopy Anchor Link

Customer-facing answers and validation depend on source-backed material. A procedure document is the utility rulebook. A published Packet Intake requirement is the structured rule GridWonk serves from its controlled, versioned catalog.

Published requirement views return every technically published row except one with a current utility rejection. Each returned row is marked approved or pending, so unfinished review stays visible without being mistaken for approval. Packet evaluation uses its pinned published set rather than mixing in the frozen legacy table.

On a finding, Explain this finding shows exact quotations from the saved review's original source edition after checking your current access. It can show nearby source wording, but it does not guess which section governs the requirement or whether that wording applies to your equipment. Follow-ups retain the selected finding until you choose Clear finding; clearing starts a fresh conversational context, and changing user, organization, or project clears the selection. Missing or incomplete evidence produces an explicit limitation. This is not a new drawing inspection or a pass/fail decision. See the assistant guide.

Navigation BasicsCopy Anchor Link

• Left sidebar icons — Navigate between main views
• Project views — Inside a project, switch between Overview, Documents, Review, and Activity from the app header
• Help button — Open the help sheet from the left sidebar's Help & Support action
• AI Assistant — Chat button opens conversational help
• Reviewer URLs — Reviewer filters in /console are saved in the URL, so utility teams can share links to a specific utility, state, view, and cleanup filter

The global rail contains Projects, File Library, and Utility Research. Eligible developer organizations in the packet-review-checks cohort also receive Checks, a queue of projects with completed checks; open a project from the queue or use its previous/next controls to move through that queue. A selected project contains Overview, Documents, Review, and Activity. One shared toolbar stays above all four project views and shows the current developer action: Submit Project, Start Response, or Resubmit Project. It shows no action while the utility owns the next step. Returning to Review after changing document roles or confirmations refreshes its readiness row. Utility Research has its own shareable destinations: ?view=utility-research&research=documents and ?view=utility-research&research=requirements. Older ?tab= links still redirect to the matching current destination. The Analytics destination has been removed: ?view=analytics, the legacy ?tab=analytics links, and /console/queue-analytics all land on Projects. Interconnection queue retrieval has been retired across every surface.

When you change or clear the selected project, GridWonk also clears any packet-review selection so it cannot carry into a different project or projectless research. Leaving a project with the back-to-projects control clears the whole project address — the project, its packet run, the open document, and the project subview and Review tab — so a shared link never describes a project view with no project. Switching to another rail destination instead keeps that subview and tab, so returning to Projects restores the workspace you left. Re-opening a project always starts on Overview.

If a saved project link points to an archived project or one that is unavailable to the active organization, the console blocks all project subviews and provides Return to projects. An old link cannot open that project's Documents, Review, or Activity content. When the availability check itself fails — for example during a temporary connection problem — the console instead shows Couldn't load this project with Try again, because the project may still exist.

For a developer organization with a sent deficiency notice, the project-view toolbar shows Start Response. The action records the response-stage transition, unlocks the working set, and then changes to Resubmit Project; reviewer organizations do not see this developer-only control. If another teammate already started the response, refreshing shows the new stage without creating a duplicate history entry.

Keyboard ShortcutsCopy Anchor Link

• Cmd+B / Ctrl+B — Toggle sidebar expanded/collapsed
• Enter — Send message in chat
• Shift+Enter — New line in chat input

Find notificationsCopy Anchor Link

Use the notification bell in the shared header or the Console and Utility workspace header, including on mobile. When enabled, new client-access alerts appear there independently of email. Opening the inbox does not mark alerts read; use Mark read or Dismiss explicitly.