Two Disjoint Measurement Domains in One Scanner
Screener designers often combine price momentum filters with profitability ratios without realizing both metrics evaluate entirely different dimensions of market reality.
Fundamental parameters—such as return on equity, debt-to-capital, or quarterly free cash flow—reflect past accounting cycles validated over three-month reporting windows. They answer questions about business health, competitive positioning, and operational solvency. Conversely, technical filters evaluate instantaneous order flow, volatility bounds, and price distribution across moving bar sequences. Blending them into a single Boolean filter without establishing hierarchical precedence creates screening queries that contradict themselves.
When a researcher demands an asset possessing top-decile return on equity while simultaneously requiring an acute 14-day relative strength contraction below 30, the screener is forced to reconcile two divergent economic regimes. The fundamental filter demands institutional stability, whereas the technical condition isolates severe short-term distribution or crisis pricing. Understanding that these conditions answer distinct inquiries prevents arbitrary parameter tweaking when result tables return empty.
Test Your Query For Dimension Collisions
Verify whether your screening criteria isolate company quality or current price state before nesting conditional operators.
The Latency Gap Between Filings and Tape Prints
Corporate filings update quarterly with reporting delays ranging from fifteen to forty-five days after the close of an accounting cycle. Technical oscillators evaluate ticks, minutes, or daily closes that adjust every fraction of a second. This asynchronous temporal foundation means fundamental data serves as a semi-static container, whereas technical indicators serve as a dynamic temporal state machine inside that container.
- Fundamental Refresh Cycle
- 90-Day Reporting Interval
- Technical Observation Interval
- Intraday to Daily Ticks
- Primary Question Answered
- What is the business state?
- Secondary Question Answered
- How is price behaving now?
When screener syntax attempts to evaluate both variables on equivalent parity—such as setting an OR clause between operating margin expansion and moving average slope—the query generates categorical noise. Companies with superb balance sheets experience normal multi-week drawdowns, while insolvent enterprises routinely exhibit explosive technical short squeezes. Decoupling the questions allows an analyst to define the investigable universe with fundamental boundaries before applying technical filters strictly as observational timing filters.
“A fundamental filter defines what kind of instrument qualifies for examination; a technical filter identifies the observational window in which that instrument currently resides. Mixing the two inquiries into a single flat rule obscures both.”
Building Structured Two-Tier Screening Workflows
Sound screener design resolves dimension friction by converting flat queries into sequential evaluation funnels. Rather than evaluating six technical and four accounting variables simultaneously in a single Stock Hacker query block, experienced researchers construct an outer boundary condition followed by focused behavioral conditions.
In practical workbook implementations, tier one filters out structural unsuitability through market capitalization minimums, debt boundaries, and earnings reporting status. Once the permissible instrument basket is locked, tier two applies technical logic—such as 50-day volume percentiles or consolidation ranges—without disturbing the underlying fundamental population. This separation keeps the output interpretable during visual manual review.
Diagnostic Checklist for Multi-Factor Queries
Before launching a multi-variable scan across broad market indices, run through a systematic logic audit. Identify every filter variable, write out the explicit English question it attempts to answer, and note its update frequency. If any two criteria evaluate conflicting market hypotheses or mismatch temporal horizons by orders of magnitude, isolate them into discrete sub-queries.