BattleIQ tutorial
How to Read BattleIQ Team Analysis and Speed Tiers
Understand BattleIQ Team Overview, Matchups, Speed, Coverage, Archetypes, and how to turn analysis findings into team changes.
Use Team Overview as the first pass
Team Overview is a summary layer. It is designed to tell you what deserves attention before you inspect more detailed damage, speed, matchup, and coverage evidence.
Read strengths and warnings as prompts. A warning does not automatically mean the team is bad, and a strength does not mean the team is finished.
Read Matchups as evidence groups
The Matchups tab groups common threats and practical answers so you can see which Pokemon pressure your team and which members are expected to help.
Open details when a matchup looks close. Representative moves, KO races, survivability, and speed assumptions often explain why a label is favorable, neutral, or concerning.
Use Speed Tiers to ask turn-order questions
Speed Tiers show where your Pokemon sit against important benchmarks. Adjusted speed can include items and field effects when the relevant state is selected.
Use this view to decide whether your team needs Tailwind, Trick Room, Choice Scarf, priority, paralysis support, or simply more natural speed.
Treat Coverage as pressure, not a win condition
Coverage views show how well your team can hit or switch into important types and targets. They help reveal repeated weaknesses, missing resistances, and offensive blind spots.
Coverage alone does not prove a matchup is solved. A Pokemon may technically hit a target while still losing the speed race, failing to survive, or needing an unrealistic move slot.
Use Archetypes to find structural gaps
Archetype checks look for broad team plans such as weather, speed control, screens, setup, priority, disruption, or balance.
A missing archetype is not always a flaw. The point is to make sure your team has a coherent plan and backup lines instead of six isolated sets.
Turn findings into team changes
After reading the analysis, choose the smallest change that addresses the highest-risk issue: a move, item, spread, ability, or team slot adjustment.
Retest after every meaningful change. Team analysis is most useful as an iterative loop: adjust one thing, recheck the evidence, then decide whether the team actually improved.