MBA Internship Plan Template

MBA Internship Plan: [Your name, employer, summer YYYY]

A working plan for the 10 to 12 week summer internship between the first and second year of a full-time MBA: goals agreed with your manager, a stakeholder map, a week-by-week project plan, a weekly check-in routine, a structured mid-point review, the final presentation, and the steps that turn a strong summer into a full-time offer. It is for MBA interns in consulting, banking, corporate strategy, product, operations, healthcare and other functions, and for career services coaches who support them. Source basis: onboarding and transition research (Watkins 2003), stakeholder analysis (Mendelow 1981), goal-setting theory (Locke and Latham 1990) and feedback practice, written in our own words. Replace every [bracketed] value and every row marked Example. The worked example uses a fictional company, Corvane Robotics. This is a planning aid, not legal, immigration or employment advice.

Document control

Contents

1. Purpose and how the internship works
2. Before day one
3. The internship as a process
4. Goals agreed with your manager
5. Stakeholder map
6. Project plan
7. Weekly check-ins
8. Mid-point review
9. Final weeks and the final presentation
10. Converting the internship into a full-time offer
11. Learning log and network
12. Timeline with relative dates
13. Quality checklist
14. Common mistakes

1. Purpose and how the internship works

The MBA summer internship is two things at once. It is a real piece of work that a team needs done, and it is a ten to twelve week assessment that ends in a decision about a full-time offer. Employers that recruit MBA students through structured programmes, such as consulting firms, investment banks and large corporate leadership programmes, usually treat the summer as the main selection step for full-time hires, and many make most of their full-time offers to returning interns. Smaller firms and start-ups may hire an intern for a defined project with no full-time role planned. Ask early which model applies to you, because it changes how you spend your time.

Most evaluations combine three sources of evidence. The first is the quality of your work product: the analysis, the recommendation and the final presentation. The second is how you worked: pace, ownership, judgement about when to ask for help, how you handled feedback. The third is fit with the team, which in practice means whether the people you worked with would want you on their next project. Formal programmes often collect written feedback from several people and discuss it in a review meeting; informal ones rely on one manager's view. Either way, the people who decide rarely see your work directly. They see what your manager and stakeholders say about it, which is why written updates and a clear stakeholder plan matter as much as the analysis.

The research on job transitions is useful here. Watkins (2003) argues that new leaders should secure early wins, agree expectations explicitly with their boss and build coalitions before they need them. A summer intern has a much shorter horizon than a new executive, but the logic transfers: you have about three weeks to understand the problem and the people, about five weeks to do the core work, and about three weeks to land the recommendation and the offer conversation. Goal-setting research (Locke and Latham 1990) adds that specific, challenging goals with feedback lead to better performance than vague "do your best" goals, which is why section 4 asks for goals you can verify.

2. Before day one

Use the weeks before the start date to remove avoidable friction. Read the company's public material: annual report or investor letters if it is listed, recent press releases, product pages, the leadership team and any public strategy statement. If your manager has shared the project topic, read about the industry and list the questions you expect to answer, but do not build a model before you have seen the data. Check practical items: start date, office, equipment, security training, any required work authorisation documents (follow your school's international student office and the employer's HR; this template does not give immigration advice), and payroll set-up.

Send your manager a short note one to two weeks before you start: thank them, confirm the date, say what you have read and ask whether there is anything they would like you to look at first. Keep it to five sentences.

3. The internship as a process

The diagram shows the internship as four phases with two formal checkpoints. The checkpoints are where your goals and your manager's view are compared on paper.

4. Goals agreed with your manager

Ask your manager three questions in the first week: what problem the business needs solved, what a great outcome looks like at the end of the summer, and how you will be evaluated. Turn the answers into three to five goals. Each goal should name an output, a standard and a date. Include at least one goal about how you work (for example, "weekly written updates every Friday") because process goals are the ones evaluators comment on most often. Then write how each goal will be checked, and by whom.

Also agree the practical rules: how your manager prefers updates (email, chat, a standing meeting), what you may decide alone, who you may contact without asking, which data are confidential and when the final presentation will be scheduled. Write the answers below.

5. Stakeholder map

A stakeholder map lists everyone who can affect your project or the offer decision and classifies them by how much power they have over the outcome and how interested they are in it. The power-interest grid is usually attributed to Mendelow (1981). Score each person from 1 to 5 on influence and on interest, multiply the two for a rough priority, and plan a contact rhythm for each quadrant: manage closely (high, high), keep satisfied (high influence, lower interest), keep informed (lower influence, high interest) and monitor (low, low).

Worked example, Corvane Robotics (Example). The intern's project is RaaS pricing; the scores are the intern's own judgement after week 1. The priority score is influence times interest.

Your map:

