Upload

Trial and prepaid intakeCopy Anchor Link

You must have an approved, current session to start or change an upload. If GridWonk asks you to accept updated legal terms, complete that step in the browser before retrying the action.

For trial and prepaid workspaces, supported uploads require a current processing allowance before an upload authorization or background processing starts. The trial source allowance includes the ZIP container and each expanded source entry; resuming that same entry does not count it twice. Native DWG processing is unavailable in this rollout, including DWG entries inside archives. A format listed for an existing integration does not override this workspace restriction. See processing allowances and recovery.

If your workspace is limited to PDF review, use standalone PDFs. The server refuses images, ZIP archives, and native CAD files in that scope, including saved File Library attachments and existing packet sources. Reusing an earlier upload or changing clients does not override the restriction. A PDF-only review does not waive the utility's required evidence.

Salesforce-managed packetsCopy Anchor Link

The Salesforce connector remains disabled pending acceptance. For a packet marked as Salesforce-managed, ordinary upload, replacement, deletion, role changes, working-copy edits, and manual reprocessing are refused. Change the source in Salesforce and request a new connector capture after activation; a utility administrator role does not bypass this boundary. Existing file formats, limits, and ordinary packet uploads are unchanged.

The separate outbound-only installed application is also disabled. Its Layer 2 work adds exact Salesforce file checks inside the shared intake code, not a new upload button or permission to open Salesforce content from the File Library. Uploading files does not bypass its separate processing gate. The ordinary upload workflow on this page is unchanged.

Select Files While Creating a ProjectCopy Anchor Link

Create Project accepts optional files before the project exists. Its compact drop area closes after selection; Add files reopens it while filenames and removal controls remain visible. Choose up to 12 PDF, PNG, JPEG, or DWG files (30 MB each, 120 MB total), or one ZIP alone. Empty, unsupported, oversized, or incompatible additions show an error without discarding accepted files. Upload starts after creation; Documents still checks permissions, ZIP availability, and file content.

A refused application formCopy Anchor Link

A failed form review may explain that the PDF appears to be the wrong form, a different revision, or could not be verified for the selected program. Read its reason and observed differences in Documents, then upload the correct form before retrying. The explanation belongs to the current failed review and clears after a successful retry or replacement; it does not mean the file transfer failed.

Supported File FormatCopy Anchor Link

The selected project's Upload Project Files control supports PDF, PNG, JPEG, and DWG files up to 30 MB each, or one ZIP up to 30 MB, subject to the workspace's current server restrictions. Word documents are not supported. It is the console's only upload lane: the older single-PDF uploader with its 3 MB limit was retired on 2026-09-30, and an organization whose secure intake is not enabled sees that upload is unavailable rather than a fallback.

Native CAD companion uploadCopy Anchor Link

For an existing site plan, choose Attach DWG directly on its card. The chosen version is fixed before upload and validated by the server; a concurrent PDF replacement cannot silently retarget the upload. The same card offers Replace DWG and shows required/optional, failed, processing, attached, or outdated states. A replacement PDF needs its companion reconfirmed or replaced. Where the workspace permits native CAD, DWG uploads are available for every utility by default, even when its checklist does not require CAD. An administrator can disable native CAD intake for an organization. The selected published utility/process policy separately determines whether CAD is mandatory: NSP's current policies keep it optional, while NES retains its requirement for systems at or above 50 kW. A utility does not need a CAD review profile to accept an upload. Only DWG is supported for native CAD intake; DXF is not currently accepted.

In a project's Documents view, use Upload Project Files for PDFs, images, and AutoCAD DWGs. You can drag the site-plan PDF and matching .dwg together. Each file may be up to 30 MB. GridWonk prepares the PDF and privately inspects the DWG, then attaches the drawing only when one current Site plan match is proven. Matching basenames may pair automatically; ambiguous drawings show Choose the Matching Site Plan and never guess.

When the PDF and DWG arrive together, GridWonk waits for the PDF to finish becoming the current site-plan version before it pairs the drawing. It does not attach the DWG to an older site-plan version just because that version was current when the upload began. A retryable processing failure keeps the same private upload available for retry, and a bounded background recovery pass resumes safe queued or waiting pairings without creating a second copy.

The PDF remains the packet document. Its DWG is an immutable native companion that supplies layouts, layers, entity properties, measurement, and extracted review evidence. Replacing it creates a new logical site-plan version. The original stays private. Intake and visualization are utility-neutral; utility-specific checks require that utility's reviewed procedure profile.

The Digitization ProcessCopy Anchor Link

After upload, AI extracts text from your PDF:

1. Upload — Select and upload your PDF file
2. Processing — AI extracts text content
3. Classification — AI detects document type automatically
4. Ready — Document available for compliance validation

