FTFC
FTFC stands for Full Timeframe Continuity. It is a STRAT concept that checks whether multiple higher timeframes align in direction. FTFC is a context filter, not a standalone confirmation.
How it is computed
FTFC compares the close versus open on higher-timeframe candles. It does not rely on 2u or 2d status, only the directional close.
Timeframe rules
FTFC always uses the next higher timeframes for the selected row, up to five. The exact list depends on the base timeframe.
- 15m uses 30m, 1h, 2h, 4h, D.
- 30m uses 1h, 2h, 4h, D, 2D.
- 1h uses 2h, 4h, D, 2D, 1W.
- 2h uses 4h, D, 2D, 1W, 2W.
- 4h uses D, 2D, 1W, 2W, 1M.
- D uses 2D, 1W, 2W, 1M, 3M.
- 2D uses 1W, 2W, 1M, 3M, 12M.
- 1W uses 2W, 1M, 3M, 12M.
- 2W uses 1M, 3M, 12M.
- 1M uses 3M, 12M.
- 3M uses 12M.
- 12M has no higher timeframes.
FTFC filters
FTFC min sets a numeric threshold. FTFC must include controls that let you require any of the higher timeframes listed for the selected row. For intraday scans, that list can include 30m, 1h, 2h, and 4h before the daily and higher timeframes. For 1M you only have 3M and 12M; for 12M there are no higher timeframes to select. In the table, each required timeframe is shown with a check or x plus a score (for example D check, 2D check, 1W x, 2W check, 1M check, then 4/5).
Why it matters
FTFC alignment helps you observe whether higher timeframes agree. Treat it as context for interpreting structure, not as a trigger by itself.