Player development plan template (PDP) for racket coaches

Most coaches carry a development plan for each player in their head. They know the kid needs a better backhand and more bottle in tight games. The trouble is that a plan in your head cannot be reviewed, cannot be shared with a parent, and quietly changes shape every week.

A written player development plan (PDP) fixes that. It is one page that says where the player is, what you are working on, and how you will know it worked. Here is what goes in it, and a template you can lift straight away.

Start from an honest current level

A development plan is only as good as the picture it starts from. “He’s decent for his age” is not a starting point you can build on.

Score the player on a framework first. If you assess on anchored levels, your starting point is concrete: backhand clear at level 4, defence at level 5, mental level 3. Now the plan has somewhere to begin and something to measure against later. Without that baseline you are guessing, and you will not be able to prove progress at the end.

Pick two or three priorities, not eight

The fastest way to write a useless plan is to list everything the player does badly. Pick the two or three things that will move them most. Usually those are the weakest pillars from the assessment, the ones holding the rest of their game back.

Everything else waits. A player can genuinely work on three things at once. Try to fix eight and you fix nothing, and the player feels like they are always failing.

Set process goals and outcome goals

Each priority needs a goal, and the strongest plans pair two kinds.

An outcome goal names the result: “reach level 6 on the backhand clear by Easter.” It gives the work direction.

A process goal names the behaviour that gets there: “racket up early on every clear, three focused reps blocks a week.” It is the part the player actually controls. A junior cannot will themselves to level 6, but they can absolutely control whether their racket is up early. Track the process and the outcome tends to follow.

Put a timeline and a review date on it

A plan with no date is a wish. Give each priority a realistic horizon (a block, a term, a season) and book the review now. The review is non-negotiable: it is where you reassess, check the goals, and decide what comes next.

Most racket programmes run on six to twelve week blocks, which is a sensible review cadence. Long enough to see real change, short enough that the plan does not drift.

Decide what parents can see

A PDP is also a communication tool. Parents who can see the plan stop asking “what are you actually working on?” and start reinforcing it at home.

Decide up front what is shared. Usually the priorities, the goals and the progress are worth sharing; your private coaching notes are not. Keep the player and parent view to what helps, and keep safeguarding tight: approved parent links only, and nothing visible that you have not chosen to share.

A template you can copy

Use this as your one-page PDP skeleton. One per player, reviewed each block.

• Player and squad: name, age group, the squad or 1-2-1 they sit in
• Current level (from assessment): the score on each pillar, dated
• Priority 1: the weakest pillar, with an outcome goal and a process goal
• Priority 2: the next weakest, same structure
• Priority 3 (optional): one more, only if the first two are well underway
• Timeline: the horizon for each priority (block, term, season)
• Review date: when you reassess and rewrite this plan
• Shared with parents: what the player and parent can see, and what stays private

Keep it to a page. If a parent cannot read it in a minute and a player cannot name their own priorities, it is too long.

Reassessment closes the loop

The plan is not finished when you write it. It is finished when you reassess and see whether it worked.

At the review, score the player on the same framework. Put then-and-now on one radar and the change is obvious: the backhand clear moved from 4 to 6, defence held, the mental side crept up a level. That is the proof a plan in your head can never give you. Where a priority has landed, retire it and promote the next weakness. Where it has not, ask why before you simply roll it over.

That loop, assess, plan, work, reassess, is what separates a player who is busy from a player who is visibly getting better. The development plan is just the page that holds the loop together.