By ScoutMyTool Editorial Team · Last updated: 2026-05-27
Introduction
I coach a small group of junior players and I have settled on PDF as the right format for two reasons: it prints clean and it reads the same on a tablet at the board as on a laptop at home. Each week I push out a themed puzzle sheet (mating nets, knight forks, endgame studies) and after every tournament I send an analysis PDF for each student’s games. The layouts that worked, the diagram tooling, and what students actually engaged with are below.
Vocabulary, quickly
| Term | Meaning |
|---|---|
| FEN | Forsyth-Edwards Notation — text encoding of a board position |
| PGN | Portable Game Notation — text encoding of a full game |
| Diagram | Rendered board position from a FEN, embedded in the PDF |
| Annotation | Coach's comment on a move — ! / !? / ? / ?? |
| Variation | Alternative line shown after a played move |
| Puzzle theme | Tactical motif the sheet is built around (fork, skewer, etc.) |
| Endgame study | Composed position with a forced winning or drawing line |
Step by step
- Pick a theme for the puzzle sheet. One motif per sheet — mating nets, pins, skewers. Mixing themes weakens the learning.
- Pull 6–8 positions from your puzzle database. Mix difficulty: two easy warm-ups, three medium, one or two hard finishers. Same theme throughout.
- Render each FEN as a board diagram image. Use a diagram tool that exports SVG or PNG; embed in the PDF at a consistent size.
- Number puzzles and leave space for solutions. Solutions on the back page or a separate solutions PDF. Don't print them next to the puzzle.
- Annotate tournament games into a PDF. For each game: opening summary, critical moments, top engine moves, your coaching note in plain language.
- Use diagram-after-critical-move pattern. Embed the board diagram at the moment you want the student to pause and think. One diagram per critical moment.
- Keep variations to two-deep. A single main line with one alternative is what students absorb. Three or four nested variations and the student gives up.
- Send PDF + the PGN file together. PDF for reading, PGN so the student can replay the game in a chess app and explore.
Practical checklist before you send
- Render board diagrams as SVG embedded in the PDF rather than rasterized PNG — SVG holds resolution at any print or screen size and the file stays small.
- Cap variations at two-deep in the main analysis; nested variations past two levels are the single biggest reason students stop reading at the third diagram.
- Print solutions on a separate page or in a companion PDF — visible solutions defeat the purpose of the puzzle and the student does not engage.
- Mix difficulty within a sheet (two easy / three medium / two hard) but keep the THEME single; cross-theme sheets test recall, single-theme sheets build pattern recognition.
- Send the PGN alongside the PDF so students can replay games in a chess app and explore lines you did not annotate.
- Version puzzle sheets by rating band rather than by week; a 1200-rated student should not see 1800-rated puzzles even if the theme matches.
- Keep the master puzzle database in PGN or a chess-tool format; the PDF sheets are derived outputs and should be regenerable on demand.
Related reading and tools
FAQ
- How do I render board diagrams from FEN into a PDF?
- Use a diagram tool that takes a FEN string and exports an SVG or PNG of the board (open-source options include python-chess for SVG export and several browser-based renderers). Embed the resulting image in the PDF at a consistent size — usually about 5 cm square for puzzle sheets, larger for analysis. SVG embeds at infinite resolution; PNG is fine if you generate it at 300 DPI.
- How many puzzles per sheet?
- Six to eight is the sweet spot for one practice session. Less than six and the sheet feels light; more than eight and engagement drops by puzzle five. Mix difficulty: two easy to build momentum, three medium to test the theme, one or two hard finishers to stretch. Use the same theme throughout one sheet — mixing themes within a sheet teaches less than focusing on one motif.
- Should I print solutions on the same sheet?
- No. Print solutions on a separate page (back side or separate file). Students who can see the solution as they look at the puzzle do not actually solve it — they pattern-match to the solution. Solutions on the back, or in a solutions PDF you send separately, forces the engagement.
- How long should a game-analysis PDF be?
- Two pages for a 30-move game, four for a complex middlegame, six maximum. The temptation to annotate every move is the enemy of getting read. Pick the 3–5 critical moments, diagram them, give your coaching note, and let the rest of the moves stand without comment. Students re-read short PDFs; long ones get scrolled past.
- What about engine evaluations — should I include them?
- Selectively. Use them to anchor critical moments ("here, white is +1.5 and the natural move drops to -0.8"), not to score every move. Quoting an evaluation on every move trains students to defer to the engine instead of learning the underlying patterns. The coach's plain-language note is what they remember; the engine number is the receipt.
- How do I version puzzle sheets across cohorts of different ratings?
- Build one master PDF with a theme and four difficulty bands (sub-1000, 1000–1400, 1400–1800, 1800+). Save four variants — same layout, different puzzles. Filename pattern: theme-pin-1200.pdf, theme-pin-1500.pdf. Predictable naming makes the weekly send a copy-paste, and the master template lets you swap puzzles without rebuilding the layout.
Citations
- Wikipedia — “Forsyth-Edwards Notation — board-position encoding.” en.wikipedia.org/wiki/Forsyth%E2%80%93Edwards_Notation
- Wikipedia — “Portable Game Notation — game encoding format.” en.wikipedia.org/wiki/Portable_Game_Notation
Ship a clean coach PDF every week
Pull a term of puzzle sheets and analysis PDFs into one workbook, in browser, no upload.
Merge a puzzle workbook →