Drop the mouse: keyboard workflow is how you actually scan 1,080 charts

A practical 10-minute workflow to move from scanning to focused review in a 1,080-chart workflow using keyboard controls, EMA/NRZ interpretation, consensus hotlist cues, check notes, and templates.

ENKO

In trading, the first question is rarely “which chart to open next.” It is usually: what should I evaluate first?

In 1k_scanner, keyboard-first workflows reduce context switching and keep your observation order stable. This post is a practical 10-minute routine you can use immediately in a 1,080-chart environment.

1) Start routine: first 30 seconds after launch

Use this order whenever you launch the app.

  1. Confirm current tab and grid state

    • Check whether the loaded workspace is the one you want to work with.
    • If not, return to your scanning view first.
  2. Begin with a wide view for candidate selection

    • Ctrl/Cmd + 7: dense grid (many symbols at once)
    • Ctrl/Cmd + 8: expanded grid (focus on fewer symbols)
  3. Lock the grid mental model

    • The grid is built as rows = timeframes, columns = symbols.
    • A single column gives a multi-timeframe sequence for one symbol, so comparison is faster and less fragmented.

Completing this pre-check keeps the process from turning into random clicking and turns it into a structured sequence of questions.

2) First pass scanning: treat EMA/NRZ as context checks

How to read EMA/NRZ without overfitting

  • Use EMA (persistence view) as a clue for how durable the current flow looks.
  • Use NRZ as a clue for whether pullback handling is coherent enough to stay in the setup.

At this stage, use only two operational questions:

  • Is this candidate aligned with the larger directional context?
  • Is the pullback showing structure that can hold, or is it already losing coherence?

Read consensus signals as filter signals, not entry signals

For many users, this is the most important shift.

  • When multiple observations point in the same direction, the symbol receives a directional frame cue (long/short color and stronger emphasis).
  • When directional input is mixed, neutral, or weak, the symbol is less emphasized (often no strong frame cue).

The key is not “consensus = guaranteed entry.” The key is “consensus helps me narrow which names deserve close review.”

So do not lock entry decisions there. Use consensus as a candidate filtering step first.

3) Focus routine: scan → expand → decode

After candidates are narrowed:

  • Move the focus with arrow keys or W/A/S/D.
  • Use Space to toggle single-chart expansion.
  • Refine checks within that symbol across nearby time windows.
  • Switch between Ctrl/Cmd + 7 and Ctrl/Cmd + 8 to balance breadth and focus.

In expanded mode, do not jump to action immediately. First lock the larger context in the same column, then confirm pullback/structure behavior in lower frames.

4) Check-note routine: V to add, N to review

A 1,080-chart workflow helps you see more, but memory can still fragment. Use this note loop to prevent that.

  • V: add or toggle current chart in Check Note.
  • N: open the CheckNote section and review.

A simple note template:

  1. Why this symbol became a candidate (one line)
  2. Why it is rejected or delayed (one line)
  3. Next check plan (one line)

This is lightweight, but it preserves your decision history and avoids losing rationale between sessions.

5) Template workflow: keep scanning reproducible

Even the cleanest keyboard rhythm is unstable without repeatable templates.

  • Generate template: set Grid Size, Timeframes per row, Exchange, then run Generate Template (by size)
  • Save layout: persist the current workspace view with F12
  • Load layout: reopen a saved layout with Ctrl/Cmd + L

Two templates are enough to start:

  • Scanning template: broad symbol coverage for fast narrowing
  • Focus template: fewer symbols with larger spacing for detailed review

6) 10-minute repeatable checklist

First 2 minutes

  • Launch app and confirm workspace
  • Open dense grid with Ctrl/Cmd+7
  • Trim to ~8–12 candidates from consensus frame cues

Next 4 minutes

  • Read each candidate by symbol column (row-by-timeframe, column-by-symbol)
  • Check EMA/NRZ for persistence + pullback coherence
  • Keep consensus cues at “priority” level only, not entry-level yet

Next 3 minutes

  • Expand each candidate with Space
  • Add notes with V
  • Exclude weak candidates and log the reason

Final 1 minute

  • Open N and close the loop on notes
  • Save/load your routine layout for next session

1k_scanner is not a document scanner. It is a Rust+egui based multi-market, multi-timeframe trading scanning app. It is designed so you can reduce how much you have to search manually and focus your attention on the candidates that are worth your next decision cycle.

Built with Hugo & Rust enthusiasm.
Built with Hugo
Theme Stack designed by Jimmy