Most coaches can remember how last month’s game felt. The three-hole hitter “looked dangerous.” The nine-spot “couldn’t catch up to the rise.” The leadoff batter “always seemed to be on base.” Those impressions shape the next matchup—until they don’t. Memory compresses a full order into a few highlight moments, mixes one pitcher’s outing with a reliever’s, and quietly upgrades a couple of extra-base hits into a scouting report that was never actually written down.
The fix is not a thicker notebook. It is attaching a name, jersey, and stance to every pitch you already log—then reading the stats that accumulate against those same hitters the next time you see them.
That is what Opposing Rosters and Scouting Reports in Pitch MetRx are built to do. Save the opponent’s batter list once. Score named hitters live. Watch per-batter lines (PA, BAA, SLG%, K, BB) grow across games. Before the rematch, generate an AI attack plan from your pitcher’s real history—not a generic scouting sheet, and not last week’s gut feel.
The problem with sequential batter numbers
Pitch MetRx still lets you chart fast with sequential Batter # and a RH/LH prompt. That workflow is fine when you need to get pitches in the log and you do not have a lineup card yet.
The limitation shows up the moment you want to coach the matchup, not just the outing:
- Batter 3 in game one is not the same person as Batter 3 in game two.
- A pinch hitter disappears into the sequence unless you captured who actually completed the plate appearance.
- Reports can split left-handed vs. right-handed hitters, but they cannot tell you whether #12 Smith is the one who has been unsuccessful vs. your changeup.
- Next week’s pre-game meeting has no named history to pull—only aggregate pitcher stats against “that team.”
Named-batter logging is what turns a pitch chart into opponent intelligence. Without names on the pitches, you can still develop your pitcher. You cannot reliably scout their lineup.
Roster vs. lineup: save the list, score today’s order
Two terms get mixed together in dugouts. Pitch MetRx keeps them distinct on purpose.
A roster is the saved player list for an opponent team—batter name, optional jersey (0–99), and stance (RH, LH, or blank). You build it once on Opposing Rosters and reuse it every time you face that team.
A lineup is today’s batting order in a live game—Lead-Off, 3-Spot, 9-Spot, and extra spots up to 20. Attach a saved roster at New Game Setup or Schedule a Game, or fill a new lineup during the game if you do not have the order yet.
That split is the coaching payoff:
- Game-day setup becomes a dropdown ({Team} - Roster) instead of retyping nine names while the umpire is walking to the plate.
- Live scoring shows the current hitter like a real lineup card—name, jersey, slot, and stance—so the pitch caller and the chartist are looking at the same person.
- Later roster edits do not rewrite past games. Each outing keeps its snapshot. History stays honest.
- New hitters who show up mid-game can be added and, after you confirm, saved to that roster—not a duplicate copy.
Jersey numbers matter more than they look. Two “M. Johnson” entries on a travel weekend are different people if one wears 7 and the other wears 17. 0 and 00 stay distinct. Identity matching is what makes per-batter stats trustworthy when you generate a scouting report later.
What opposing roster stats actually give you
Once games are scored with named lineups, each roster card is more than a contact list. It is a running ledger of how your pitchers have done against those hitters.
Typical per-batter lines include pitches, plate appearances (PA), hits, BAA, SLG%, strikeouts, and walks—accumulated across logged games vs that team. Team scouting reports add a TOTALS row and let you tap a batter name with logged pitches to open that hitter’s individual report.
Read those numbers as hitter results vs your pitching, not as an official season batting average from another team’s statkeeper.
BAA (batter view vs your staff): under .200 is unsuccessful hitting for average; .250–.299 is mixed; .300+ is a real threat. A line like BAA .196 with SLG .435 is not “significant success.” The extra-base number lives on a higher scale than batting average. Average extra-base production does not upgrade a poor BAA into a dangerous hitter. Thin samples—under about 15 pitches or 5 plate appearances—stay qualitative. One double in four PAs is a note, not a scouting gospel.
That discipline is the benefit. You stop promoting the three-hole hitter to “their best bat” because they ripped one ball last time, and you stop burying a nine-spot who has quietly been on base with walks. The roster stats tell you who has actually been successful against you.
Handedness comes along for free. Stance on the roster drives LH/RH filters in reports and scouting, so you can see whether your riseball is playing against lefties in that order or whether the damage is concentrated in a couple of right-handed middle-of-the-order bats.
Why tracking the same hitters compounds over a season
Conference, league, and travel schedules are full of rematches. That is where named-batter history pays for itself.
First look: you may only have a roster and a thin sample. Pitch MetRx will not invent hot zones. A roster-only or thin-history scouting report stays cautious—identity and what little you logged, not a fake spray chart.
Second look: the same names now have PAs attached. You can see who expanded the zone, who sat on first-pitch fastballs, and which pitch types produced outs vs extra-base hits. The conversation with your pitcher changes from “be careful with their three-hole” to “Smith is .125 BAA in 16 pitches vs your changeup outside; Jones has walked twice in five PAs—attack the zone earlier.”
Tournament weekend: import a CSV before you arrive, attach the roster at game time, and keep adding pinch hitters as the order changes. By Sunday you have named history from Friday and Saturday instead of three separate “Batter #” charts that cannot be joined.
Staff handoff: export CSV or PDF from Opposing Rosters so an assistant who is not holding the tablet still has the opponent list. The scouting report PDF carries the same branded header as your other Pitch MetRx reports—usable in a pre-game meeting without rebuilding a spreadsheet.
None of this requires stadium radar. It requires logging the pitch call and outcome you already track, with the batter’s name on the row.
Scouting reports: pre-game attack plans from real pitch logs
Scouting Reports turn that named history into a plan you can walk into the circle or the mound meeting with.
Open Reports → Scouting Report, choose Team or Batter, select the pitcher who will throw, then the opponent (and the batter, if needed). You can also start from a roster card: Scout Team for the whole order, or Scout on a named batter while editing. Custom Reports that already filter by opponent or batter name can launch the same flow.
A team report gives you an AI narrative (overview, handedness, pitch mix, attack plan), a per-batter table, pitch-type breakdowns (All / LH / RH), and export to PDF or CSV. A batter report focuses the same metrics on one named hitter—how to attack that person with the pitcher’s actual mix (rise, drop, fastball, change, or custom types).
Two guardrails keep the report honest:
- Pitcher-scoped history. Your Friday starter’s games vs Eastside are not mixed with a reliever’s by default. Choose the pitcher who will face the order so the attack plan matches the arsenal that will be on the rubber.
- Sample-size badges. Adequate, Thin, or No history — roster only. Thin samples get a short, cautious note. Roster-only reports do not invent tendencies. If you have not scored named batters yet, the report will not pretend you have.
Scouting is pre-game guidance. It does not replace mid-game or post-game reports for today’s outing. Scout from history, then chart live. If the count leverage changes, open Pitch Call Analysis. If contact is clustering, check spray charts. The scouting sheet is the plan; the live log is the truth.
A practical workflow for coaches
Here is a repeatable way to get value from opposing roster stats and scouting reports without adding a second job in the dugout:
Before the season (or the next tournament): Build rosters for the teams you know you will see. Name, jersey, stance. Import CSV if an opponent list already lives in a spreadsheet. Practice the flow on the sample Eastside Eagles / Valley Vipers rosters if you want a dry run with named-batter demo games.
Game day: Attach {Team} - Roster when you start or schedule the game. Log pitch type, location, outcome, and the named hitter who is actually in the box. Use Add Batter or Pinch Hitter / Replacement when the order changes. Confirm new players onto the saved roster so next week’s list is already current.
Right after the game: Open the roster card or the team scouting view and scan the per-batter lines. Who was unsuccessful for average vs this pitcher? Who walked? Who did damage on extra-base hits? That is the post-game conversation with your pitch caller—specific names, not “their lineup was tough.”
Before the rematch: Generate a Team scouting report for the pitcher who will start. Read the attack plan, then tap any batter with enough pitches for an individual report. Export PDF for staff. Pair it with first-pitch strike and WHIFF% habits you already track, so the plan is both who to attack and how your pitcher gets ahead.
During the rematch: Trust the plan until the live log disagrees. A hitter who was unsuccessful last time can still barrel a mistake. Named history is an edge, not a script.
What you gain by using both together
Opposing Rosters without scouting is a better lineup card. Scouting without named rosters is an AI summary of anonymous Batter #s. Together they close the loop:
- Faster game setup — reuse the opponent list; stop retyping the same hitters.
- Cleaner live charting — the person in the box is the person on the pitch.
- Compounding stats — BAA, SLG%, K, and BB attach to real identities across rematches.
- Honest pre-game plans — attack plans grounded in your pitcher’s log, with thin samples labeled as thin.
- Shareable staff tools — CSV/PDF for the roster; branded PDF/CSV for the scouting report.
The programs that get the most from this are not the ones with the biggest analytics staff. They are the ones who log every pitch with a name on it, then actually open the scouting report the night before they see that order again.
That is the difference between remembering how a game felt and knowing how that lineup has hit you.
Pitch MetRx is a pitching analytics platform for baseball and softball coaches. Save opposing rosters, score named lineups from the dugout, and generate AI scouting reports from your pitcher’s real history—without radar hardware or spreadsheet reconstruction.
Ready to scout your next opponent from real pitch data? Start your free trial today.