Each processing run is tied to the exact stored file generation. If a newer generation replaces the run's input through an internal or future versioned workflow, stale digitization, classification, and text-location results are discarded instead of being attached to the newer file.

Project ContextCopy Anchor Link

You can upload and digitize files before creating a project. Those files are shown as Draft files.

Draft files are useful for research and cleanup, but validation results must belong to a project. To validate a draft file:

1. Click Create project to validate
2. Enter a Project name, capacity, and distribution/transmission track
3. Attach the draft file to the project
4. Run validation in that project

If you upload while a project is already selected, the file is linked to that project automatically and can auto-validate when the document type is ready.

The console does not ask you to enter a utility application number. GridWonk creates an internal placeholder behind the scenes and can later map or replace it when the utility system assigns an official number.

Manage Project DocumentsCopy Anchor Link

Current finding counts are visible without opening More. Select a count to read its findings. Processing completion is not a clean review: unreviewed, failed, and stale checks remain explicit.

Findings and CAD status refresh after document changes, accepted uploads, or review changes. Unchanged background responses do not reload them. A failed findings refresh remains visible instead of being treated as a clean result. These counts use the same current source as Overview, Findings, and the partial Report view.

With permission-aware live updates enabled, temporary connection failures retain the displayed documents while authorized background reads recover. A connection warning is not an upload failure. Successful scheduled refreshes stay quiet; they do not imply measured delivery delay or proof that processing finished. If updates remain unavailable, use the offered refresh/retry action; if your session expires, use Sign in. See progress-update troubleshooting. This behavior remains gated until rollout; tabs opened before the upgrade need a refresh.

The full uploader stays visible while a project has no documents. After the first document exists, use Add documents in the Documents header to expand it when needed, or Attach from library to reuse an eligible file. Active storage-native uploads and upload errors remain visible until they are resolved.

Each compact or expanded document row labels Upload, Text recognition, and Document review separately. Upload completion means the file was received, not that text recognition or review passed. The review progress bar describes only the individual review. On a phone, Preview and More remain beside the filename while the full-width role selector uses a deliberate second row. Open More for Review or Retry, Findings, Replace, and Delete. Delete still requires confirmation. Open a role suggestion to read its rationale and confirm it; abstentions and possible combined-document warnings remain visible without expanding every row. The required-role checklist starts as an N of M assigned summary and expands on demand.

Read the three processing statesCopy Anchor Link

An intake card can say Document review: Check document because that card does not read the review record. Check the settled document row for its result. Text recognition may fail while a document review is complete; preserve and read the review findings instead of assuming all work failed. A complete document review is not a clean result, a full-packet review, or utility approval.

Applicant-document safety statesCopy Anchor Link

1. Working copy

   New upload

   GridWonk stores the source PDF, starts digitization, and links it to the selected project when one is active.

2. Safe reuse

   Byte-identical upload

   The existing document may be reused and missing references restored without creating a false revision.

3. New version

   Replace a working document

   Use More → Replace in an editable project to upload a corrected PDF as a new logical version. Earlier review results and submitted-package versions remain historical evidence.

4. Restricted

   Linked project document

   A document identity already linked to one project cannot also be attached to a second project.

5. Immutable history

   Submitted-package document

   Once pinned into a submitted or resubmitted package, that exact document version cannot be replaced or removed.

Source anchors: app/actions/applicant-documents.ts, lib/documents/intake/acceptance.ts, domains/applicant-packets/mutations/packet-mutation-lock.ts

Document ClassificationCopy Anchor Link

AI automatically detects your document type with a confidence score. The manual selector currently focuses on site-control evidence types used by validation.

Site-control validation focuses on evidence such as deeds, leases, options, easements, rights of way, development rights, exclusivity agreements, and shared site agreements. Application forms and permits may be uploaded and digitized, but they do not automatically satisfy site-control evidence requirements unless the extracted utility requirement allows that evidence.

Review and confirm the classification to ensure accurate validation. You can override the AI classification if needed.

Packet content rolesCopy Anchor Link

For supported interconnection packets, GridWonk classifies the content role from the safe viewing copy while text extraction runs separately. A positive result for application form, single-line diagram, site plan, equipment specification, or site control is accepted automatically when the project is in the enabled rollout. Unknown, not-evaluated, possible-combined, and supporting-role results still require a person.

Check the assigned role and reason in project Documents. If the role is wrong, select the correct role and choose Correct. The human correction becomes authoritative, the automatic assignment stays in audit history, and the analysis applicable to the corrected role runs again. Once document processing is ready, an accepted reviewable role can start its individual review automatically and can also make the full packet eligible for automatic review. Review and Retry review remain manual recovery actions.

Combined PDFsCopy Anchor Link

In project Documents, choose More actions → Split PDF for an eligible, accepted PDF with 2–250 pages. This works after assigning a document type or completing a review, even if automatic classification did not flag the combined content. Possible combined document is an additional shortcut, not a requirement. Existing uploads do not need to be uploaded again.

