Loyola College, Chennai: Project Management Internship Guide to Tools, Trackers and Demos

Can a Loyola College, Chennai student build a credible project management internship portfolio using only free tools? Yes. A spreadsheet tracker, a free kanban board and a short demo of both are enough to show planning, tracking and communication skills. This guide walks through each tool, then ends with a sample plan you can copy, adapt and share.

This is an independent guide written for students of the college. It is not issued by, endorsed by or connected with the institution. Anything about college rules, internship credit or project formats should be confirmed with your department, as explained in the verification section below.

What a project management internship actually tests

Project management is the discipline of getting a defined piece of work finished, on time, within limits, with the right people informed. In a short internship, nobody expects you to run a multi-crore programme. A reviewer wants to see four things:

• Scope clarity: can you say what the project will deliver and what it will not?
• Breakdown: can you split a goal into tasks small enough to finish in a day or two?
• Tracking: can you show, at any moment, what is done, what is blocked and what is late?
• Communication: can you explain status in two minutes to someone who was not in the room?

Every tool in this guide serves one of those four tests. A tool is only useful if it makes one of them easier to show.

Choosing your tool: spreadsheet versus kanban board

Both options below are free at a basic level on several widely used services, though plan limits and features change. Check the current free tier of whichever service you pick before you commit to it. A spreadsheet suits a plan that has dates and dependencies. A kanban board suits work that arrives continuously and moves through stages.

The strongest demo uses both: the spreadsheet as the plan of record, the board as the daily working view. The next sections build each in turn.

Demo 1: The spreadsheet tracker, step by step

Step 1: Set up the task register

Create one sheet named Plan. Use one row per task and these columns: Task ID, Work package, Task, Owner, Start date, Due date, Duration (days), Status, Percent complete, Dependency, and Notes. Freeze the top row so headings stay visible when you scroll.

Step 2: Add data validation

Make Status a dropdown with exactly four values: Not started, In progress, Blocked, Done. Fixed options prevent typos that would break your summary counts later. In most spreadsheet apps this is under the Data menu as data validation or a dropdown list.

Step 3: Calculate duration and lateness

Duration is the due date minus the start date plus one. Add a helper column called Late? that flags any task whose due date has passed and whose status is not Done. The logic, in plain words: if today is after the due date and status is not Done, show Late, otherwise leave blank.

Step 4: Build a summary block

On a second sheet named Dashboard, count tasks by status and compute overall percent complete as the average of the percent column. Add a count of late tasks. A reviewer should understand project health from this one screen without opening the task list.

Step 5: Add a risk log

A third sheet, Risks, holds each risk with a description, likelihood (1 to 3), impact (1 to 3), a score (likelihood times impact), a response and an owner. Sort by score, highest first. Three to six honest risks beat a dozen generic ones.

Demo 2: The free kanban board, step by step

1. Create the board and name it after the project, not the tool.
2. Set columns: Backlog, This week, In progress, Blocked, Review, Done. Keep six at most.
3. Write cards as outcomes. “Draft survey questions” is a card. “Survey” is a category, not a card.
4. Add a due date and one owner to every card that enters This week.
5. Limit work in progress. Allow no more than three cards in In progress at a time. This habit is the core of kanban, and it exposes bottlenecks quickly.
6. Use labels for work packages, such as Research, Design and Communication, so you can filter the board.
7. Record why a card is Blocked in the card itself, and note who can unblock it.
8. Review weekly: move finished cards to Done, then write a three-line status note.

The scorecard: rate your own demo before sharing it

This is the practical asset to use before you show anything to a mentor, faculty member or hiring manager. Score each row from 0 to 2: 0 means absent, 1 means partly done, 2 means clearly done. The maximum is 24.

A score under 14 means the plan needs another pass. A score of 20 or more is ready to share. Treat the numbers as a self-check, not an official grade.

Worked example: planning a department orientation week (illustrative)

