Scout Aid Pro
Midfielder · capture sheet

Subject & coverage

One match shows form. Three show patterns. Minutes on and off drive every per-90 figure — get them right. A midfielder’s record is written as much by his team as by him. Count how often he showed for it and the ball went somewhere else.

Match one

Match two

Match three

00:00
0′15′30′45′60′75′90′

Rubric

Your overall read across the coverage, 1–5. Judgement, not arithmetic.

Voice capture

Watch him and talk. Every phrase is stamped with the clock and kept as your own words — the transcript is the evidence. The obvious actions are lifted out of your speech and dropped into the log for you.

How to commentate on one player — the protocol (tap to open)
1 · Open with orientation. Before kick-off, say the kit colours, which way he is playing, and his shirt number. Every recording, every time.
2 · Scout him, don't commentate the match. Ball-by-ball narration of the game yields almost nothing. Watch a passage, then say what it told you about him. Stay quiet when he isn't the story.
3 · Say the outcome, not just the action. This is the whole thing. The tool only logs an action when you name what happened to it — won or lost, found or not found, kept or given away. Say the outcome and it goes in the log; leave it out and the line is kept as evidence but nothing is counted.
4 · What this sheet is listening for. Say whether they found him. "Shows for it — they go long over his head" is the finding; "shows for it, found" is the reward. Same for the pass into space: was it attacked, or did nobody go?
5 · Flag repeats aloud. "That's the second time", "again", "every time". A repeat spoken out loud is the strongest evidence this report can carry, and the report is told to weight it that way.
6 · Speak the minute on the big moments. Goals, errors, the moment that decides the report: say "43rd minute" and the clock snaps to it. Everything else is stamped for you.
7 · Fixing mistakes. Say "scratch that" to bin the last thing you said, along with anything it logged. Say "flag this" to mark a moment for yourself.
Anything the tool picks out is marked provisional. It sits in the log with a ⚡ and one tap deletes it. The report is instructed to check every one against your actual words and to throw out any it can't support.
00:00
Mic off. Best in Chrome — the live transcription runs through the browser.

What you said

Tap any line to bin it, tap again to restore. Binned lines never reach the report.

Heard & logged — provisional

Actions the tool lifted out of your speech. They are already in the event log, marked ⚡. Delete any mishear now — these feed the rates.

Tap while you talk

Say anything — every line you speak is kept word for word and goes to the report as primary evidence, whether or not it matches an event on this sheet. Every event here can be logged by voice too; these pads are for the counts you would rather not say out loud fifty times. The mic keeps running if you switch to the Tally view. Keyboard shortcuts work on this page too.

Paste a transcript instead

Recorded in Voice Memos or anywhere else? Paste the transcript here and it lands against the match tab you have open. Lines with a spoken minute get stamped; the rest inherit the last minute heard and are reported as approximate.

Your licence key comes from your welcome email, covers all seven tools and is held in this browser only. The AI is included in your plan — there is nothing else to set up. Every line below is editable — click it and type.

How to use this tool

A midfielder sheet that turns you watching a player — talking, or tapping, or both — into a full scouting report. Read this once; you'll have it after a match or two.

The idea in three lines

  1. You watch one player, and log what he does. One sheet, three roles. An 8 is a 6 out of possession and a 10 in transition, so forcing three separate sheets would be a fiction. Pick the role on Setup — it filters which pads show, and never touches the data. A DM tally and a 10 tally are directly comparable.
  2. It writes the report. From your tally, your voice capture and your 1–5 ratings, it drafts the verdict, the strengths, the limitations, the coach's notes and the key moments.
  3. You always have the final word. Nothing leaves the tool until you have read every line and confirmed it. The tool drafts; you decide.

Step 1 — Setup

Who you are watching, and how much of him you have seen.

The player: name, club, date of birth, height, foot, shirt number. Age matters more than it looks — the report grades an under-21 on trajectory and a 28-year-old on how his game will age, and it will not do either without a date of birth.

Report for: a club coach gets a development priority; a recruiter gets Sign / Pursue / Monitor / Watch again / Pass, plus an A–E grade.

Coverage: one match, two or three. One match shows form. Three show patterns, and the report weights recurrence far more heavily than any single event. Minutes on and off drive every per-90 figure — get them right or the rates lie.

Step 2 — Tally

Watch, pause, log, resume. Minute precision is all that matters.

Tap a pad or press the letter on it. Every entry takes the clock. The clock has nudges (−1m, −10s, +10s, +1m) and a Set box, so you can keep it lined up with your video.

Showed for it — found against showed for it — bypassed is the signature pair. Pass into space — attacked against not attacked is its mirror at the other end. Late runs into the box and press triggers split the same way.

Line-breaking passes and key passes fire a two-tap tray: how many opponents that pass took out, and how many of those were defenders. That rolls into a packing figure the report frames as packing on decisive passes only — an IMPECT-style number for a league IMPECT does not cover.

