Methodology
How NFA Watch Works
NFA Watch is an operational intelligence system built on approval reports from the NFA filing community. This page documents how data is sourced, how operational conditions are derived, and the editorial principles that govern interpretation.
Data Sources
Every record is an approval that a filer reported — form type, filing date, approval date, ownership structure, and wait time. There is no government data feed and no official ATF data access.
Reports reach NFA Watch both directly, through the submission form on this site, and from approval reports filers share within the NFA community. No account names, contact details, or other identifying information are stored — only the filing facts themselves.
Every record is self-selected: it exists because someone chose to report an approval. People who never report never appear in these figures. That is the platform's constraint as well as its strength — the data reflects real approval outcomes, but it does not represent a complete census of all approvals, only those that surfaced.
What These Numbers Can and Cannot Tell You
A median computed from reported approvals describes the approvals that were reported. It does not automatically describe every filing ATF processed. Two limits govern how far these figures can be read, and both are worth knowing before relying on one.
Right-censoring
Recent filing months read artificially fast. Only the quickest approvals from a recent cohort have happened yet — everyone still waiting has no approval date and so contributes nothing. This is the most consequential caveat on the site, and it is why recent-month figures rise over time rather than settle. Comparison windows deliberately end several days back so that late-arriving reports cannot skew the recent end.
Reporting bias
Whether people who waited a long time report at a different rate than people who did not is a fair question, and it cannot be fully answered from inside a self-selected sample. Internal checks find no difference large enough to clear this site's own sample-size and interval thresholds — but that bounds only what is measurable internally. No figure here should be read as a precise estimate of what every filer experienced.
Where a figure is too thin to support a claim, this site shows nothing rather than a weak number. These floors are applied before any median is published.
Sample floors in use
Lane medians on the dashboard, the wait-times page and the embeddable badge require at least 15 e-file approvals within a 90-day window. Window-over-window comparisons require at least 8 approvals in each window and use an order-statistic confidence interval rather than a point estimate. Cohort alerts require at least 3 nearby approvals. State pages require 20 reported approvals before any state-specific median is shown, and each form-and-owner cell within a state carries its own minimum. Below any of these, the figure is withheld rather than estimated.
The estimator
Entering a filing date returns the distribution of wait times among reported approvals with nearby filing dates — a typical wait, a faster end and a slower end. It is a read of what comparable filers reported, not a prediction of any individual approval date, and it carries its own confidence tier and censoring warning based on how mature the cohort is.
Operational Definitions
NFA Watch uses a consistent operational vocabulary derived from queue behavior analysis rather than individual approval events. These terms describe emergent properties of the approval distribution, not individual timelines.
Frontier
The filing date boundary of active ATF approval processing — the cohort currently being worked through. When recent submissions show approvals concentrated in filings from a specific month, that month defines the operational frontier. A frontier of '8 months ago' means the queue is actively processing filings submitted approximately eight months prior.
Regime
The behavioral classification of the queue's current distribution: stable (consistent spread across cohorts), compressing (narrowing toward a tighter cohort window), volatile (irregular spread with inconsistent cohort spacing), or fragmenting (highly inconsistent, multi-cohort dispersion with no clear processing pattern).
Trajectory
The directional momentum of approval velocity: accelerating (increasing rate of cohort advancement), slowing (decreasing rate), or flat (no material directional change). Trajectory reflects the recent direction of frontier movement, not its speed in absolute terms.
Compression
The degree to which approval activity concentrates within a narrow range of filing cohort dates. High compression indicates focused processing — the queue is working through a tight window of filings. Low compression indicates dispersed processing across a wider cohort range.
Frontier Velocity
A signed measure of how quickly the frontier is advancing toward more recent filing cohorts. Positive velocity indicates advancement. Negative indicates the frontier is retreating or stalling. Velocity is derived from recent cohort movement signals and scored on a -3 to +3 scale.
Context
A filing structure segment. Four disjoint lanes cover every filing exactly once: Form 4 Trust, Form 4 Individual, Form 1 Trust, and Form 1 Individual. Comparisons, rankings, and superlatives (fastest, slowest, steadiest) run only across these four lanes. Global, Form 4, and Form 1 are aggregates — blends of the lanes beneath them, shown for reference in tables and charts, but never ranked against their own components.
Divergence
A widening of operational differences between filing contexts — when lanes process cohorts at meaningfully different rates. Divergence expansion means the gap between the most and least advanced contexts is increasing.
Convergence
A narrowing of operational differences between filing contexts — lanes moving toward more similar processing conditions. Convergence does not imply improved conditions; it indicates the gap between contexts is narrowing.
Signal Detection Methodology
Operational signals are derived from multi-day persistence patterns in the queue data — not from single-day observations. A signal requires repeated confirmation across consecutive captures before it is recognized by the system.
This persistence threshold exists to prevent single-day noise from being interpreted as meaningful operational movement. A frontier advancement on one day is an observation. The same advancement across five consecutive captures is a developing signal.
Signal Strength Thresholds
Weak — 2 consecutive confirmations
Developing — 3–4 consecutive confirmations
Established — 5–6 consecutive confirmations
Structural — 7+ confirmations with broad context participation
Signal confidence further reflects breadth: how many filing contexts show the same pattern. A signal visible only in the global composite is tentative. The same signal confirmed across multiple filing structures is elevated to moderate or confirmed confidence.
All signal detection is deterministic and threshold-driven. No machine learning or statistical modeling is involved. Every signal can be traced to a specific sequence of observable conditions in the data.
What Signals Are Not
Signals are observational persistence records — not predictions. A “frontier acceleration” signal means frontier advancement has been consistently observed across multiple captures. It does not mean advancement will continue.
A “divergence expansion” signal means the operational spread between filing contexts has been widening in recent observations. It does not predict the spread will reach any specific level or duration.
Signals describe what the queue has been doing. They make no claim about what it will do. The distinction is deliberate and non-negotiable.
Language and Epistemic Constraints
NFA Watch avoids prediction language throughout the platform. Words like “will,” “expected,” “guaranteed,” and “soon” do not appear in operationally-generated content.
The NFA approval process is an administrative operation subject to ATF staffing levels, policy changes, processing priorities, and factors that are not observable from approval data alone. Any prediction made from community-sourced approval records would be speculative rather than analytical.
The language the platform uses — “appears,” “continues,” “may be broadening,” “is persisting” — reflects this constraint. Conditions are observed and interpreted, not forecast.
Structural Themes
Structural themes differ from operational signals. Signals require days of persistence. Structural themes require weeks — typically seven to thirty or more consecutive observations confirming the same operational asymmetry.
A structural theme represents an entrenched operational condition: a persistent gap between filing contexts, a sustained stabilization period, or a recurring leadership rotation pattern. These are qualitatively different from daily signal noise.
Structural themes are surfaced separately and carry a longer-term interpretive weight than emerging signals.
Publication Philosophy
NFA Watch publishes operational intelligence on a significance-driven cadence, not a calendar cadence. Quiet operational periods produce no publication. Meaningful regime transitions, persistent structural changes, or significant divergence events warrant documentation.
The goal is institutional continuity — a longitudinal record of what the queue was doing, in what operational context, and with what structural framing. Frequency is subordinated to significance.
Publication artifacts are designed to age gracefully: the operational state at the time of publication should be reconstructible from the content alone, without relying on external context.
Interpretation Principles
Observational, not predictive
Operational interpretation describes what is occurring and what has been occurring — not what will occur.
Persistence over noise
Single-day conditions are noted but not amplified. Persistent conditions across multiple captures are given interpretive weight.
Breadth over isolated movement
A condition visible across multiple filing contexts carries more interpretive weight than one isolated to a single lane.
Structural over emotional
The platform interprets queue structure — not individual experiences. Operational conditions are characterized by their systemic properties, not their human impact.
Continuity over headlines
Institutional memory matters. Current conditions are interpreted in the context of prior observations rather than presented as isolated events.
Deterministic over probabilistic
All analytical outputs are derived from threshold-based rules operating on observable data. There are no confidence intervals, no probabilistic outputs, and no black-box models.
This methodology documentation reflects the current analytical approach as of the latest platform update. Methodology evolves as the platform matures. Community submissions and operational feedback improve the system over time.