RegPreflight
Independent reporting QA
RegPreflight products

Three products. One supervisory workflow.

RegPreflight applies a consistent review model across Rule 605 and Rule 606 while keeping each product focused on the report, calculations, disclosures, and review questions that matter for that rule.

Suite overview

Choose the report you need to review.

Each workspace can be used independently or as part of the full 605 + 606 suite.

Rule 605 Preflight

Monthly execution-quality review with full OES recalculation and prior-period change screening.

See Rule 605 details →

Rule 606(a) Preflight

Quarterly public routing review across XML, publication PDF, routing disclosures, payment disclosures, and monthly changes.

See Rule 606(a) details →

Rule 606(b)(1) Preflight

Customer-specific routing package review with request-period, package consistency, and Not-Held Exempt documentation controls.

See Rule 606(b)(1) details →
Rule 605

Execution-quality report QA

Designed for the monthly Rule 605 publication package. RegPreflight independently checks the finished report and recalculates the OES summary from the detailed report.

Open Rule 605 Preflight

What you add

  • Rule 605(a)(1) detailed report
  • Rule 605(a)(2) OES summary
  • Month-specific S&P 500 classification
  • Optional prior-month reports

What RegPreflight checks

  • File and reporting-period consistency
  • All 12 Rule 605(a)(2) OES metrics
  • Published versus recalculated values
  • Prior-period changes that may need explanation

What you get

  • Clear report findings
  • Calculation comparison detail
  • Reviewer disposition and comments
  • Supervisory PDF and QA data
Scope: Rule 605 Preflight reviews the finished reporting output. It does not independently verify source-order completeness, source timestamps, NBBO inputs, market data, or upstream inclusion decisions.
Rule 606(a)

Public routing report QA

Designed for the quarterly public Rule 606(a) package before publication. RegPreflight reviews the XML and publication PDF together and carries month-to-month review across the quarter.

Open Rule 606(a) Preflight

What you add

  • Current-quarter XML
  • Current-quarter publication PDF
  • Optional prior-quarter XML
  • Optional prior-quarter PDF

What RegPreflight checks

  • Required report fields and period information
  • XML and PDF consistency
  • Routing percentages and venue disclosures
  • Payment and Material Aspects disclosures
  • Month-to-month changes with equities and options kept separate

What you get

  • Prioritized review items
  • Equities and options change views
  • Reviewer dispositions and comments
  • Supervisory PDF and QA data
Scope: Rule 606(a) Preflight reviews the finished report package. It does not independently rebuild total PFOF from the firm's underlying routed-share data.
Rule 606(b)(1)

Customer routing report QA

Designed for customer-specific routing reports before delivery. RegPreflight reviews the finished XML and publication PDF package together with the customer-request context.

Open Rule 606(b)(1) Preflight

What you add

  • Rule 606(b)(1) XML
  • One combined publication PDF or multiple PDFs
  • Customer request date
  • Report production source
  • Not-Held Exempt basis and supporting note when applicable

What RegPreflight checks

  • Required report fields and six-month reporting period
  • XML and PDF consistency
  • Held, Not-Held Exempt, and Options populations separately
  • Order, route, venue, and transaction details in the report package
  • Not-Held Exempt documentation and reviewer context

What you get

  • Population-level report overview
  • Prioritized review items
  • Reviewer dispositions and final sign-off
  • Supervisory PDF and QA data
Scope: Rule 606(b)(1) Preflight checks the finished customer report package. It does not verify every customer order against the firm's underlying order-routing records; that requires a separate source-data reconciliation.
Shared across the suite

A consistent supervisory control framework.

The reporting rule changes. The reviewer experience stays familiar: Inputs → Analysis → Review → Supervisory Report.

Pending Review queueItems that need reviewer attention stay open until a disposition is recorded.
Reviewer decisionsRecord dispositions and comments without changing the original RegPreflight finding.
Final sign-offComplete reviewer name, date, conclusion, and overall comments before final downloads.
Retainable evidenceDownload a supervisory PDF and QA data for the completed review.

Planned Rule 606 expansion

Rule 606(b)(3) is planned on the same review framework after the current 605, 606(a), and 606(b)(1) modules are fully released and validated.