1. Select More actions → Split PDF from the project or packet document list.
2. Check the safe page thumbnails and the suggested ranges.
3. Make every range continuous and non-overlapping so every page is included exactly once.
4. Assign a packet role to each document range, or explicitly discard separator/blank pages.
5. Select Confirm and create documents. Opening, analyzing, or canceling the dialog does not change the document. The original remains available; only a successful split makes its existing review historical. Each resulting document enters processing and requires its own review.

Suggestions are drafts, not decisions. If analysis fails, use Try again or enter page ranges manually when page previews are available. Confirmed work continues in the background; reopen Split PDF to see progress. A failed attempt offers Retry split or Keep original. New reviews and submission remain paused until the split succeeds or you keep the original. Keeping the original preserves its document type and review history.

Splitting is enabled by default for applicant organizations; administrators can restrict it through the existing feature controls. There is no new developer setting or public API. Unsupported files, imported/source-managed documents, and read-only packets are not eligible. Pages are split as whole pages; content within a page is not cropped.

Packet ZIP uploadsCopy Anchor Link

Choose one ZIP in Upload Project Files to use it as a temporary container. GridWonk validates the whole archive first, then sends each accepted PDF, PNG, JPEG, or DWG through its ordinary processor. The ZIP itself never becomes a packet document or enters review.

• Keep the compressed ZIP at or below 30 MB and include 1–12 files.
• Use only PDF, PNG, JPEG, or DWG entries. Nested or encrypted ZIP files and unsafe paths are rejected.
• If any entry fails validation, no entry is handed to Packet Intake.
• The control appears only when the storage-native upload experience and the ZIP upload feature are both enabled for the applicant organization (server-side, per-organization settings), and only while the project is in an editable stage.
• Upload the ZIP by itself; a selection that mixes a ZIP with loose files is rejected with guidance.

ZIP upload is a convenience, not a different review path. After successful handoff, each document follows the normal preparation and review rules, while each DWG follows safe site-plan pairing, immutable attachment, visualization, and evidence extraction.

GridWonk waits for the whole upload batch to settle before reserving a whole-packet review. A CAD item settles when its immutable site-plan attachment is complete; Autodesk evidence may arrive later and can trigger a new review against the updated packet fingerprint. Cancelling or failing one optional item does not turn it into packet evidence—the ordinary readiness rules decide whether the remaining documents can be reviewed.

This also applies when you start a packet review manually: finish or cancel the unfinished uploads, abandon their batch, or wait for it to expire before retrying. Accepted documents stay attached. Individual document reviews can still run while the rest of the batch is unfinished.

If a retry resumes an item after its coordinating batch expired, the expired batch remains truthful history while the file's own status continues to completion. The Documents list keeps polling that file directly, so a temporary batch-status failure cannot hide a successful retry.

The same safety rule works in reverse. If a whole-packet review is already reserved or running, GridWonk asks you to retry the new upload after that review finishes instead of reviewing a packet while its files are changing. A recoverable review-start failure does not block uploads while idle; if GridWonk retries it, the retry first claims the same submission lock and becomes queued before a new batch can be accepted.

Document Status StatesCopy Anchor Link

Site-control documents review alongside the application form, single-line diagram, site plan, and equipment spec sheets. When all present typed documents have current extraction evidence and the packet's required documents are ready, automatic full-packet review can start.

The Documents view states whether the full packet review has not run, is in progress, last completed, or failed. Open Review to see the result, findings, or retry action.

Retry and Delete OptionsCopy Anchor Link

If you refresh after a secure upload has started, return to the same project's Documents in the same browser tab and account. Reselect original files to resume checks the original files before continuing the same upload. Already accepted files are not uploaded again, and an Attach DWG upload keeps its original site-plan version. Files selected before a project exists are still temporary; no upload has been reserved for them yet.

Recovery remembers identifiers and file fingerprints, not document contents or upload credentials. If recovery cannot be verified, use Retry Recovery. Dismiss Local Record removes only the browser's recovery record: it does not cancel server processing or release an unfinished upload gate. Use the file's cancellation control to stop an eligible unfinished upload.

An empty, unsupported, or unreadable new file shows a normal upload error, not recovery controls. Correct the selection and choose the file again. Retry Recovery remains available when the account or saved upload cannot be verified, even if no recovery record could be loaded.

• If the transfer is interrupted or its authorization expires: Follow the upload card's message and use Retry when offered. An eligible retry keeps the upload's identity but starts a fresh transfer from byte zero. A service rejection does not mean the PDF is invalid; contact support if the message asks you to. If finishing reports that the upload changed, another retry replaced it: the card refreshes and keeps Retry available when the file still needs bytes.
• If preparation fails after upload: Use the processing Retry offered for that accepted file. This reuses the stored source rather than uploading it again; only eligible internal failures can be retried, within the recovery limit. If the file changed before the retry started, refresh the page and retry the current version.
• If document review fails: Use the document's review recovery action. Upload recovery does not rerun a completed review.
• To remove an unpinned document: While the packet is a draft or resubmission under development, click Delete
• Submitted-package safety: A document frozen into a submitted or resubmitted package cannot be changed or removed

