regulatory filing version register: A docket sequence is not a folder sorted by filename
Regulatory matters often produce an application, exhibits, supplements, corrected pages, hearing materials, correspondence, and an order. Downloaded files may carry names such as "final" or "revised," but those names do not establish what the agency received or how the document functioned in the proceeding.
Begin the register with the agency, docket or cause number, matter title, and access date. For each docket entry, capture the agency's event label, filed or received date as displayed, filer, document title, direct locator, and any entry number. Preserve the source terminology. A filing prepared on one date and received on another should not be reduced to a single timestamp.
Save each permitted copy with a stable local label and hash. Record page count after confirming whether the file includes covers, certificates, or attachments. If a docket link later serves a different file, the hash and access date preserve what the team actually reviewed.
Assign document roles from evidence
Classify a document after reading the docket event and the document itself. Useful roles may include application, supplement, correction, exhibit, response, notice, hearing copy, withdrawal, staff filing, or order. The filename can help locate the item, but it should not be the basis for the role.
Keep filer language separate from agency status. A party may title a document "Final Revised Application," while the docket records it as a supplemental filing and later shows another correction. Store both labels. This allows a reviewer to see what the filer called the document without mistaking that label for an agency determination.
If a document is entered under the wrong docket number or its internal caption conflicts with the docket page, preserve both observations. Do not move it to the apparently correct matter without a documented basis. The mismatch may require agency clarification or may reveal that the file was linked incorrectly.
Inventory exhibits inside every version
A version register should reach below the filing level. List the exhibits named in the table of contents, attachment pages, and docket metadata. For each exhibit, record its label, descriptive title, page range, date if stated, and parent filing. Repeated labels such as "Exhibit A" are not unique identifiers across a docket.
Compare exhibit content as well as labels. A revised acreage table can keep the same exhibit name while changing tracts, totals, operators, or effective dates. A map may retain its title while its legend or boundary changes. Record the changed fields and pages, not merely that one file is newer.
Missing attachments are their own exception. A filing may refer to an exhibit that was submitted separately, sealed, omitted from the public copy, or unavailable because of a broken link. State which condition the docket shows. Do not report the filing as complete solely because the main PDF opens.
Distinguish correction, supplementation, and supersession
A corrected filing may replace selected pages. A supplement may add information without withdrawing the earlier document. A filing may also expressly supersede a prior version. These relationships should come from the text or docket event, not from chronological order.
Record every express replacement or supersession statement and quote enough language to identify its scope. "Revised Exhibit A supersedes Exhibit A filed on [date]" is narrower than a statement replacing the entire application. If no statement appears, leave the relationship unresolved even when the later document looks complete.
Withdrawal requires similar care. A notice may withdraw one request, one exhibit, or the whole application. Preserve the affected item and date. Do not mark every earlier docket entry withdrawn unless the notice or agency event supports that result.
Build a field-level comparison
Choose the fields that matter to the proceeding before comparing versions. Those might include applicant name, well or lease identifiers, acreage, tract list, operator, requested authority, hearing date, or proposed effective date. Copy values with page locators and retain blanks.
The comparison should show which filing first introduced a value and where it later changed. If a correction changes acreage from one total to another, keep both numbers, source pages, and document roles. Do not propagate the latest value backward into the original application.
Use a separate review column for interpretation. An analyst can note that two values appear inconsistent, but the register should not declare which one governs unless the authorized reviewer or agency record resolves that question.
Test the final order against the filing record
An order can refer to an application "as amended," incorporate an exhibit, or attach its own schedule. Reopen the operative language and list every document or exhibit it identifies. Match references by date, title, entry number, page, or other stated identifier.
Suppose the application includes Exhibit A, a supplement later files Revised Exhibit A, and the order incorporates "Exhibit A" without a date. File order alone does not prove which version the agency adopted. The register should show both exhibits and frame the ambiguity for regulatory or legal review.
Do not assume the last-filed exhibit controls simply because it appears nearest the order on the docket. A hearing transcript, staff recommendation, or incorporation clause may supply relevant context, but any conclusion belongs to the qualified reviewer. The administrative record should make that conclusion reproducible.
Preserve procedural events after the order
Later events can change how the file is understood. Corrected orders, rehearing requests, stays, amendments, withdrawals, or subsequent observations belong after the initial decision in the same register. Preserve the prior order rather than replacing it with the latest PDF.
Record when the team observed a docket status and distinguish that access date from the agency event date. If an entry disappears or a link fails later, document the condition and retain the permitted copy. A current portal view should not rewrite the historical sequence.
Quality review should recount pages and exhibits, verify docket identifiers and dates, compare hashes, test every supersession statement, and reopen the order's incorporation language. Return the file when a version relationship rests only on a filename, an attachment is missing, or the order reference cannot be matched confidently.
The handoff contains the ordered docket timeline, document-role table, exhibit inventory, field-level changes, express supersession language, unavailable records, and the narrow incorporation question. The register documents filing history. It does not decide procedural validity, agency intent, compliance, or which version legally controls.
If your team needs support maintaining a traceable regulatory filing version register, Book a free consultation.
Authoritative starting points
Use the official custodian relevant to the asset and jurisdiction. These sources help confirm terminology, record coverage, identifiers, and access routes:
Ready to Scale Your Landman Business?
Discuss a defined remote support scope for title research, lease administration, GIS coordination, or document work.
