Midseason Pitching Evaluation Checklist: What to Keep, Change or Stop

A midseason review should answer three questions: Is the pitcher recovering well? What has improved? What needs to change before the next stretch of games? Wins and radar readings cannot answer all three.

Use this checklist with the pitcher, coach and—for youth players—a parent or guardian. It is a coaching review, not a medical screening or clearance to throw.

Set up the review without adding throws

Gather the season pitch log, upcoming schedule, available game video and notes from early in the season. A practical starting point is to compare the most recent three outings with three earlier outings. That is a manageable review sample, not a validated testing protocol.

Record the pitcher’s age, pitching distance, teams, usual role and any recent schedule changes. Note differences in competition and conditions before comparing results. If early-season records are missing, establish a baseline now rather than guessing at improvement.

Complete the review from existing records first. Any later throwing observation should fit an already-planned session, respect required rest and happen only when the pitcher is well enough to throw.

1. Check pain and recovery first

• [ ] Ask the pitcher directly: “Any elbow or shoulder pain during throwing, afterward or today?”
• [ ] Record fatigue, stiffness or soreness after each outing and whether it remains before the next planned session.
• [ ] Ask whether the arm feels ready normally, or whether the pitcher increasingly needs to “work through” discomfort.

Decision: Elbow or shoulder pain is not a mechanics problem to troubleshoot with more pitches. ASMI recommends discontinuing pitching until a sports-medicine physician evaluates an adolescent pitcher reporting that pain. It also recommends rest from pitching and other throwing when a pitcher reports or shows fatigue. See ASMI’s adolescent pitching statement, updated April 2013.

A completed rest interval does not override pain or fatigue.

2. Audit workload across the whole schedule

• [ ] Combine game pitch counts from every team, tournament and showcase into one log.
• [ ] Check daily limits and rest intervals against the pitcher’s age band and applicable competition rules.
• [ ] List bullpens, lessons, warm-up throwing, long toss and throwing at other positions separately. Do not treat them as invisible workload—or add them to the game count as though the official table measures all throws.
• [ ] Look ahead for overlapping team commitments and crowded tournament weekends.
• [ ] Review accumulated innings and whether the calendar still leaves room for the age-appropriate annual throwing break. Use Pitch Smart’s age-specific recommendations, linked from its guidelines page, to check both.

As of November 2026, MLB Pitch Smart recommends a daily game maximum of 85 pitches for ages 11–12 and 95 for ages 13–16, but rest thresholds differ by age. For example, a 12-year-old throwing 60 game pitches falls in the three-day-rest band. These are limits, not targets; check the full age-based pitch-count and rest table.

Decision: Resolve schedule conflicts before adding development work. Pitch Smart’s guidelines specifically call for families to account for participation across organizations, not just one team’s records.

3. Separate control from command

Control means throwing strikes. Command, for this review, means placing the ball near the intended target.

• [ ] Compare strikes divided by total pitches and first-pitch strikes divided by batters faced.
• [ ] Review walks alongside batters faced rather than comparing raw walk totals from different-length outings.
• [ ] Where video shows the intended target, note common misses: high, low, arm side or glove side.
• [ ] Review fastballs and changeups separately so improvement in one does not hide difficulty with the other.

Decision: Choose one observable priority, such as reducing high fastball misses. If you cannot see the target, do not label every strike as good command. Avoid declaring progress or regression from one outing.

4. Compare delivery repeatability

• [ ] Compare existing clips from similar camera angles and the same delivery: windup with windup, stretch with stretch.
• [ ] Watch setup, balance, stride direction and finish—not whether the pitcher resembles a professional.
• [ ] Compare early and later pitches in an outing. Note when delivery changes coincide with worsening location or reported tiredness.

ASMI lists declining velocity, declining accuracy and delivery changes among possible fatigue signs. They are reasons to check the pitcher and respond, not proof of a particular mechanical fault. ASMI guidance

Decision: Have the coach select one cue, rather than rebuilding the delivery midseason. Use the pitching mechanics checkpoints to organize video observations; video alone cannot establish injury risk.

5. Treat velocity as optional context

• [ ] If readings already exist, compare the same pitch type, device and measurement setup, including typical readings rather than only the fastest pitch.
• [ ] Note whether any drop coincides with fatigue, discomfort or poorer location.
• [ ] Leave this item blank if there are no comparable readings. Do not add a maximum-effort test to complete the checklist.

ASMI’s adolescent guidance advises avoiding radar guns. A youth midseason evaluation does not need one. Decision: Do not make “throw harder” the automatic response to stalled progress.

6. Ask about confidence and routine

• [ ] Ask: “Which pitch can you trust? What gets difficult? What helps after a miss?”
• [ ] Review whether the pitcher follows a familiar warm-up and between-pitch routine.
• [ ] Check whether the player feels comfortable reporting tiredness and still enjoys pitching.

Decision: Write down one routine to keep and one coaching support to provide. Describe behavior—“returns to the target after a walk”—rather than assigning a toughness label.

Finish with a short action record

For each area, mark keep, adjust, refer or unknown, and attach one supporting observation. Do not average these into a score: better command cannot cancel out arm pain.

Address every health or workload concern first. Then leave the meeting with:

• One thing to keep: a pitch, cue or routine that is working.
• One development priority: a specific command task or coaching cue, with a named adult responsible for follow-up.
• One follow-up date: review the same measures after the next few eligible outings, or sooner if symptoms or workload concerns arise.

For example: “Keep the current setup. Track high fastball misses during scheduled work. Parent shares the combined pitch log with both coaches. Review location notes after three outings.” For turning that single development priority into useful practice, see practice makes permanent.