Modifiers arm before the event, not after. The phase tags (PEN / FK / CK) and PRESSED attach to the next pad you press. Tap the tag first, then the pad — they clear straight after, deliberately, so a stale modifier can never silently mis-tag something later.

The "why" tray. Some pads open a strip along the bottom asking what the team did around the action. This is the most valuable thing in the sheet: it is how the report tells "left isolated, no cover" from "his touch, his fault". The report treats your answer as eyewitness cause and is forbidden from overriding it with an inference from the counts. Skip it when you are not sure — a blank is honest, a guess is not.

Keyboard shortcuts always fire, even for pads your role hides. A DM can still log a goal with 8. Tap ALL PADS to reveal everything.

The number the report is built around

Found when he showed — how often the team actually used him when he made himself available. Second headline: passes into space attacked — how often anyone ran onto the ball he played.

It sits on a blue chip at the top of the report and it is stated in the verdict. It only works if you log the pairs below honestly, including the ones that make his team look bad.

Step 3 — Voice

Watch him and talk. No keyboard.

Open the Voice tab, tap Start voice capture, mute the match audio and commentate. Every phrase is stamped with the clock and kept as your own words. Best in Chrome — the transcription runs through the browser. Recorded elsewhere? Paste the transcript into the box at the bottom instead; it works the same.

The transcript is the evidence. The report is told plainly that your spoken words outrank every counted number in the brief, and that where the two disagree, your words win. Every phrase is attached to the actions logged at that minute — a sentence spoken while you tap is what the report uses to describe that action.

Say the outcome, or nothing is logged. This is the one rule that matters. The tool only turns speech into a logged action when you name what happened to it. On this sheet:
"Shows for it, they go long over his head." "Shows for it, found, turns out." "Plays it into space, nobody attacks it." "Out of position there, left the hole."
Say the action without the outcome and the line is still kept as evidence — it just is not counted. That is deliberate: a phantom count is a false finding in a paid report, whereas a missed one is a shrug.

The report can only describe what you give it. Commentate an action, or answer its tray, and the report describes it exactly. Give it nothing and it stays a bare count — the report is not allowed to fill the gap. Your voice and the trays are the two levers you have over report quality.

Anything the tool picks out is marked provisional with a ⚡ in the event log, and one tap on the Voice tab deletes it. The report is instructed to check every one against your actual words and throw out any it cannot support.

Say "again" or "that's the second time" out loud. A repeat you name while watching is the strongest single piece of evidence the report can carry, and it is told to weight it above any total.

Fixing things: say "scratch that" to bin the last thing you said along with anything it logged. Say "flag this" to mark a moment for yourself. Tap any line to bin it, tap again to restore.

Talk and tap at once. The mic keeps running when you switch tabs, and the sheet's main pads are repeated on the Voice page. Keyboard shortcuts work there too. Let your voice carry the reads and the moments; use the pads for the counts you would rather not say out loud fifty times.

Step 4 — Your ratings and your notes

Under the pads, score him 1–5 on each attribute, anchored to the standard of the league you cover (3 = holds his own at that level). Leave anything you did not see at zero — zero means unscored and the report respects it. Never guess to fill a row.

The AI drafts scores you have not set and marks them as drafts; anything you set by hand is never overwritten.

Scout's notes take everything the pads cannot: conditions, opposition quality, the shape around him. It feeds the report and is never shown to the client, so be candid.

The honesty check — "Bypassed, or not there to find?"

If you log him being bypassed and log Out of position — left the hole, those cannot both be fully true. A player cannot be bypassed in a position he was not in.

This exists because an unseen sheet is an alibi machine unless something stops it. A report that only ever blames the team is flattery, and a sceptical recruiter will bin everything around it. The flag appears on the Report tab; your answer decides what the report says.

Step 5 — Generate and review

The report drafts everything; you edit it in place.

Go to the Report tab. Work through the pattern flags first — the data spots a pattern, you supply the cause. A flag you confirm becomes a coach's note with your explanation as the stated cause; a flag you dismiss is never used. The notes are far stronger with your reads attached.

Then enter your licence key and tap Generate analysis. The licence key comes from your welcome email and covers all seven tools. The AI is included — there is no other account to set up and no charge per report. Export capture data saves your event log, rates and notes as JSON for your own records.

Everything on the page is editable — click any line and rewrite it. When it is right, tick Confirm reviewed at the top, then Print / PDF. It will warn you if you try to print something you have not confirmed.

Worth knowing

Nothing is lost. The sheet saves to this browser after every action. Save sheet to file on Setup writes a JSON you can reload anywhere.

Capture never needs a licence or a connection. Tallying, voice capture, autosave, export and print all work offline and with no key at all. Only generating a report reaches the network. If a licence ever fails, your capture is safe — the tool will say so.

Tally two players in the same match and the records either corroborate each other or disagree. When a midfielder logs "played it, nobody ran" and a striker logs "ran, nobody played it", that disagreement is the finding, and no platform on earth can tell a coach that.