Internship Program Plan: 9-Month Timeline, Roles and Example
8 min read ยท 2026-10-25
An internship program plan lays out how you will approve, design, recruit for, run and evaluate an internship program, with dates and owners for each part. For a summer program, planning usually starts many months ahead, because projects, managers, budget approval and recruiting all need to be in place before the interns arrive.
The plan below covers nine months in six phases, built around a summer program of about ten to twelve weeks. Each phase has steps and a milestone you can check. You will also find a week-by-week example, a checklist for scoping intern projects, who owns what, the metrics to track and how to present the program to leadership. For a semester or year-round program, keep the phases and shift the dates to the academic calendar.
The roadmap at a glance
Goal: Every intern finishes a real, scoped project, presents it to leadership, gets a fair evaluation, and the company decides on return offers with clear criteria. Duration: 9 months
Make the case and get approval (Month 1)
Agree on why the company runs the program and how many interns it can support.
- Write a one-page business case: goals such as an entry-level hiring pipeline or project capacity, number of interns, teams involved and budget needs.
- Ask managers which teams have real projects and the time to mentor.
- Check pay, hours, eligibility and school credit questions with HR or legal for each location.
- Name a program lead who owns the plan from approval to return offers.
Milestone: Business case approved with intern headcount, participating teams and a named program lead.
Design the program (Months 2-3)
Have projects, mentors and a program calendar ready before recruiting starts.
- Ask each hiring manager to write a one-page project brief with the problem, deliverable, data or tools needed and success criteria.
- Assign a manager and a separate peer mentor or buddy to each intern.
- Build the program calendar: orientation, weekly one-to-ones, learning sessions, mid-point review and final presentations.
- Write an evaluation rubric and the criteria for a return offer.
Milestone: Approved project briefs for every intern slot, a named manager and mentor for each, and a published program calendar.
Recruit and select (Months 3-5)
Fill every slot with candidates who fit the projects.
- Post roles that describe the actual project, the team and the skills needed.
- Work with university career centers, student groups and job boards that reach the students you want.
- Use structured interviews with the same questions and a scorecard for every candidate.
- Make offers quickly and keep a short backup list for declined offers.
Milestone: All slots filled with signed offers, and a ranked backup list kept until the start date.
Pre-board (Months 5-6)
Make sure interns can start working on day one.
- Order laptops, accounts, badges and system access for each intern and test them before the start date.
- Send a welcome email with the first-week schedule, dress code, location or remote setup, and who to ask for help.
- Train managers and mentors: how to give feedback, how to run one-to-ones and what the rubric means.
- Confirm the first task for each intern, small enough to finish in the first week.
Milestone: Equipment and access tested for every intern, and every manager and mentor briefed.
Run the program (Months 6-8)
Keep every intern moving on their project and learning about the company.
- Hold orientation in week one and a project kickoff with each manager.
- Run weekly one-to-ones and a short weekly check-in between the program lead and all managers.
- Hold a mid-point review with written feedback and an adjusted project plan if needed.
- Run learning sessions with leaders and social events so interns meet people outside their team.
- Ask interns to present their work at the end in front of leaders and their teams.
Milestone: Mid-point reviews done for every intern, and every final presentation delivered on the scheduled day.
Evaluate, decide and improve (Month 9)
Make fair return-offer decisions and improve the program for next year.
- Collect manager evaluations against the rubric and calibrate them in one meeting.
- Extend return offers based on the criteria set in phase two, with a clear deadline to accept.
- Run an exit survey for interns and a short survey for managers and mentors.
- Write a one-page program review with results, lessons and changes for next year.
Milestone: Return-offer decisions made for every intern, survey results reviewed and next year's plan drafted.
How to scope an intern project
The project decides whether the internship works. A vague project leads to busywork, and a project that is too large leaves the intern with nothing finished to show. Ask each manager to write a one-page brief before you post the role, and review every brief yourself.
A good test: could the intern explain the problem and the result in a five-minute final presentation? If not, narrow the scope. Keep a stretch goal in the brief for interns who move fast.
- Real: it solves a problem the team actually has, and someone will use the result.
- Sized for the time: an intern can finish a first version in about two thirds of the program, leaving time to polish and present.
- Clear deliverable: a dashboard, a feature, a research report, a campaign or a process document.
- No blockers: data, tools and access can be ready before day one.
- Owned: a named manager reviews the work every week.
Example: a 10-week summer program for six interns
Picture a mid-size software company with six interns: two in engineering, one in data, one in product design, one in marketing and one in finance. The program lead is an HR business partner who gives the program part of their time.
This calendar gives the interns a fixed rhythm and gives managers clear dates to plan around. Put it in a shared calendar before the interns arrive.
- Week 1 (owner: program lead): orientation, laptop setup, meet the CEO, first small task done with the mentor. Milestone: every intern has access and a finished first task.
- Week 2 (owner: each manager): project kickoff, written plan with weekly goals. Milestone: project plan agreed.
- Weeks 3-4 (owners: managers and mentors): build the first version, weekly one-to-ones, one learning session per week. Milestone: first draft or prototype shown to the manager.
- Week 5 (owner: program lead): mid-point review with written feedback using the rubric. Milestone: review done and plan adjusted.
- Weeks 6-8 (owners: managers): finish the project, test it with real users or stakeholders. Milestone: deliverable working or report complete.
- Week 9 (owner: mentors): practice runs of final presentations. Milestone: slides reviewed.
- Week 10 (owner: program lead): final presentations to leadership, exit survey, evaluations submitted. Milestone: every intern presented and evaluated.
Who owns what
Internship programs fail quietly when everyone assumes someone else is handling the intern. Write the owners into the plan and share it with every manager.
Ask each manager to block time in their calendar for one-to-ones before the intern starts. A manager who cannot give that time should share the role with a colleague or wait for next year.
- Program lead (HR, early careers or university recruiting): the plan, calendar, rubric, events and reporting.
- Hiring managers: project brief, interviews, weekly one-to-ones, mid-point and final evaluations.
- Mentors or buddies: daily questions, first-week support and help with the final presentation.
- Recruiters: job posts, school relationships, interview scheduling and offers.
- IT and facilities: laptops, accounts, badges and desks or remote setup.
- HR, payroll and legal: pay, hours, eligibility and school credit questions.
Metrics to track
Pick a few metrics that match the goals in the business case. If the program exists to build a hiring pipeline, return offers and acceptances matter most. If it exists to add project capacity, project completion and manager satisfaction matter more.
Record the same metrics every year so you can compare programs over time.
- Offer acceptance: offers accepted against offers made, from your recruiting system.
- Project completion: share of interns who finished their deliverable, judged by managers against the brief.
- Intern experience: exit survey on project quality, mentoring, learning and whether they would recommend the program.
- Manager experience: short survey on intern quality and the time the program took.
- Return offers and acceptances: offers extended and accepted, and later, how many joined full time.
How to present the program to leadership
To get approval, keep it to one slide: the goal of the program, the number of interns by team, the projects they will work on, the manager time needed and the budget request. Leaders approve faster when they see real projects, not a general wish to have interns.
After the program, report on one slide again: projects delivered, return offers made and accepted, survey highlights and the changes for next year. Invite leaders to the final presentations. Seeing the work firsthand is the best case for running the program again.
How to adapt the plan
A small company with one or two interns can merge phases. The founder or a team lead can act as program lead, and the calendar can be a simple list of weekly check-ins plus a final demo. Keep the project brief and the mid-point review, since they matter most.
For remote interns, plan more structure, not less. Ship equipment early, schedule daily check-ins in the first week, set up a group chat for the intern cohort and plan at least one virtual social event a week. For co-op or year-round programs, run recruiting on a rolling basis and repeat the run phase for each cohort.
Common mistakes to avoid
- Starting recruiting late leaves you with the candidates other employers passed on, so plan backwards from the start date and open roles early.
- Letting an intern arrive with no laptop, access or first task wastes the first week, so test equipment and confirm a first task before day one.
- Assigning busywork instead of a real project hurts both learning and your reputation on campus, so require a one-page project brief for every role.
- Giving feedback only at the end leaves no time to improve, so hold a written mid-point review for every intern.
- Deciding return offers on gut feel creates unfair outcomes, so set the criteria and rubric before the program starts and calibrate evaluations in one meeting.
- Forgetting to ask interns and managers what worked repeats the same problems, so run exit surveys and write a short review each year.
Frequently asked questions
What should an internship program plan include?
It should include the program goals, number of interns, project briefs, managers and mentors, a recruiting timeline, a program calendar, an evaluation rubric and return-offer criteria. Add owners and dates for each part, and the metrics you will report.
How long should an internship program be?
Many summer internships run around ten to twelve weeks, and semester internships follow the school calendar. Choose a length that lets an intern finish a real project with time to present it. Check any school credit requirements with the student's school.
When should you start planning a summer internship program?
Start several months ahead. Many employers begin recruiting for summer roles in the fall or winter, so approval and project briefs need to be ready before then. Plan backwards from the start date.
What should an intern do in the first week?
Get set up, meet their manager, mentor and team, learn how the company works and finish one small task. Hold the project kickoff by the end of the week or early in the second week so they know exactly what they are building.
How do you measure the success of an internship program?
Compare results with the program goals: project completion, intern and manager survey scores, return offers made and accepted, and how many interns later join full time. Track the same metrics every year to see the trend.