Refresh after an uncertain result. The server may have received the bytes even when the browser reported a transfer failure; verified completion wins. An expired or abandoned upload selection stays closed, but each unfinished file keeps its own Retry, and quota checks still apply. Keep accepted documents and follow the current on-screen recovery guidance instead of repeatedly creating replacement uploads.

If an accepted file's text recognition or review remains failed, contact support with the project, filename and affected outcome. Support may be able to recover processing from the stored file after a scoped check; this is not a customer OCR-retry control. Do not rerun a completed review merely because OCR failed. If the original upload was never accepted, processing recovery cannot recreate its bytes. See Document troubleshooting before uploading another copy or replacing a document.

Tell support if the document or project review inputs change while recovery is being prepared, including a change to the project's state. Support must check the current inputs and obtain a new approval before proceeding; the earlier approval does not authorize recovery of changed inputs.

GridWonk does not currently promise automatic 30-day cleanup for applicant documents. Keep documents until you no longer need the working copy, subject to submitted-package retention and your organization's records policy.

Document Type ConfirmationCopy Anchor Link

After AI classifies a document, a confirmation modal appears:

1. Review — The modal shows the AI's detected type and confidence score
2. Confirm or Override — Accept the classification or select the correct type from the dropdown
3. Save — The confirmed type is saved and the document proceeds to validation-ready state

This step ensures classification accuracy before compliance checks run.

Packet Review AuthorityCopy Anchor Link

The developer console uses the applicant self-check lane by default. Utility teams run utility screening from their utility organization context. An optional compact Review as selector may be enabled for an authorized GridWonk operator, but the server still decides which lanes that user can exercise.

Attach from Files VaultCopy Anchor Link

Reuse a previously uploaded vault file in an eligible utility or project context without uploading the bytes again. A document identity already linked to another project cannot also be attached to a second project; create or upload a distinct working copy when the UI requires one.

1. Click Attach from Files in the "Your Documents" section
2. A side sheet opens listing files from your personal vault
3. Files already linked to the current utility are filtered out
4. Click Attach next to a file to link it to the selected utility
5. The file appears in your document list immediately

This is useful when the same site-control source is relevant in more than one utility context, while keeping each project's document linkage unambiguous.

Document Revision RoundsCopy Anchor Link

When an assistant or integration returns upload, job, or review-run identifiers, keep them with the project and packet identifiers. Check the same operation after an interruption before starting another attempt, and include those references when asking support about an unresolved result. Preserve source document and page citations when sharing review findings. A completed upload or individual-document result is not a completed packet review.

For transfer failures, expired authorization, review retry and splitting, use Document troubleshooting. Retry upload sends the unchanged source through a fresh attempt; Replace is for a corrected document version. Do not repeatedly retry a protocol rejection before the underlying platform issue is resolved.

For a corrected PDF in an editable project's Documents view, choose More → Replace on the document you intend to revise. This versioned intake creates a new current logical version; it does not overwrite the bytes used by an earlier review or submitted package.

• Re-uploading byte-identical content may reuse the existing document and restore missing references without creating a new version
• Replacement is checked against the version selected when you opened the action. If that version changes before acceptance, refresh and select the intended document again
• Earlier review results remain attached to their original version; processing and review of the new version are separate outcomes
• A direct overwrite through an older upload interface may still be refused. Use the project's explicit Replace action, not a same-filename upload, to request a revision
• Documents frozen into formal submission packages remain immutable review history

Do not treat a conflict as a completed revision round. Confirm the document shown in the current project before running validation or submitting.

PDF PreviewCopy Anchor Link

Click a document card to open a full PDF preview:

• Opens in a 70% width side sheet on the right
• Uses the annotated PDF viewer with page navigation
• View the original document alongside the digitized content
• Close the preview to return to the document list

Best PracticesCopy Anchor Link

1. Ensure PDFs are not password-protected
2. Use high-quality scans for handwritten documents
3. Check the limit shown by the upload control: project uploads support up to 30 MB per file
4. Name files descriptively for easy identification
5. Use the Files Vault to reuse eligible source files, while keeping each project's document linkage distinct
6. Correct any automatic role assignment that does not match the document

Asking the Assistant About Uploaded FilesCopy Anchor Link

Useful uploaded-file questions include:

• "Which documents have I already uploaded for this utility?"
• "Do I have a lease uploaded for Duke Energy NC?"
• "Can I attach a file from my vault instead of uploading it again?"