Navigation
Reading Progress
0%
Complete guide to the CS2 Analyst role. Learn systematic demo review, statistical evaluation, opponent scouting, and how to present your findings to coaches and players for maximum impact.
Difficulty
Advanced
Read Time
25 min
Author
CS2Hype Pro Team
Updated
March 2026
Role Overview
4 min
What Analysts Do
- Opponent scouting: Break down enemy teams before matches
- Statistical tracking: Monitor team and player metrics over time
- Pattern recognition: Identify recurring tendencies in demos
- Report creation: Deliver clear, actionable briefs to coaches
Analyst vs Coach
- Analyst: Focuses on data collection, pattern identification, and reporting
- Coach: Focuses on strategy creation, player development, and match-day decisions
- Overlap: Both review demos, but with different goals and depth
- Partnership: The analyst supplies the data, the coach acts on it
Career Paths
The analyst role has become increasingly valued in professional CS2. Many analysts transition into coaching, broadcast talent, or dedicated scouting roles for organizations. Building a portfolio of thorough analysis work is the best way to break into the scene.
Demo Review Process
5 min
Review Workflow
1
Open your note-taking template. Record match context: teams, map, date, tournament stage, and final score. Set up your demo viewer with the overhead view ready.
2
Skim through the demo tracking buy decisions. Note force buys, eco rounds, and when each team reaches key economic thresholds. This frames every tactical decision that follows.
3
Watch full-buy rounds closely from overhead. Document defaults, mid-round adjustments, and execute patterns. Record utility usage per player and per round type.
4
Follow key players one at a time. Track positioning habits, aggression triggers, and performance under pressure. Note consistent tendencies that can be exploited.
5
Compile findings into a brief. Separate facts from opinions. Prioritize the 3-5 most impactful takeaways that the coach can act on immediately.
Note-Taking Best Practices
- Use timestamps for every observation
- Tag notes by category (utility, positioning, economy)
- Include round number and side for context
- Capture screenshots of key setups and positions
Common Pitfalls
- Result bias: Do not assume winning rounds were well-played
- Overfitting: Avoid building conclusions on one or two rounds
- Missing context: Always consider the economy and score when evaluating decisions
Statistical Analysis
5 min
Key Metrics to Track
| Metric | What It Measures | Why It Matters |
|---|---|---|
ADR | Average Damage per Round | More consistent than K/D -- shows true impact |
KAST | Kill/Assist/Survived/Traded percentage | Measures round-by-round contribution |
Impact | Multi-kills, opening kills, clutch wins | Highlights game-changing moments |
Utility DMG | Damage dealt via grenades | Indicates utility efficiency and site control |
FK/FD | First Kill to First Death ratio | Measures opening duel success rate |
Context Matters
A player with 60 ADR might be the best support player on the team, sacrificing stats to enable others. Always evaluate numbers in the context of role, opponent quality, and map. Comparing an entry fragger's K/D to a support player's K/D is meaningless without role context.
Opponent Scouting
5 min
Scouting Report Structure
Team-Level Analysis
- Defaults: Standard CT and T setups on each map
- Executes: Full utility sequences and timing for site takes
- Tendencies: How they react to early picks, eco rounds, overtime
- Economy: When they force, when they save, bonus round patterns
Player-Level Analysis
- Star player: Preferred positions, peek timing, how they react when shut down
- AWPer: Angles held, aggression level, repositioning habits
- IGL: Calling patterns, timeout tendencies, adaptation speed
- Weak link: Player who struggles most under pressure
Identifying Exploitable Patterns
Predictable Defaults
If a team uses the same default setup in 70%+ of rounds, your team can pre-aim and pre-nade those positions with high confidence.
Rotation Timing
Measure how fast the team rotates. Slow rotators can be exploited with quick executes. Fast rotators are vulnerable to fakes and split attacks.
Tilt Triggers
Some teams collapse after losing pistol rounds or anti-ecos. Identifying these mental triggers lets your coach apply targeted pressure.
Presentation & Communication
4 min
Effective Reporting
Good Report Habits
- Lead with the 3 most actionable findings
- Use screenshots and video clips to illustrate points
- Keep written reports under 2 pages per map
- Separate confirmed patterns from one-off observations
- Provide specific round references so the coach can verify
Visual Aids
- Overhead screenshots: Mark default positions with player labels
- Utility maps: Show smoke, flash, and molotov landing spots
- Timeline charts: Visualize when executes happen by round clock
- Heat maps: Display where a player dies or gets kills most often
Briefing Your Team
When presenting to players, keep it short and visual. Players absorb information differently from coaches. Focus on what they need to know for their specific role.
- Entry fragger: Where opponents hold, which angles are favored
- AWPer: Enemy AWP positions and how to counter-AWP
- Support: Utility lineups that counter specific setups
- Lurker: Rotation timing data and flank opportunities
Tools & Resources
3 min
Core Platforms
| Tool | Purpose | Key Features |
|---|---|---|
| HLTV.org | Match stats and player data | Rating 2.0, head-to-head records, map stats |
| CS2 Demo UI | In-game demo playback | Free-cam, X-ray, round selection, speed control |
| Leetify | Advanced performance analytics | Aim stats, positioning ratings, utility efficiency |
| Scope.gg | Demo analysis automation | 2D replays, flash efficiency, opening duels breakdown |
| Notion / Google Sheets | Report organization | Templates, collaboration, data tracking over time |
Building Your Workflow
- Create a reusable scouting report template
- Build a database of opponent tendencies over time
- Use spreadsheets to track stats across multiple matches
- Archive demo clips for future reference and comparison
Staying Current
- Follow professional matches weekly to track meta shifts
- Join analyst communities to share methods and learn
- Experiment with new tools as the ecosystem evolves
- Practice by publishing public analyses to build a portfolio