Screening
Review package-bound application findings and utility screening decisions.
How Automated Screening Works
The Salesforce connector remains disabled pending acceptance. Its independent review gate stays closed until every captured field and declared file is transferred, processed, and resolved; failed or expired intake batches cannot permit a partial review. Source-managed packets cannot use ordinary Screen Selected to bypass that gate. After the exact completed review, connector recovery now freezes an immutable package with the real human or service actor before completing the import. It does not change queue status, decisions, or notices. Live pilot acceptance remains open.
Connector retries reuse the saved package only after rechecking current access and the exact completed review. A revoked permission or changed source revision blocks reuse; it does not turn the saved result into a new screening decision.
When you trigger screening for selected applications, GridWonk runs the whole-packet review engine in the utility lane: one utility_screening run per application, the same engine that reviews a developer's packet before submission. The run reviews the current document versions against your utility's published packet requirements and records findings with citations.
Only formal submissions enter the utility queue. A developer's private draft, replacement files, and private correction reviews are not available for utility screening. Previously received frozen packages remain visible during a correction round.
The Screening Pipeline
Each run is a durable workflow, shown as grouped stages in the jobs tray:
| Stage | What It Does |
|---|---|
| 1. Digitize | Converts each current document version to extractable text |
| 2. Review | Checks the whole packet against your utility's published packet requirements |
| 3. Findings | Records each deficiency with severity, citation, and page reference |
| 4. Package | For a packet your utility originated, the immutable package is frozen pinned to the completed run: automatically when the utility-packet-screening feature is on for your organization, otherwise with Freeze package |
Which utilities can screen
Automated review is switched on per utility (the packet-review switchboard). For a utility that is not on it, Screen Selected reports Automated review is not yet available for this utility for each of that utility's rows. Those rows stay unchanged and notices stay manual; there is no fallback to the retired per-document pipeline.
Screen Selected reports its result per application: started rows leave the selection, and refused rows stay selected with the reason shown above the table.
A combined PDF whose applicant confirmed a split is retired source material: screening selects and aggregates only its derived child documents, so the retained combined source never contributes duplicate findings or counts alongside its children. Project lists, the portfolio, and status views apply the same rule, so document and deficiency counts match across every surface.
Screening work is tied to the exact uploaded document generation it started from. If an applicant replaces a document during processing, the older generation stops without attaching stale findings or a stale validation verdict to the replacement file. The replacement generation owns the next screening result.
Until that replacement finishes review, the Review view hides findings from the replaced bytes and shows Document re-review pending. Aggregate counts do not reuse the older result, and Begin deficiency notice remains unavailable so the utility cannot send an incomplete packet-wide notice.
Reviewing Screening Results
After screening completes, open the application from Applications and choose Review in the header. The selected immutable package determines which document versions and findings you see. The other header views are Overview, Documents, Communications, and History.
Findings show severity, description, page reference, and requirement provenance when available. Use the package selector to inspect an older snapshot; historical packages are read-only. If no review is pinned, or its stored identity does not match the selected package, the view explains that state rather than displaying unrelated results.
The old six-tab shell and standalone Screening view are removed. Existing Screening bookmarks redirect to the current application workspace. Stored legacy scores remain historical data; this change does not delete or recalculate them.
Point-of-interconnection evidence
When enabled for the packet owner, the selected package report can include a Point of interconnection section. It shows extracted coordinates, source pages, inspection coverage, and comparisons between explicitly labelled points of interconnection (POIs). Open the source to check the original document before recording a human decision. Missing coordinate-system information or unsupported documents remain unresolved; nearby coordinates do not prove that two labels describe the same physical point.
Standard geographic review covers application forms, site plans, single-line diagrams, equipment specifications and site-control documents. Supporting documents and native DWGs are not geographically inspected. An accepted PDF companion contributes evidence only when it has one of those document roles. Document coverage preserves missing, incomplete and failed interpretations; no coordinates found requires every page to have been explicitly inspected by at least two complete interpretations.
The report shows actual interpretation counts and the number of existing text transcriptions they used. One interpretation requires source review and does not establish a map location. Multiple interpretations sharing one optical character recognition (OCR) transcription are not independent confirmations of its digits. Conflicting evidence remains unresolved and is not mapped, even when the same transcription is repeated. View source opens the safe PDF rendition of the reviewed version, page and available region. Missing text recognition does not block the ordinary document review from using the PDF.
POI decisions are separate from deficiency adjudication and packet approval. They belong to the selected review and source version; changing the documents requires a new review. Older package evidence remains read-only. Map display is optional and loads only after Show map; the evidence table remains available when the map is unavailable. Developer review begins in Projects → Review → Report.
Generating a Notice from Screening
When you're ready to communicate deficiencies to the applicant:
- Review and adjudicate the package findings in Review.
- Use the package screening decision to begin a notice when the current package is eligible.
- Continue in the Notice Composer for review, approval, sending, and applicant acknowledgment.
Notice eligibility remains server-checked against the selected package and current review. Removing the old screen does not bypass authorization, finding decisions, or document re-review requirements.
Real-Time Updates
Screening status updates appear as the selected application refreshes and as reviewers revisit the queue. If a run is still in flight, keep the application selected or reopen the row after the queue status changes.
Related
- Application Queue — Managing your application queue
- Document provenance — How indexed utility sources become cited findings
- Deficiency Notices — The notice workflow
- For Utilities — Utility workspace overview