The following example is illustrative. It is a made-up project, not a real event at any college, and no figures here come from an actual institution.

Goal: Deliver a three-day orientation programme for 60 new students by a fixed Monday, with a feedback summary published within five days of the final session.

Out of scope: Hostel arrangements and printed souvenirs.

Team (hypothetical): Four student volunteers named A, B, C and D, plus a faculty advisor who approves the schedule.

Work packages

• WP1 Schedule and venue: draft the session plan, request the venue, confirm speakers.
• WP2 Communication: prepare a welcome message, a reminder message and a one-page map.
• WP3 Registration: build the attendee list and a sign-in sheet.
• WP4 Feedback: write a short survey, collect responses, summarise them.

Sample task register (excerpt)

Reading the plan like a manager

Task 1.2 is on the critical path, because speakers (1.3) and the welcome message (2.1) both wait for it. If approval slips by two days, the whole schedule slips by two days. Task 3.1 is blocked, and its note should say why, for example “waiting for the admissions list”, and name who can release it. Task 3.1 does not depend on anything else, so the fix is a quick follow-up, not a replan.

Risk log excerpt (illustrative)

The shareable sample plan template

Copy this into a blank spreadsheet to start. Paste each line into cells separated by commas, or import it as a CSV file. The dates are placeholders to replace with your own.

ID,Work package,Task,Owner,Start,Due,Duration,Dependency,Status,Percent
1.1,Schedule,Draft session plan,A,DD-MM,DD-MM,2,,Not started,0
1.2,Schedule,Advisor approval,A,DD-MM,DD-MM,2,1.1,Not started,0
2.1,Communication,Write welcome message,C,DD-MM,DD-MM,1,1.2,Not started,0
3.1,Registration,Build attendee list,D,DD-MM,DD-MM,2,,Not started,0
4.1,Feedback,Write survey,C,DD-MM,DD-MM,2,1.1,Not started,0
4.2,Feedback,Summarise responses,C,DD-MM,DD-MM,2,4.1,Not started,0

One-page cover note to attach

1. Project goal in one sentence.
2. Scope and exclusions in two short lists.
3. Timeline: start, end and the one milestone that matters most.
4. Current status: done, next, blocked.
5. Top three risks with owners.
6. Link to the view-only spreadsheet and board.

Sharing safely

• Use view-only links, not edit links, for anything leaving your group.
• Remove phone numbers, email addresses and any student data from sample files. Use initials or placeholders such as A, B, C.
• Label the file clearly as a sample or practice plan, so nobody mistakes it for a real institutional document.

A five-minute demo script

Many internship reviews and viva sessions ask you to show your work live. Practise this order:

1. Minute 1: State the goal and scope. Do not open any tool yet.
2. Minute 2: Show the Dashboard sheet. Name the number of late and blocked tasks.
3. Minute 3: Open the kanban board. Pick one card and explain how it moved.
4. Minute 4: Show the top risk and your response.
5. Minute 5: Give the three-line status note and name one thing you would do differently.

Ending with a candid improvement point signals maturity. Reviewers tend to trust a plan whose author can say what went wrong.

Common mistakes in student project plans

• Tasks that are too large. “Complete research” cannot be marked done honestly. Break it into pieces.
• Shared ownership. When two people own a task, neither does.
• No buffer. Plans where every task fills its slot exactly will slip. Add a day before any fixed deadline.
• Silent date changes. Overwriting a due date erases the history. Log the old date, the new date and the reason.
• Tool over substance. A beautiful board with vague cards earns less than a plain sheet with sharp tasks.

A two-week practice roadmap

If you want structured practice alongside this roadmap, CareerSwami offers a free two-week online internship with a free offer letter and a free completion certificate after successful completion, across 26 tracks. Choose the track that matches your goals, and confirm separately whether your department treats any external internship as acceptable for its requirements.

Loyola College, Chennai: where a project management practice plan fits

