Documents
Document discovery, requirements, and management for interconnection procedures.
Customer processing availability
Trial and prepaid workspaces use supported project intake and reviews. Public procedure-document reads do not start customer processing. New uploads, text recognition, and review work require a current processing allowance; native DWG processing and legacy standalone digitization are unavailable in this rollout. Reading an authorized existing result does not spend a review credit.
Background updates
The gated permission-aware rollout keeps displayed documents during temporary refresh failures. Confirmed removal or lost access clears them. Periodic refresh coverage also includes procedure document changes that do not emit an organization job event. Successful refreshes stay quiet; failures still show recovery actions. Retry updates refreshes data, not discovery or processing work. See live-update status.
Salesforce evidence
The Salesforce connector is still disabled pending pilot acceptance. Its source-managed packet files are separate from discovered procedure documents. Reading a captured file, CAD preview, text, or report requires an approved linked reviewer with current Salesforce source access; ordinary role changes and file edits are refused. See Salesforce preparation.
Current access checks cover fields from all captured revisions, including fields no longer mapped. Losing access to an older field can therefore also block a current file or report. Ask the connection administrator to resolve the source permission; do not substitute an ordinary download.
What is Document Discovery?
Packet-review cancellation belongs to the project's Review Actions and does not delete completed document findings. It is separate from procedure discovery and its controls below. See Jobs for cancellation warnings and limits.
GridWonk automatically discovers interconnection procedure documents from utility websites. This includes:
- Tariffs
- Guidelines
- Technical specifications
These documents define the requirements for your project's grid connection approval.
Procedure documents are the rulebooks GridWonk reads before it extracts requirements. Uploaded applicant files are different: they are the evidence you provide to show that your project meets those rules. Optional upload conveniences such as Combined-PDF split and packet ZIP upload are per-organization features, on by default, that your organization admin manages from the workspace Features page (see Upload).
From utility source to cited finding
From utility source to cited finding
Discovery only indexes a candidate source. Customer-facing validation begins after a reviewer approves a readable current procedure document, then keeps the requirement and applicant evidence traceable.
Index a utility-published document
Discovery records a candidate procedure source. Indexed does not mean human-reviewed or ready for customer use.
Approve a current readable rulebook
A reviewer confirms the document is the right current source and GridWonk has readable extracted text.
Publish a Packet Intake requirement
GridWonk stores the structured requirement in the versioned Packet Intake catalog with source provenance.
Compare applicant evidence
The project document is evaluated against the requirement without replacing the utility source text.
Return a cited result
A finding keeps the rule and applicant evidence connected so a reviewer can defend or correct it.
Source anchors: lib/interconnection/procedure-documents/current.ts, lib/interconnection/site-control-requirements/usable.ts, domains/requirements/presentation/published-requirements.server.ts
Document Roles and Sources
GridWonk uses Role for what a procedure document covers. This avoids the ambiguity of “document type,” which can mean its file format, author, legal authority, or purpose.
Examples include Interconnection Procedures, Application Form, Technical Requirements, Site Control, Rates and Fees, and Interconnection Agreement. The console turns the internal content_role value into the readable group heading above the cards, so users do not need to learn it.
Source is separate. It identifies who published or owns the material, such as the selected utility, a state commission, an RTO/ISO, or a federal entity. Keeping Role and Source separate makes questions easier to answer:
- “What does this document cover?” → Role
- “Who issued this document?” → Source
An unclassified role means GridWonk has not assigned a reliable role yet. It does not mean the document is invalid.
When synchronization discovers a reliable title for a previously untitled document, GridWonk can fill that missing title without replacing a title that a reviewer has already accepted.
Applicant Project Documents
Inside a developer project, document selectors lead with the assigned packet role, such as Single-Line Diagram or Site Plan. A short filename is added only when two files share the same role. Uploaded documents show processing, failure, or another actionable state; a redundant success badge is not shown after processing completes.
A site-plan PDF can carry an immutable native AutoCAD DWG companion. The PDF remains the packet document, while the DWG supplies the original drawing structure for layouts, layers, entity properties, measurement, and utility-specific checks. Replacing the DWG creates a new site-plan version so reviewers can compare revisions without changing the earlier evidence.
Saved project and curated demo links are resolved inside the active organization. GridWonk refuses the link when the project is missing, duplicated, belongs to another organization, or the active user is not authorized; it does not switch organization context automatically.
Review Status Explained
GridWonk labels procedure documents by whether they are ready to support customer-facing answers and validation.
| Status | What it means | What customers see |
|---|---|---|
| Current usable | A reviewer approved the document and GridWonk finished reading the document text. | Can be used for requirements, validation, and customer-facing outputs. |
| Pending review | GridWonk found the document, but a reviewer has not approved it yet, or reading the text is not complete. | Hidden from customer-facing outputs after current-procedure enforcement is on. |
| Deprecated | Kept for history because it may be old, replaced, or no longer authoritative. | Not used for new customer-facing answers or validation. |
| Rejected | A reviewer decided the file is not the right source. | Not used for customer-facing outputs. |
Current-procedure enforcement means GridWonk only uses approved, readable rulebooks for customer-visible work. This can make a utility look temporarily sparse while review cleanup is in progress, but it prevents old or unapproved rulebooks from driving deficiency results.
Starting the Discovery Process
Starting discovery is a mutation available in utility and GridWonk organization contexts. Developer and consultant users can browse Utility Research as read-only reference material but do not receive discovery or extraction controls there.
For an authorized utility or GridWonk user:
- Select your utility with the picker in Utility Research
- Click Start Discovery to scan the utility's website
- Follow the job status while scanning runs
- Review discovered documents
Extracting Requirements
Extraction is also limited to utility and GridWonk organization contexts. After discovery completes, an authorized user can choose:
- Extract All — Process all documents in the current eligible set
- Extract Selected — Process only specific eligible documents you choose
Extraction pulls structured requirements from the documents for validation against your submissions.
When a reviewer status filter is active, extraction uses the filtered document set. Extraction is limited to Current usable documents so new requirements come from approved source material.
Reliable Background Processing
Discovery and applicant-document review run as durable background jobs. If the workflow platform retries a step after losing an acknowledgement, GridWonk reuses the job's stored terminal result instead of changing a completed job to failed or running the review again. Completion and failure notifications also use stable event identities so a safe replay does not create a contradictory result.
Transmission and Distribution Filtering
Utility and GridWonk reviewers use the transmission/distribution toggle in the Procedure Docs header to narrow discovered procedure documents (developer research is pinned to distribution):
- Both shows all discovered procedure documents.
- Transmission shows transmission-applicable documents and uncategorized documents.
- Distribution shows distribution-applicable documents and uncategorized documents.
Procedure Docs shows the filtered count when a specific interconnection level is active.
Reviewer Filters and Shareable Links
Utility reviewers and GridWonk admins may see a document status filter in /console. The temporary filter options are:
- Current usable
- Pending review
- Deprecated
- All reviewable
These filters are URL-backed, which means the address bar carries the review state. A reviewer link
can include view=utility-research&research=documents&procedureStatus=all_reviewable so another
reviewer opens the same utility, state, destination, and filter. Older tab=documents links still
redirect to that destination and keep the filter, and the Cmd+K palette jumps straight to the
Procedure Docs or Requirements destination from anywhere in the console.
Developer Utility Research shows active distribution documents only and has no status filter; deprecated and rejected documents never appear for developers. Reviewer and admin surfaces retain the Current usable, Pending review, Deprecated and All reviewable filters, and the console lists distribution documents for every audience.
Understanding Document Cards
GridWonk does not show unreviewed discovery-script notes on document cards. Any future document summary should be source-backed and reviewed before customer display.
Every console audience sees the same slim card built for assembling an application packet; the group heading names the role:
- Title and Region/State
- Feeds — The published programs (for example Simplified, Expedited, Standard) whose reviewed source set includes the document; each chip opens the Requirements tab on that program
- Cited by — How many published requirements cite the document, or "Not yet cited by published requirements"
- View — Opens the stored copy GridWonk indexed for this record in a new tab, with its file type, or says the stored copy is unavailable
- Original source — Where GridWonk got the document: the utility's own link, kept for provenance; for monitored utilities a warning appears only when the public version may have changed since capture
Utility and GridWonk reviewers see the same card. Their only extra control is the review-status filter above the list; cards do not show a review-status chip.
Review status, source owner, level and discovery date are not shown on console cards.
Programs and the Packet Map
The console header shows the lineage Utility › Program. The utility segment is the picker; the program segment lists the utility's published programs plus All programs. With a program selected, Procedure Docs shows the packet map: the program's reviewed source set, numbered in the order the packet is usually assembled, each document with its role label and how many published requirements cite it, and the utility's other documents in a collapsed section. With All programs, every document is grouped by role in packet order. The Requirements tab follows the same program. Every audience sees distribution documents only, with no level toggle or refresh button; reviewers keep the status filter. While a remembered program's data is still loading, the list shows a placeholder instead of flashing the grouped cards first.
Older captured procedure documents keep their original record identifiers. The stored-copy link and review workspace can read those records without replacing the captured file or resetting its review history. A preview error alone does not mean the stored copy is unavailable.
Asking the Assistant About Documents
Useful document questions include:
- "What procedure documents has GridWonk found for Duke Energy NC?"
- "Have requirements been extracted from these documents?"
- "Which documents have I uploaded for this utility?"