The prompt
Score 10 of 10, Excellent
Use it when You are starting or rebuilding an internship program and want projects worth doing, mentors who know their part and a fair way to decide on job offers at the end.
- {{organization}}
- {{owner}}
- {{decisions}}
- {{project_ideas}}
- {{mentors}}
- {{budget}}
- {{conversion_goal}}
Full prompt and why it works
Prompt
Plan an internship program for {{organization}}, for {{owner}} to take to the managers who will host interns, so that every intern has real work to learn from and a mentor with time set aside, and so that offers at the end follow a fair, written process. What we have decided so far (number of interns, dates, pay, hours, who the program is for): """ {{decisions}} """ Project ideas from the teams: """ {{project_ideas}} """ Mentors who have volunteered, and how much time they can give: {{mentors}} Budget beyond pay, if any: {{budget}} How we hope to hire from the program: {{conversion_goal}} Use these headings: 1. Program at a glance: dates, number of interns, pay and hours exactly as decided, and who it is for. 2. Projects: a table with the columns Project, Team, What the intern delivers, What they learn, Mentor. Keep a project only if an intern can finish a useful piece of it in the time and it teaches something; list the ideas you dropped and why. 3. The mentor's part: what a mentor does each week, how much time it takes, and what they are not expected to do. 4. Schedule: week by week, as a table, from first-day setup to final presentations. 5. Evaluation: a midpoint check and a final review, with the same criteria for every intern, written as things a mentor can observe. 6. From intern to hire: who decides on offers, on what evidence and by when, and what interns are told about it on day one. 7. Risks and open decisions. Keep it under 900 words, apart from the tables. A good plan gives each intern one project they can explain to a stranger at the end, for example "I rebuilt the returns report so the warehouse team sees damaged items every day." That example shows the form only. Do not set projects that replace a paid employee's normal work or have no learning in them. Rules on intern pay, hours, school credit and work permits differ by country and state, so state pay and hours only as decided above, add [CHECK WITH HR OR COUNSEL] beside each, and do not say whether an unpaid internship is allowed anywhere. Evaluation and offers rest on the written criteria only, never on age, background or any protected characteristic. If a decision the plan needs is missing, such as pay or the end date, write [DECISION NEEDED: what] rather than choosing one.
Variables
- {{organization}}
- Your organization, for example "a 200-person software company".
- {{owner}}
- Who runs the program, for example "the HR business partner for engineering".
- {{decisions}}
- What is decided: how many interns, dates, pay, hours, who it is for (students, career changers, graduates).
- {{project_ideas}}
- Project ideas from the teams, one per line, with the team that offered each.
- {{mentors}}
- Who has volunteered to mentor and the time each can give.
- {{budget}}
- Money available beyond pay, for events, equipment or travel, or "none".
- {{conversion_goal}}
- What you hope for, for example "offer roles to two or three interns for next year's graduate intake".
Why it works
- What to avoid. Projects that replace paid work are ruled out, and pay and hours appear only as decided, with each one marked for HR or counsel to check.
- What good looks like. Each intern should leave with one project they can explain to a stranger, which keeps weak project ideas off the list.
- If unsure. A missing decision such as pay or the end date becomes a [DECISION NEEDED] marker instead of a figure the model picked.