IDP generator, by Resume Worded ★4.9 on Trustpilot · 5M+ job seekers

Make the individual development plan actually yours

An individual development plan is the version of career planning your employer writes down: a grid of goals, actions, support, timelines, and measures, usually attached to the review cycle, often started because a manager asked. None of that stops it from working for you. Answer four questions and get the grid filled in properly, then use this page to make it worth the meeting.

Build my IDP »

Four questions, the classic five-column grid. Free, no account needed.

Individual development plan · review cycle

Goal

Actions

Support needed

Timeline

Measure

Own the Q4 model for one business unit

Rebuild last quarter's model from a blank sheet

2 hrs/month of the senior analyst's time

By Q4

Model ships under my name

Present variance story to the director, solo

Write the one-page narrative monthly

A 15-min feedback slot after each

September

Solo, and the questions get answered

your third goal

Five columns. The one your manager can actually act on is Support needed.

Interactive, answer four questions

Build your IDP grid

Tell it your role, where the IDP sits in your review cycle, and whether goals are already agreed with your manager. It returns three goals in the classic grid: each with actions, the support to ask for (written so it can be approved or declined in the meeting, not nodded at), a timeline a reviewer can hold you to, and a measure a stranger could verify.

What an IDP is

The IDP is the formal cousin of the development plan

An individual development plan does the same job as any professional development plan: it names growth areas and commits actions to them. The difference is that it lives inside a process. It usually exists because a manager, an HR cycle, or a funding requirement asked for it; federal agencies, universities, and research programs mandate them outright. It gets co-signed, revisited at reviews, and filed. None of that is bad. It changes one thing that matters: the document has two readers, and the second reader controls budget and assignments.

Writing for two readers is a skill. Goals have to be legible to someone who will approve resources against them, which rules out both corporate wallpaper ("improve communication skills") and private shorthand. The classic grid earns its place because it forces that legibility: every goal carries its actions, the support it needs from the company, a timeline a reviewer can hold you to, and a measure a stranger could verify.

The grid is not bureaucracy for its own sake. It is the format that lets a second reader say yes to something.

Two rules keep a mandated IDP from becoming pure paperwork. First, draft it before the meeting, not in it: whoever writes the first draft owns the frame, and managers approve edits far more readily than they invent goals for you. Second, put one goal in the grid that you actually want, funded by the process: pair the company's goal for you with your goal for you and let one document carry both. And if nobody is making you write anything, you may not want this format at all; the freer personal version is our professional development plan generator, same method without the co-signature.

The conversation

Bring a draft, leave with commitments

The IDP meeting goes one of two ways. Arrive empty-handed and you will leave with your manager's guesses about your ambitions, phrased as goals. Arrive with a drafted grid and the meeting becomes an edit, which is faster for them and better for you.

The column that decides whether the plan becomes real is Support needed, because it is the only cell your manager can act on directly. Vague support ("mentorship", "more exposure") gets a sympathetic nod and no follow-up, because there is nothing to approve. Specific support gets decisions: a named course with a price, two hours a month of a named senior person's time, a seat on the Q3 project, conference budget with the conference named. Write asks that can be approved or declined in the meeting. Either answer moves you forward, and a declined ask with a reason is worth more than an approved vagueness.

A support ask is well written when the meeting can end with a yes or a no. Sympathy is not a resource.

Close the meeting by converting review-cycle language into calendar language: which of these actions starts this month, and when do we look at this grid again. One 30-minute mid-cycle check against the Measure column is enough. And if your manager is the one who asked for the IDP, this same meeting quietly builds your leverage: an agreed grid with an approved support column is the paper trail that promotion cases get argued from later.

Worked example

A filled grid, end to end

One real run of the generator, inputs included. Read the Support needed column closely: every ask has a price, a name, or a date, which is what makes this grid a working document instead of review-week paperwork.

Inputs: Financial analyst, manufacturing · annual review coming, drafting first · goals roughly agreed · growth areas: modeling depth, executive communication

Goal

Actions

Support needed

Timeline

Measure

Own the three-statement model for one business unit by Q4.

Take the named FP&A modeling course; rebuild last quarter's model from a blank sheet; shadow the senior analyst through one close.

Course budget, $450; two hours per month of the senior analyst's time; read access to the unit's driver data.

Course by end of Q2; blank-sheet rebuild in Q3; own the Q4 cycle.

The Q4 model ships under my name and survives review with fewer than five material corrections.

Present the monthly variance story to the finance director, solo, by September.

Write the one-page narrative each month; present twice with my manager present, then alone; collect 15 minutes of feedback after each.

A recurring 15-minute feedback slot with my manager; the September slot on the director's calendar.

Monthly from May; first solo presentation in September.

The September presentation happens without my manager in the room, and the director's questions get answered in the room.

Understand the sales pipeline well enough to challenge the forecast.

Sit in on four pipeline reviews; build the bridge document between CRM stages and revenue recognition.

A standing invitation to pipeline reviews, agreed with the sales director.

Reviews across Q2 and Q3; bridge document by August.

One forecast assumption changes because of a question I asked.

Frequently asked questions

What is an individual development plan?

An individual development plan (IDP) is a structured document, usually a grid, that maps an employee's growth goals to actions, the support the employer will provide, timelines, and measures of progress. It is typically written as a partnership between you and your manager and revisited during the review cycle. Federal agencies, universities, and many research programs require them; plenty of companies use them voluntarily as the development half of performance conversations.

What should an individual development plan include?

The classic grid has five columns and they earn their places. Goal: what will be true, written so a stranger could verify it. Actions: the two or three concrete steps that get there. Support needed: what you are asking the company for, specific enough to approve or decline. Timeline: dates a reviewer can hold you to. Measure: the evidence. Two or three goal rows is the right size; ten-row IDPs are how the document stops being read.

How do I write an individual development plan for work?

Draft it before you meet your manager, not during: whoever writes the first draft owns the frame. Pick two or three goals, ideally pairing what the company wants from you with one thing you genuinely want for yourself. Fill all five columns, and spend the most care on Support needed, phrasing each ask so it can be approved in the meeting. The generator on this page produces a working draft from four answers.

What is the difference between an IDP and a performance review?

Direction. A performance review looks backward and evaluates what you did; an IDP looks forward and plans what you will grow into. They meet in the same conversation, and a good review feeds the IDP, but they should not grade each other: an IDP goal you attempted and missed is development working as intended, not a performance failure. If your company scores IDP completion as a performance metric, keep the stretch goals in your personal plan instead.

What should I put in the support needed section of an IDP?

Asks your manager can act on: a named course with its price, scheduled time with a named senior person, a seat on a specific project, conference budget with the conference named, read access to specific data or meetings. Avoid unactionable nouns like mentorship or exposure; they get nodded at and forgotten because there is nothing to approve. The test: could the meeting end with a yes or a no to each line? Both answers are useful.

What is the difference between an individual development plan and a professional development plan?

Same method, different ownership. A professional development plan is the personal version: you write it, you review it, nobody co-signs it. An IDP is the formal version: requested by a process, tied to the review cycle, and written for two readers, which is why its goals and support asks have to be legible to someone who controls budget. If nobody is requiring a form, start with our professional development plan generator instead.

The grid is filled. Is it pointed anywhere?

An IDP can be immaculate and still be someone else's plan for you. Coached reads your career from just your LinkedIn profile, free: your strengths, values, and work style, and whether the goals on this grid actually match them.

Get your free career read »

Resume Worded

Score My Resume

Targeted Resume

LinkedIn Review

Get Resume Worded Pro