Checklists

When an AI agent prepares a filing package, the result is presented as a structured collection of data, documents, and artifacts. The filing detail view in the queue organizes this information into reviewable sections so you can thoroughly examine every part of the package before making a decision.

Reviewing a Filing Package

When you select a filing from the queue, the detail view loads with the following sections:

Agent Summary

The agent provides a plain-language summary of what it did and what it found. This is a good starting point for your review — it highlights the key conclusions, any issues the agent flagged, and the overall recommendation.

Read this carefully before diving into the specifics. If the agent flagged missing data or uncertainty, those are areas to pay extra attention to.

Form Data Fields

This section shows the actual form fields that will be submitted to the RRC (for example, Form W-1 or Form R-32 data). Each field is displayed as a key-value pair:

• Field name — What the field represents (for example, “Operator Name,” “API Number,” “Lease Name”)
• Field value — The data that will be submitted

Fields marked [REQUIRED] in red are mandatory fields that have not yet been populated. These must be resolved before the filing can be approved.

Spacing Analysis (Rule 37 Filings)

For spacing exception filings, you will see a dedicated analysis section showing:

• Lease line distance — The distance from the proposed well to the nearest lease line, with a PASS or FAIL indicator against the standard (typically 1,200 ft for a 40-acre unit)
• Nearest well distance — The distance to the closest offset well, with a PASS or FAIL indicator against the standard (typically 467 ft)
• Offset wells table — A list of nearby wells that may be affected, including their names, API numbers, well types, and statuses

This data comes from the agent’s spacing calculations and knowledge graph queries.

Good Cause Narrative (Rule 37 Filings)

When a spacing exception requires a “good cause” argument, the agent drafts a narrative that will be included in the filing. Review this narrative for:

• Accuracy of the facts cited
• Completeness of the justification
• Appropriate references to RRC rules and precedent
• Professional tone suitable for a regulatory submission

Required Attachments

A checklist of documents and attachments that must accompany the filing. Each attachment has a status:

HITL Review Checklist

Some filings include a review checklist — a set of items for the human reviewer to confirm before approving. These appear as checkboxes that you can mark as you complete your review:

• Verify operator information is correct
• Confirm well location data matches survey
• Review spacing calculations against plat
• Validate offset well notifications are complete

This checklist is for your tracking purposes and helps ensure a thorough review.

Audit Trail

At the bottom of the filing detail, the audit trail records every action taken on this filing:

• Created — When the agent generated the filing, which agent created it, the execution ID, token usage, and cost
• Skills used — Which AI skills were employed (spacing calculation, filing assembly, etc.)
• Entities referenced — Which entities from the knowledge graph were consulted
• Decision — If a decision has been made, the reviewer, timestamp, and any comments are recorded

The audit trail is append-only — entries cannot be modified or deleted. This provides a complete, tamper-proof record of the filing lifecycle.

Navigating Between Filings

Click different filings in the left-side queue list to switch between them. The detail view updates immediately. Use the Close button in the detail header to return to the full queue view.