How to Write a Scouting Report That a Front Office Will Read

Most advice about scouting reports is about what to put in them. That is the easier half. The harder half is that somebody has to read the thing, and that person is not reading it the way you wrote it.

Picture the actual reader. A cross-checker in late May with forty reports in the queue, deciding where to spend eight days of travel he cannot get back. He is not evaluating your prose. He is scanning for a reason to get on a plane, and if he cannot find one in about ninety seconds, your player does not get seen. Not because the report was wrong — because it did not survive triage.

Everything below follows from that.

Lead with the conclusion

The single most common structural mistake is building to the verdict. The scout walks the reader through the frame, then the swing, then the approach, then the tools, and arrives at the recommendation in the last paragraph, the way you would tell the story out loud.

Invert it. Open with what you think and why, in two or three sentences. Then spend the rest of the report supporting it.

Weak opening. “Saw him three times this spring. Athletic build, room to fill out. Good bat speed. Struggled some against better arms.”

Strong opening. “Follow. Everyday corner outfielder if the hit tool plays — 45/55 hit, 50/60 power on a frame with real strength projection left. The swing works. The question is pitch recognition against spin, and I have not seen him get a steady diet of it yet.”

The second version can be read in eight seconds and acted on. The first requires the reader to assemble your conclusion himself, and he will not do that forty times.

This is also a discipline for the writer, not just a courtesy to the reader. If you cannot state the conclusion in three sentences, you probably have not reached one yet, and the report you are about to write is a set of notes wearing a report’s clothing.

The header is not a formality

Every report needs a block of context before the evaluation, and every field in it exists because somebody downstream got burned without it.

Player identification — name, position, school or club, class or graduation year, date of birth, bats/throws, height and weight
Dates seen and where — every look, not just the best one
Number of looks — a two-look opinion and a nine-look opinion are different claims
Opponent and level — who he did it against
Conditions — wind, temperature, mound quality, gun used and where you sat

That last item gets skipped and should not be. Radar readings vary by device and position; a report that says 94-96 without saying what gun took it is asking the reader to trust a number he cannot calibrate. The same is true for a 60 time taken on a wet track.

Number of looks is the field that changes how the whole report should be read. A scout who has seen a player once and grades him with certainty is telling on himself. A scout who has seen him seven times and says the hit tool is still an open question has said something valuable. Make the reader able to tell those apart.

Separate what you saw from what you think

This is the habit that most distinguishes a report a front office trusts from one it argues with.

An observation is a thing that happened in front of you. A judgment is your interpretation of it. Both belong in the report, and they should be visibly different, because the reader may accept your observation and reject your conclusion — and that is a productive outcome, not a failure.

Blurred. “Below-average arm, will have to move off short.”

Separated. “Arm plays 45. Throws from the hole were 78-81 with carry but he needs a crow hop to get there, and he short-armed two of them under pressure. Present feet are fine. I think it is a second base profile — but if the arm strength is a strength issue rather than a mechanical one, and he is 17, that grade could move.”

The second version gives the cross-checker something to check. When he goes to see the player, he knows exactly what to look at. The first version gives him a verdict he can only agree or disagree with.

The related discipline: when you write a number that came from a measurement, say so, and when you write a number that came from your eye, say that too. A 6.6 you ran on a stopwatch and a 55 run grade you assigned are different kinds of claim.

Specificity is the whole game

Adjectives are where reports go to die. “Good arm,” “advanced feel,” “projectable frame,” “competes” — every scout in the country has written all four this month, and none of them survive contact with a reader who has other options.

Replace the adjective with the thing you actually saw.

Instead of	Write
”Good velocity"	"92-94 first two innings, 89-91 by the fifth, T95"
"Projectable frame"	"6’3”, 175, narrow shoulders, high waist, size 14 shoe — room for 25 pounds"
"Advanced feel for the change"	"Threw it 11 times, 6 for strikes, 2 swing-and-miss, only 1 to a lefty"
"Competes"	"Gave up a three-run homer in the 3rd, came back out and threw 14 of 18 for strikes"
"Struggles with spin"	"0-for-6 with 4 swinging strikeouts against breaking balls in two looks”

Velocity that fades is a different pitcher than velocity that holds, and “good velocity” hides which one you saw. The specific version is shorter to read and carries more information, which is the rare case where being rigorous and being brief are the same act.

Say what you did not see

Silence in a report reads as absence of a problem. It usually is not — it is absence of a look.

If you never saw him throw to a runner, write that. If you never saw him against a left-handed pitcher, write that. If the two games you covered were both in 40-degree weather against a bad conference opponent, write that.

“Not observed” is a complete and respectable entry. A grade you invented to fill the field is worse than a blank, because it is indistinguishable from a grade you earned. Every organization has been burned by a report that looked complete and was not, and the scouts who write “no data provided” without embarrassment are the ones whose completed fields get believed.

Put the level on everything

A grade with no level attached is a number nobody downstream can use. A 55 arm against a weak high school schedule and a 55 arm in the Cape Cod League are different claims about the same player, and the reader cannot tell which you meant unless you say.

This connects directly to how the 20-80 scale works: the baseline is always the major leagues, never the field you are sitting at. If your report grades a player against his conference, everything above you has to translate it, and translation is where information gets lost.

State the level, state the competition quality, and contextualize the production. “Hit .412” means one thing in a strong JUCO conference and something else in a weak high school league, and the number by itself is closer to noise than to evidence.

Own the projection, including how you could be wrong

The projection is the part of the report you are actually being paid for. Anyone can describe a player. You are being asked what he becomes.

So commit to it. Then do the thing that almost no one does: write down what would change your mind.

“I have this as a 50 OFP — big league regular, second-division everyday guy. The case against is the swing gets long against velocity up, and I have seen him beaten there twice. If he shows me he can shorten up with two strikes, this is a 55 and I would push it. If the swing looks the same in June, it is a 45 and a bat-first corner profile with real risk.”

That paragraph does three things at once. It gives a grade, it tells the cross-checker exactly what to watch for, and it puts your reasoning on the record so it can be evaluated later. Scouts get better by being checkable. A report that cannot be wrong cannot teach you anything when the player’s career resolves.

On comps, and on makeup

Comparisons are the most-abused device in scouting. A good comp is mechanical and specific — similar frame, similar arm slot, similar swing path. A bad comp is an outcome, and it hijacks the entire report: name a star and every reader stops evaluating your player and starts evaluating your comp. If you use one, comp the body or the delivery, not the career.

Makeup is the hardest section to write honestly, and the one where reports most often drift from evidence into impression. Write what you observed and where it came from: what a coach told you, what you saw after a bad at-bat, how he was with teammates when things went badly. Attribute it. “His travel coach says he is the first one there” is a usable sentence. “Great makeup” is not, and it carries real weight in a draft room for something that is functionally a rumor.

Be especially careful that makeup language is describing behavior rather than background. That distinction protects the player and it protects the accuracy of your report, which are the same thing more often than people admit.

The working checklist

Before you file:

The report is the record of your judgment

The reason to write this way is not that it is tidy. It is that a scouting report is the only durable artifact of an evaluation, and your evaluations are your career.

If you were right about a player in 2021, that is worth something in 2026 — but only if the report still exists, still says what you said at the time, and can be found. A scout with nine years of specific, checkable, dated reports has a case. A scout with nine years of “good arm, competes, follow” has nine years of nothing anybody can verify, including himself.

Write for the cross-checker who has ninety seconds. Then keep it for the version of you who wants to know, four years from now, whether you actually saw it coming.