Excel: priority in column E is =C2*D2. Sort by column E, largest first, and check that every person with a score of 12 or more has a dated contact in your plan. If the person who decides on offers is not on the map, add them: in many firms that is a recruiting partner or a committee you will meet only once or twice.

For decision rights on the project itself, a RACI chart (responsible, accountable, consulted, informed) helps when several functions are involved; see business/raci.

6. Project plan

A summer project fails more often from late scoping than from weak analysis. Agree the question, the scope and the deliverable in week 2, write them in a one-page charter (business/project-charter works), and plan backwards from the final presentation. A useful rule is "answer first": write a draft recommendation, labelled as a hypothesis, by the end of week 3, then spend the middle weeks proving or disproving it. Revise it openly when the evidence goes the other way; that shows judgement, not weakness.

6.1 Charter

6.2 Week-by-week plan (Example)

The Gantt chart shows an 11-week plan for the Corvane example. Replace the dates with your own.

6.3 Time budget

How you spend your hours is a choice. The example below assumes 50 hours a week for 11 weeks (550 hours). Adjust the weekly hours to your employer's norms and local working-time rules.

Excel: hours in 11 weeks =B2*$B$9*$B$10 where B9 holds 50 (hours a week) and B10 holds 11 (weeks); check that the shares sum to 100% with =SUM(B2:B6). The point of the table is the 10% for events and networking: interns who skip cohort events to polish slides lose the relationships that matter at the offer stage, and interns who attend every event lose the analysis.

7. Weekly check-ins

A standing weekly 1:1 with your manager plus a short written update is the single most useful habit of a summer internship. The written update does three jobs: it keeps your manager ahead of questions from their own boss, it creates a record of progress that feeds your evaluation, and it surfaces problems while they are still cheap to fix. Use the same format every week so it takes ten minutes to write and one minute to read.

Friday update format

• Done this week: [two to four bullets, each a result, not an activity].
• Next week: [two to three bullets].
• Risks and asks: [one ask with a date: "Can you introduce me to the CRO's chief of staff by Wednesday?"].

At each 1:1, ask one feedback question that is specific enough to answer: "What would make the interview synthesis more useful to you?" works better than "How am I doing?". Record the answer and what you changed in response; the evidence of acting on feedback is itself something evaluators look for.

8. Mid-point review

The mid-point review is your one chance to correct course with time left to show the change. Before the meeting, rate yourself on the criteria the firm uses (ask HR or your manager for the form; if there is none, use the criteria below), with one piece of evidence for each rating. Ask your manager to rate the same criteria. Compare, discuss the largest gaps, and agree no more than three actions.

Worked example (Example). Weights reflect what the manager said matters most; ratings are on a 1 to 5 scale.

Excel: weighted total =SUMPRODUCT(B2:B6,C2:C6) for self and =SUMPRODUCT(B2:B6,D2:D6) for the manager. In the example the manager rates the intern 0.35 points higher than the intern's own score, with the largest gap on ownership and on stakeholder management. That is good news, but the shared weak point is communication (3 from both). The action plan should therefore target the storyline, for example by writing the final presentation's executive summary in week 6 and testing it with the manager (see mba/mba-internship-final-presentation).

Questions to ask at the mid-point review:

1. "If the summer ended today, what would the evaluation say?"
2. "What is one thing I should do more of, and one thing I should stop?"
3. "Who else will give input on my evaluation, and is there anything I should do to make sure they have seen my work?"
4. "What would make the final presentation a clear success from your point of view?"

9. Final weeks and the final presentation

The final presentation is the most visible moment of the summer, and often the only time senior decision makers see your work. Build it with the template mba/mba-internship-final-presentation, which covers the storyline, executive summary, exhibits, implementation plan and Q&A preparation. In this plan, record the dates:

The handover pack matters more than interns expect. A model nobody can update dies when you leave, and a manager who has to explain your spreadsheet to their boss in September will remember that. Include the final deck, the model with an assumptions log, interview notes in the agreed format, open questions and the names of the people who helped.

10. Converting the internship into a full-time offer

How offers are made differs by employer and sector. Structured programmes typically decide at the end of the summer or a few weeks after it, and communicate offers before or early in the second year. Many business schools publish recruiting guidelines for employers that recruit on campus, including how long an offer made at the end of a summer internship should remain open; the dates and rules differ by school and change, so check your school's current career services policy and the offer letter itself. Smaller employers may decide later, once they know their hiring needs for the following year. If you are not sure, ask your manager or the recruiting contact in week 8 or 9: "Could you tell me how and when decisions about full-time roles are made for this year's interns?"

Ways to strengthen the case in the last three weeks:

• Finish strong: the final presentation and handover shape the last impression.
• Make sure every person who will give input on your evaluation has seen your work directly at least once.
• Ask your manager, in the last 1:1, for their honest view of your strengths and the one area to develop. Thank them in writing.
• Keep in touch after the summer: a short note when the recommendation is implemented, or a congratulation on a team result.

