A risk register is a single table that lists what could go wrong on your project, how likely it is, how badly it would hurt, and who will act on it. For a first internship project, a ten-row register scored on a 1-to-5 scale for probability and impact is enough, and you can defend it in a review by showing how each score was reached. This walkthrough gives you the template, ten populated risks, a scoring method, and a worked example built around a 14-day plan.
Why a 14-day internship project needs a risk register at all
Two weeks is short. A single lost day is about 7% of your total time, and a missed approval can eat three days. Large projects can absorb surprises; yours cannot. A register forces you to think about surprises on day 1, when fixing them is cheap, rather than on day 9, when the only options are cutting scope or submitting something half-finished.
It also gives you something concrete to show a supervisor or faculty reviewer. Reviewers rarely expect a flawless first project. They do notice whether you anticipated problems, named a response, and updated your thinking as the days passed. A register is visible evidence of that.
If you are looking for a project to practise on, the free two-week online internship from CareerSwami has a 14-day structure that fits this exercise well, with a free offer letter and a free completion certificate after successful completion, across 26 tracks.
The register template: columns and what each one is for
Keep the columns few. Every extra column is something you must maintain, and by day 5 you will stop maintaining anything that is tedious.
- ID: R1 to R10, so you can refer to a risk in a message or review.
- Risk statement: written as “If [event], then [consequence]”. This prevents vague entries such as “time problems”.
- Probability (P): 1 to 5, scored using the guide below.
- Impact (I): 1 to 5, scored using the guide below.
- Score: P × I, giving 1 to 25.
- Owner: one named person who watches the risk and triggers the response. On an individual internship this is often you, but it can be your mentor or a teammate.
- Response: the action you will take. State whether you are avoiding, reducing, accepting or escalating.
- Trigger and status: the observable sign that the risk is happening, and whether it is open, closed or occurred.
Free 2-Week CareerSwami Internship
Online, 14 days, with a free offer letter and a free completion certificate once you finish the work. Check with your college that it fits your requirement before you enrol.
A scoring method a beginner can defend in a review
Defensible means that another person, given the same facts, would land within one point of your number. That requires written anchors, not gut feel. Use these.
Probability anchors for a 14-day project
| Score | Label | Anchor |
|---|---|---|
| 1 | Rare | Has not happened to you or anyone you know in similar work |
| 2 | Unlikely | Could happen, but you have a specific reason to think it will not |
| 3 | Possible | Happens to roughly one in three comparable projects |
| 4 | Likely | You have already seen early signs, or it is common in your setup |
| 5 | Near certain | It is already happening or depends on something outside your control that is unconfirmed |
Impact anchors measured in days and deliverables
| Score | Label | Anchor |
|---|---|---|
| 1 | Negligible | Less than half a day lost; no deliverable affected |
| 2 | Minor | About one day lost; a deliverable is slightly weaker |
| 3 | Moderate | Two days lost, or one secondary deliverable dropped |
| 4 | Major | Three or more days lost, or the main deliverable is materially reduced |
| 5 | Severe | The main deliverable cannot be submitted by day 14 |
The impact scale is tied to days because your constraint is days. Probability scores are your own judgement, so write one line of evidence beside every 4 or 5. That single habit is what makes the score defensible.
Turning scores into action bands
- 15 to 25 (high): needs a response written today and a check every day.
- 8 to 14 (medium): needs a response and a check every three or four days.
- 1 to 7 (low): accept and note it; review at the day 7 checkpoint.
When two risks tie, rank the one with the higher impact first. A 3 × 5 risk is more dangerous than a 5 × 3 risk, because the damage is larger even if it is less likely.
Ten realistic internship risks, scored and assigned
The table below is an illustrative starting register for a generic software or analysis project completed in 14 days. The scores are examples of reasoning, not measured data. Replace them with your own after you have scoped your project.
| ID | Risk (If… then…) | P | I | Score | Owner | Response |
|---|---|---|---|---|---|---|
| R1 | If the project scope is not written down on day 1, then you build the wrong thing and rework in the final week | 4 | 4 | 16 | You | Reduce: one-page scope note agreed with mentor by end of day 1 |
| R2 | If the mentor is slow to reply, then you are blocked on decisions for one to two days | 4 | 3 | 12 | You, with mentor | Reduce: agree a reply window; batch questions in one message daily |
| R3 | If your internet or power fails during a working session, then you lose hours of work | 3 | 3 | 9 | You | Reduce: save work to cloud storage hourly; identify a backup location and mobile hotspot |
| R4 | If the data or source material you need is unavailable or messy, then analysis starts late | 3 | 4 | 12 | You | Avoid: confirm a data source by day 2; keep a public fallback dataset |
| R5 | If you over-promise features, then the final days are spent rushing rather than finishing | 4 | 3 | 12 | You | Reduce: split scope into must-have and nice-to-have; freeze must-have by day 3 |
| R6 | If a tool, library or account needs approval or installation you cannot do, then setup takes days | 3 | 3 | 9 | You | Avoid: test setup on day 1 with a trivial task |
| R7 | If you fall ill or have a family or college commitment, then one to three days are lost | 2 | 4 | 8 | You | Accept with buffer: leave days 13 and 14 for finishing only |
| R8 | If your files are not versioned or backed up, then an overwrite or corruption destroys work | 2 | 4 | 8 | You | Reduce: use dated file names or a Git repository from day 1 |
| R9 | If the final report or presentation is left until the last day, then quality drops and errors slip in | 4 | 3 | 12 | You | Reduce: write a section of the report every second day |
| R10 | If you do not know what documents your college wants, then the work is done but cannot be submitted or credited | 3 | 5 | 15 | You | Escalate: ask your department in writing in week 1 (see the SMU section below) |
Notice the owners. Eight of ten sit with you, which is normal for a solo internship. The point of an owner column is not to spread blame; it is to make sure each risk has one person who will notice it. If a risk depends on your mentor, name the mentor as owner for the decision and yourself as owner for the follow-up.
Worked example: scoring and re-scoring one risk across the 14 days
This example is illustrative. It shows reasoning, not the result of any real project.
Suppose your project is to build a small dashboard analysing a public dataset. On day 1 you write R4: “If the data is messy, then analysis starts late.”
- Initial probability. You have not opened the file yet and the source is a public portal that has changed formats before. You choose P = 3 and write beside it: “Not yet inspected; format unknown.”
- Initial impact. Cleaning could take two to three days of your 14, which cuts into the dashboard. By the impact anchors, three days lost is a 4. Score: 3 × 4 = 12, medium.
- Response. You decide to open the file on day 2 and check three things: missing values, inconsistent column names, and date formats. Trigger: more than 20% of rows have a problem.
- Day 2 re-score. You find missing values in about a quarter of rows. Probability becomes 5 because it is now happening. Impact stays at 4. Score: 20, high.
- Escalation and action. You tell your mentor and agree to drop the two columns with the worst gaps. Cleaning is now planned at one day. Impact falls to 2 because the deliverable is intact. Score: 5 × 2 = 10, medium.
- Day 7 review. Cleaning finished in one day as planned. You mark the risk as occurred, closed, and write one line: “Inspected data early; dropped two columns.”
In a review, that one trail answers the questions a reviewer will ask: why did you score it that way, what did you do, and what happened. You never had to claim the risk was avoided. You showed it was managed.
A 14-day rhythm for keeping the register alive
- Day 1: draft the register with at least eight risks; score them with evidence lines.
- Days 2 to 6: two-minute check each morning. Add new risks, re-score any that changed.
- Day 7: formal midpoint review. Close dead risks, re-rank the top three, and cut scope if two high risks are still open.
- Days 8 to 12: continue daily checks; focus on risks about the final deliverable.
- Days 13 to 14: no new features. Update the register to its final state and add a short lessons-learned note.
Sikkim Manipal University students: using a risk register to protect your internship paperwork
For SMU students, the riskiest item in the register is often not technical. It is R10: not knowing what your department needs. The published rules also differ by programme and year, so check which applies to you.
The university’s history page describes SMIT as a constituent college of SMU, so your rules most likely come from the university and campus rather than from an outside affiliating body. For B.Tech students at Majitar, the SMIT Exam Procedure Manual (Version 2.0, November 2021) sets Industrial Training-I at 0.5 credit, a minimum of two weeks, done in the summer break after the 4th semester and evaluated in the 5th-semester end-semester examination. Industrial Training-II is 1 credit, a minimum of four weeks, after the 6th semester. The same manual says Mini Project, Industrial Training and Viva-Voce are evaluated by at least two examiners, drawn from the Head of Department, programme coordinator, guide or senior faculty.
In practice, a 14-day plan matches the minimum duration for Industrial Training-I, which leaves almost no slack. That makes R7 (illness or lost days) more serious for you: a lost day could put you under the minimum. Raise its probability or add a buffer. The SMIT Information Booklet 2023-24 repeats the two-week and four-week minimums for B.Tech and a four-week minimum for MCA, but it is an older document that was available only as an excerpt, so treat it cautiously.
What is not confirmed matters just as much. Whether an online internship is accepted, what completion document or report format is required, and how marks are split are not addressed in the sources reviewed. The 2021 manual is also older than the current academic year. Do not assume your CareerSwami certificate will be accepted for credit; that is your department’s decision.
Verification steps to close R10 in week 1
- Ask your programme coordinator or Head of Department, by email, whether an online two-week internship can count towards Industrial Training-I for your batch.
- Request the current internship or industrial training regulation for your scheme year, and check it against the 2021 manual rather than relying on it.
- Ask in writing what documents are required: offer letter, completion certificate, report, logbook or mentor sign-off, and in what format.
- Ask who your examiners will be and how marks are divided between report, viva and mentor feedback.
- Confirm the submission deadline and the summer break dates for 2026-27 from the published academic calendar.
- For placement-linked questions, write to the Training Placement & Industry Liaison office at placement@smit.smu.edu.in, listed on the SMIT placement contact page.
Save the replies and attach them to your register as evidence. If the answer is “not accepted”, you have lost nothing but an email; if you never asked, the risk could cost you the whole credit.
Wording each risk so a reviewer cannot dismiss it
- Name the event, not the worry. “Mentor unavailable for 48 hours” is a risk. “Communication” is a topic.
- State the consequence in days. It turns an opinion into a number reviewers can check.
- Write the trigger. “Data file not received by end of day 2” tells you when to act.
- Keep responses small. An action that takes ten minutes will get done; a plan that needs a week will not.
- Record what happened. Closed and occurred risks are proof of learning, so do not delete them.
Frequently Asked Questions
How many risks should a 14-day internship register contain?
Eight to twelve is practical. Fewer than eight usually means you have only listed obvious items; more than twelve becomes hard to review daily. Ten, as in the table above, is a sensible starting point.
What is the difference between a risk and an issue?
A risk is something that might happen. An issue is something that already has. When a risk occurs, mark it as occurred, move the action to your task list, and note what the response was.
Can I use the same register for a group project?
Yes, but give each risk one named owner and agree the scoring anchors together. Different people will otherwise score the same risk very differently, and the review will turn into an argument about numbers.
Should I score risks before or after my planned response?
Score the current exposure first, then re-score after the response is in place. Keeping both numbers shows the reviewer that your action changed something, which is the real purpose of the register.
What if my mentor disagrees with my scores?
Ask which anchor they think is wrong, and why. A disagreement of one point is normal. A larger gap usually means one of you has information the other lacks, which is useful to learn on day 2 rather than day 12.
Is a spreadsheet enough, or do I need project software?
A spreadsheet is enough. Use filters on the score column to sort the high risks to the top and conditional colouring for the three action bands.
Where should a risk about college documentation sit in the ranking?
Score it by what you would lose, not by how technical it is. If missing paperwork could prevent the work counting towards your course, impact is high, so it will often rank near the top even though it looks administrative.
How does the register help me when I start a free online internship track?
The 14-day length of the CareerSwami internship fits this exercise directly: draft the register on day 1, review on day 7, and close it on day 14. Use the same ten-row template and adjust the risks to your chosen track.
Ready to put this into practice?
Join the free two-week CareerSwami online internship in Project Management. The internship, the offer letter and the completion certificate are free.