CHRIST (Deemed to be University): Project Management Internship Portfolio with Plans and Risk Logs

A strong project management internship portfolio for a CHRIST (Deemed to be University) student needs three core documents: a plan (usually a Gantt chart), a risk register, and a status report. Each should be anonymised and show how you made decisions, not just what you produced. This guide gives you templates and an illustrative worked example for each, a scorecard to check your own work, and a short list of questions to put to your college.

What a project management portfolio is actually for

A portfolio is evidence. A resume line such as “assisted with project coordination” tells a reader nothing. A one-page plan, a risk log with owners and dates, and a status report that flags a slipping milestone show how you think. Evaluators reading an internship portfolio, whether a faculty mentor, a hiring manager or a selection panel, usually look for four things:

• Structure: can you break a goal into deliverables, tasks and dependencies?
• Foresight: do you identify what could go wrong before it does?
• Communication: can you report status in plain language, with numbers and next steps?
• Judgement: when something changed, what did you decide and why?

Project management is a good domain for students because even a small task has a scope, a deadline, stakeholders and risks. A fest committee, a club event, a research survey or a short online internship can all be treated as projects. The skill lies in documenting them the way a professional would.

The portfolio at a glance

Keep the whole portfolio to roughly six to eight pages. Longer is rarely better. Use the table below as your contents page.

Step 1: Write a project brief before anything else

Every later document depends on the brief. Write it in five short parts:

1. Goal: one sentence with a measurable result.
2. Scope: three to five deliverables you will produce.
3. Out of scope: things people might assume you will do, but you will not.
4. Stakeholders: who approves, who is affected, who helps.
5. Success measures: deadline, quality criteria, and any budget or effort limit.

The “out of scope” line matters most. It is your protection against scope creep, and it shows maturity to a reader.

Step 2: Build the plan and Gantt chart

Start with a work breakdown structure (WBS): list deliverables, then split each into tasks small enough to finish in one to three days. Then add durations, dependencies and milestones. A spreadsheet is enough. You do not need paid software to show good planning.

Illustrative Gantt sample (anonymised)

The sample below is illustrative. It imagines a 14-day student project: preparing a vendor comparison report for a small campus event. It is not drawn from any real organisation. Each “X” marks a working day for that task.

Notice what makes this usable. The tasks are verbs. Every task after the first has a dependency. The critical path runs 1 → 2 → 3 → 4 → 5 → 6 → 7, so any delay in collecting quotes pushes the final date. You should say so in your portfolio, in one sentence beneath the chart.

Gantt quality checklist

• Every task starts with a verb and produces something checkable.
• No task is longer than about a third of the whole timeline.
• Dependencies are written down, not implied.
• At least one milestone is a review or approval, not just a task end.
• The critical path is named.
• You have saved a baseline copy so you can compare planned and actual dates later.

Step 3: Keep a risk register that someone could act on

A risk is something that might happen. An issue is something that has already happened. Many student registers confuse the two. List risks, score them, assign an owner, and write a response you could realistically carry out.

A simple scoring method: rate probability and impact from 1 (low) to 3 (high), then multiply. Scores of 6-9 need active management, 3-4 need monitoring, 1-2 can be accepted.

Illustrative risk register (anonymised)

This sample continues the imaginary vendor-comparison project. All names, figures and dates are invented for demonstration.

Risk register checklist

• Each risk is written as “if X happens, then Y suffers”, not as a vague worry.
• Every row has a named owner. “Team” is not an owner.
• Responses use one of four labels: avoid, mitigate, transfer or accept.
• There is a trigger, meaning a visible sign that the risk is becoming real.
• The register is reviewed on dated occasions, and the portfolio shows at least two versions.

Step 4: Write status reports that a busy reader can scan

A status report answers five questions: where are we, are we on track, what changed, what could hurt us, and what do you need from the reader. Keep it to one page. Include two reports taken at different times so the reader sees the project moving.

Illustrative status report (anonymised)

The report below is invented for the sample project, as at the end of day 8.

Status colours should have a stated rule. For example: green means within one day of plan, amber means one to two days behind with a recovery plan, red means more than two days behind or a milestone at real risk. Whatever rule you choose, write it at the foot of the report.

Step 5: A worked example of the plan, risk and report working together

This short example is illustrative and shows how the three documents connect.

1. Plan: The Gantt chart shows task 3 (collect quotes) as a four-day task on the critical path.
2. Risk: R1 in the register flags late vendor replies as the highest-scoring risk (3 × 3 = 9), with a trigger of “no reply by D5”.
3. Event: On D5 one vendor has not replied. The trigger fires.
4. Response: The intern contacts the backup vendor and records the action against R1.
5. Report: The D8 status report shows amber, explains the one-day slip, and asks for approval of the backup vendor if needed.
6. Re-plan: The Gantt chart is updated, and the baseline copy shows the original dates for comparison. Task 4 now overlaps task 3 by one day, which is noted in the change log.

A reader who sees this chain understands that the documents are not decoration. Each one drove a decision. That is what separates a portfolio from a folder of templates.

Portfolio scorecard

Before you share your portfolio, score each item from 0 to 2: 0 for missing, 1 for present but weak, 2 for strong. A total of 22 or more out of 28 is a solid submission.

How to anonymise properly