If you receive an offer, evaluate it against your other options and the school's offer-deadline rules before you answer; mba/mba-offer-negotiation covers total-compensation comparison, the negotiation plan and exploding offers, and career/offer-comparison is a shorter checklist. If you do not receive an offer, ask for specific feedback, ask whether your manager would act as a reference, and return to second-year recruiting with your career services office. Many students who do not convert land strong full-time roles; a well-documented project is a good interview story (mba/mba-fit-stories).

11. Learning log and network

The internship is also an experiment about your career: you are testing whether you like the work, the people and the pace. Record evidence while it is fresh. Kolb's (1984) experiential learning cycle (concrete experience, reflective observation, abstract conceptualisation, active experimentation) is a simple structure: what happened, what you noticed, what you conclude, what you will try next week.

Track the people you meet in mba/mba-networking-tracker. Aim for a short conversation with someone outside your team each week; ask what their path was and what they would look for in a full-time hire. These are also the people who can tell you what full-time work in this firm is really like, which you need for the post-MBA plan (mba/mba-post-mba-career-plan).

12. Timeline with relative dates

13. Quality checklist

• Goals agreed in writing in week 1, each with an output, standard, date and checker.
• Working rules (updates, decisions, confidentiality, AI tools) recorded.
• Stakeholder map covers everyone who gives input on the evaluation.
• One-page charter with a key question signed off by week 2.
• A written hypothesis exists by week 3 and is revised openly as evidence arrives.
• A Friday update was sent every week.
• Mid-point review held, gaps compared, at most three actions agreed.
• Final presentation pre-wired with the key stakeholders.
• Handover pack delivered and confirmed usable.
• Offer timing and the school's offer-deadline guideline understood before week 9.
• Learning log has an entry for most weeks.
• No confidential employer data stored on personal devices or unapproved tools.

14. Common mistakes

1. Starting analysis before agreeing the question. Two weeks of modelling on the wrong scope is a lost sixth of the summer.
2. No written goals. You are then evaluated against criteria you never saw.
3. Silent weeks. A manager who hears nothing assumes nothing is happening; send the Friday update.
4. Waiting for the perfect answer. Present a labelled hypothesis early; the feedback is worth more than the polish.
5. Ignoring the people who decide. If the recruiting partner or committee never sees your work, your manager has to argue for you without evidence.
6. Surprising senior people in the final presentation. Pre-wire the key stakeholders so that disagreements surface in private.
7. Skipping the cohort and firm events. Fit is part of the evaluation, and the other interns are your future network.
8. Attending every event and missing deadlines. Balance with an explicit time budget (section 6.3).
9. Asking for an offer directly. Ask how decisions are made and what would strengthen your case instead.
10. Mishandling confidential data. Pasting employer data into a personal AI tool or emailing it to a personal account can end an internship; follow the employer's policy.
11. A model only you can use. No assumptions log, no handover, no credit after you leave.
12. Treating the summer only as a test. It is also your best evidence about whether you want this career; keep the learning log.

Sources and further reading

• Watkins, M. D. (2003). The First 90 Days: Critical Success Strategies for New Leaders at All Levels. Harvard Business School Press. Transition planning, early wins and the relationship with the boss.
• Locke, E. A. and Latham, G. P. (1990). A Theory of Goal Setting and Task Performance. Prentice Hall. The evidence for specific, challenging goals with feedback.
• Mendelow, A. L. (1981). Environmental scanning: the impact of the stakeholder concept. ICIS 1981 Proceedings, 20. aisel.aisnet.org. Usually cited as the origin of the power-interest grid (sometimes referenced with the year 1991).
• Kolb, D. A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Prentice Hall. The learning cycle used in section 11.
• Minto, B. (2009). The Pyramid Principle: Logic in Writing and Thinking (3rd ed.). FT Prentice Hall. Answer-first structure for updates and the final presentation.
• Your school's career services recruiting guidelines for employers, including any rules on offer deadlines (check the current year).
• Related templates: career/ninety-day-plan (the same logic for the first full-time role), mba/mba-internship-final-presentation, mba/mba-offer-negotiation, mba/mba-networking-tracker, business/raci, business/project-charter.

Revision history

Standard and licence note

Structure aligned with published research on job transitions (Watkins 2003), goal setting (Locke and Latham 1990), stakeholder mapping (Mendelow 1981) and experiential learning (Kolb 1984). The text, examples and calculations are original, and Corvane Robotics and all people in the examples are fictional. The template is not affiliated with or endorsed by any business school, employer or professional body. Check your employer's policies and your school's current recruiting guidelines before you rely on any timing rule. Template licence: MIT.