Loyola styles itself Loyola College (Autonomous), Chennai, and its About page says it was among the first eight colleges to receive autonomous status, in 1978. For a student building a tracker or kanban demo, this matters mainly because internship and project requirements may be set at college or department level. Look for the rules for your own programme instead of relying on a general template.

The college site has departmental home pages for Computer Science, Data Science, B.B.A., B.Com (Computer Applications) and B.Com (CS). A B.B.A. student may frame the orientation-week plan as an operations or event exercise, while a computer science or data science student may frame it as a small software or analysis project. The Data Science page lists M.Sc. Data Science and has a Syllabus section, but the link did not lead to syllabus text. Find the current syllabus through your department office before linking your plan to any course.

On timing, the academic calendar page shows semester examinations on 3-6 Nov 2026 and day-order teaching restarting on 24 Nov 2026. The gap in mid-November is a practical window to complete the two-week practice roadmap, provided your own timetable agrees with the calendar. Check the page again for any revision.

The Training & Placement Cell manages campus placements and coordinates between the college and recruiters, and the page gives separate contact addresses for corporate and student enquiries. Use the student address if you want to ask whether the cell deals with internship queries, since the page describes placement work. The calendar archive has a 2019 entry, “Internship begins for III UG students”, which suggests a college-scheduled UG internship at that time but states no rules. Do not treat it as a current requirement.

No internship duration, credit, report format or online-internship rule was found on the pages above, so treat your tracker as a self-made practice portfolio unless your department says otherwise.

Checks before you share or submit your plan

• Email your department office asking whether an online or self-directed project internship is acceptable and what proof is needed.
• Ask for the current syllabus or regulations for your batch and find any internship or project-work clause, including hours and report format.
• Ask your faculty mentor whether a tracker plus a cover note is enough or whether a signed report or logbook is required.
• Write to the student address of the Training & Placement Cell, asking whether it handles internship documents for your department.
• Confirm whether you may use real class, event or student data in a shared sample.
• Keep every reply as an email or signed note and file it with your certificate.

Frequently Asked Questions

Do I need paid software to practise project management?

No. A free spreadsheet application and a free tier of a kanban service cover everything in this guide. Free plan limits change, so check the current terms of the service you choose.

Should I use a Gantt chart?

A Gantt chart helps when tasks depend on each other and dates matter. You can approximate one in a spreadsheet by shading date cells with conditional formatting. For a small project, the task register with a dependency column often communicates just as well.

How many tasks should a practice project have?

Fifteen to twenty-five tasks suit a two-week exercise. Fewer than ten hides your breakdown skill, and more than thirty makes the plan hard to maintain and hard to explain in a short demo.

What is the difference between a task and a milestone?

A task is work that takes time, such as drafting a survey. A milestone is a checkpoint with no duration, such as “survey approved”. Milestones help you report progress to people who do not need task detail.

Can a sample plan count as an internship project at my college?

That depends on your programme’s rules, which this guide cannot state. Ask your department in writing what format and proof it accepts, and use the verification list above.

How do I show teamwork if I built the plan alone?

Use a realistic scenario with clearly labelled hypothetical roles, and say so in your cover note. Alternatively, run a small genuine project with classmates, assign real owners and log each person’s cards honestly.

What should I put on a CV from this exercise?

Describe what you built and what it showed, in plain terms: for instance, a task register, dashboard and risk log for a practice project. Avoid claiming outcomes, budgets or team sizes that did not exist.

How often should I update the tracker?

Update the board daily while work is active and the dashboard at least weekly. A tracker that is a week old is worse than none, because it gives false confidence.

Related Project Management guides

• Madras Christian College Students: Turning Project Management Internship Work into Resume Evidence
• St. Joseph's College of Commerce, Bengaluru: Project Management Internship Questions to Ask Before Applying
• Guru Nanak Dev University Students: Project Management Internship Prerequisites and Starter Tools
• All Project Management internship guides