If your work involves a real organisation, even a college club, remove anything that could identify people or reveal private numbers. Replace names with roles (“Faculty mentor”, “Vendor A”). Round or scale financial figures, or replace them with percentages. Remove email addresses, phone numbers and file paths. Check document properties and spreadsheet comments, since author names often hide there. If you are unsure whether something is confidential, leave it out or ask the person who owns the information, in writing.

Where a free online internship can supply your project

If you do not have a live project to document, you can create a real one from a short internship task. CareerSwami offers a free two-week online internship across 26 tracks, with a free offer letter and a free completion certificate after successful completion. Treat the 14 days as your project window. Write the brief on day 1, plan the tasks, keep a risk log, and issue yourself a status report at the midpoint and the end. The certificate is a separate document. The portfolio is what shows your thinking.

CHRIST internship rules and your project management portfolio

A project management portfolio (brief, Gantt plan, risk register, status reports) is only useful at CHRIST if it fits the way your own department runs internships. The one published rule set available is a department-level document, so it shows how rules can work rather than what applies to every programme.

The 2018 summer internship guidelines of the MA International Studies programme state that students finishing semester 2 complete a six-week internship in April–May, before semester 3. That is a useful template for planning: a fixed six-week window is the kind of schedule a Gantt chart handles well, with a start-up week, delivery weeks and a closing week for the report.

The same document says students may find an internship themselves or through the department, but must get a confirmation letter from the host organisation sent to the internship coordinator before joining, and cannot change organisation without the coordinator’s approval. In practice, secure that letter before you start building any plan, and do not swap your project host midway because your risk register suggests it.

It also requires at least six weekly reports to an allocated internship guide through the LMS, copied to the coordinator. Your portfolio’s status report format maps neatly onto this: one scannable weekly report can serve as the basis for the official one, though the department’s own template decides what is submitted. The 2018 deadlines (certificate by 1 June, report by 10 June) applied to that batch only.

Important limits: this is a 2018 document for one department. It does not give credits or evaluation weightage, and it does not address online internships. Rules for other programmes may differ, so treat the portfolio as a separate showcase or as appendices to the official report. This is an independent guide; CareerSwami is not affiliated with the university, and a free internship or certificate from it carries no stipend, credit, placement or job.

Checks before you build your portfolio

• Ask your internship coordinator for the current guidelines for your programme and batch, as the 2018 version may have been replaced.
• Confirm in writing whether an online, self-sourced internship is allowed, and whether the host confirmation letter is required before starting.
• Ask whether weekly reports go through the LMS, how many are needed, and whether your portfolio status reports can be adapted for them.
• Check who your internship guide will be and whether they accept extra material such as a Gantt chart or risk register as appendices.
• Ask about confidentiality rules before including any project material, even anonymised, in a public portfolio.

A 14-day schedule for building the portfolio

Project management portfolio mistakes that weaken plans and risk logs

• Plans with no dependencies. A list of dates is a calendar, not a plan.
• Risks that read like slogans. “Time management” is not a risk. “Quote replies arrive after D5” is.
• Always-green reports. A project that never slips looks invented. Honest amber entries build credibility.
• Template-only portfolios. Blank templates prove nothing. Show filled documents and how they changed.
• Overstating your role. Say what you did, what the team did and what you only observed.

Presenting the portfolio

Export to one PDF with a clear file name, such as “Name_ProjectManagement_Portfolio.pdf”. Add a short opening paragraph describing the project, your role, the timeline and the outcome. On your resume, use one line that points to measurable content, for example: “Planned and tracked a 14-day project with a 7-task Gantt chart, a 6-item risk register and two status reports.” Only use numbers that match your real documents. In an interview, be ready to walk through one risk, one change and one decision from start to finish.

Frequently Asked Questions

How many documents should a project management internship portfolio include?

Five to six is enough: a brief, a Gantt chart, a risk register, two status reports, a change log and a short reflection. Depth and evidence of updates matter more than volume.

Do I need Microsoft Project or other paid software?

No. A spreadsheet can produce a clear Gantt chart and a risk register. What reviewers look at is the logic: dependencies, owners, dates and changes over time.

Can I build a portfolio from a club or fest project?

Yes, if you anonymise it and have permission to share anything sensitive. Treat the event like a project with a scope, plan, risks and reports. Replace names with roles and remove private figures.

In a project risk log, how is a risk different from an issue that has already happened?

A risk is a possible future event with a probability and impact. An issue is already happening and needs action now. A risk can become an issue, and your register should show when that happened.

Will this portfolio count toward my college internship requirement?

That depends on your programme’s rules, which this guide cannot state. Ask your department coordinator in writing whether your internship type and documentation format are acceptable.

How do I show results if my project was small?

Use planned-versus-actual comparisons: days planned against days used, risks identified against risks that occurred, and changes requested against changes accepted. Small projects can still show disciplined control.

Should I include real company data to look more impressive?

No. Confidential data can cause harm and does not improve the portfolio. Use anonymised or scaled figures and describe your method clearly.

Does a completion certificate replace the portfolio?

No. A certificate confirms that you completed a programme. The portfolio shows how you plan, assess risk and report, which is what a reader usually wants to see.

Related Project Management guides

• Amity University, Uttar Pradesh: Project Management Internship Interview Preparation Guide
• SRCC Students: Project Management Internship Tasks, from Scheduling to Stakeholder Updates
• Hindu College, University of Delhi: Choosing a Project Management Internship Project Scope
• All Project Management internship guides