Lords University Students: Preparing Mentor Feedback Sessions in a Data Analytics Internship

To get useful mentor feedback in a 14-day data analytics internship, send a short, specific request before each session, record every comment in an action tracker, and convert each comment into a dated revision task. Then close the loop with a brief progress note. This guide gives you the template, the tracker, a worked example and a two-week schedule you can use as written.

Why feedback sessions matter more in a two-week data analytics internship

A two-week internship leaves little room for drift. If you spend six days cleaning a dataset the wrong way, you cannot recover that time later. Analytics work also hides its mistakes well: a join that duplicates rows, a filter that silently drops a category, or a chart with a truncated axis can all look fine until someone experienced reads the work.

That is what a mentor is for. But mentors are usually busy, and a vague “please review my work” message tends to get a vague “looks good” reply. Your job is to make feedback easy to give and easy to act on. Three habits do most of the work:

• Ask narrow questions. “Is my handling of missing values acceptable?” gets a better answer than “Is this okay?”
• Show evidence, not just conclusions. Share the notebook, sheet or query alongside the chart.
• Track what you do with each comment. Mentors give more time to people who visibly act on advice.

If you are still looking for a structured placement for this, the free two-week online internship from CareerSwami offers a 14-day format with an offer letter and a completion certificate after successful completion, across 26 tracks. The method below works for any short analytics internship, though.

A 14-day feedback rhythm for an analytics internship

Do not plan one big review at the end. Plan three short checkpoints, each tied to a stage of the work, plus a final wrap-up. Adjust the days to your mentor’s availability.

Keep each session to 15-20 minutes. Short, frequent sessions are easier for a mentor to agree to than an hour-long review.

Feedback-request template you can paste into a message

Send this 24 hours before each session. Replace the bracketed parts. It keeps the mentor’s reading time under five minutes.

Subject: Day [X] feedback request - [project name]

Hello [Mentor name],

Ahead of our session on [date/time], here is where I am.

1. Goal of this project: [one sentence]
2. What I completed since last time: [2-3 bullets]
3. What I want feedback on (max 3):
   a. [Specific question, e.g. "Is median imputation reasonable for the income column?"]
   b. [Specific question, e.g. "Does this bar chart answer the retention question clearly?"]
   c. [Specific question, e.g. "Is my SQL join on customer_id correct?"]
4. Files: [link to notebook / sheet / dashboard, view access on]
5. Where I am unsure: [one honest sentence]
6. Next step I plan if nothing changes: [one sentence]

Thank you,
[Name], [programme], Lords University

Two details matter here. Point 5 invites candid advice, and point 6 lets the mentor redirect you with one word if your plan is wrong.

Questions worth asking at each checkpoint

• Scope checkpoint: Is this question answerable with the data I have? What would you cut if I had only half the time?
• Data-quality checkpoint: Which cleaning decisions would you challenge? Are there outliers I should keep rather than remove?
• Findings checkpoint: What would a sceptical manager ask about this chart? Is my conclusion stronger than the evidence allows?
• Wrap-up: What is the one skill I should practise next? Is there anything in my report that is unclear to a non-technical reader?

Action-tracker sheet: columns and what each one does

Build this in Google Sheets or Excel. One row per comment, never one row per session. Splitting comments is what turns a conversation into a task list.

Rules for filling the tracker

1. Write the comment first, the interpretation second. Do not rewrite the mentor’s words into what you wished they had said.
2. If a comment is unclear, add a clarification question in the revision-task column and ask in the next message.
3. Rank correctness problems (wrong numbers, wrong joins) above presentation problems (colours, fonts).
4. If you decide not to act on a comment, mark it “declined” and write a one-line reason. Silence looks like neglect; a reasoned decline looks like judgement.

Turning raw comments into a revision list: a worked illustration

The following is an illustrative example, not a record of a real session. Suppose you are analysing a retail sales dataset and, after Checkpoint 2, your mentor says:

• “Your average order value looks high. Check for returns.”
• “Region column has inconsistent spellings.”
• “The dashboard is busy. What is the main message?”
• “Read about cohort analysis if you have time.”

Here is how those become tracker rows.

Notice what changed. Each vague remark now has a verb, a measurable output and a day. C4 is optional reading, so it is low priority but not ignored.

Writing the progress note after each session

A progress note is a short message sent within a day of the session. It confirms what you heard and shows what you will do. It also gives the mentor a chance to correct a misunderstanding before you spend time on it. Use this structure:

Subject: Progress note - Day [X] - [project name]

Hello [Mentor name],

Thank you for the session today. Summary:

Done since last session
- [Item, with link]

Feedback received and my plan
- C1: [comment in short] -> [task], by Day [N]
- C2: [comment in short] -> [task], by Day [N]

Not acting on (with reason)
- C5: [comment] -> [reason]

Questions for you
- [One clarification question]

Tracker status: [n] done, [n] in progress, [n] open
Link: [tracker URL]

Using the illustrative case above, the first note might read: “C1 and C2 are being fixed by Day 7, because they affect every downstream number. C3 follows on Day 10 once the numbers are stable.” That tells the mentor your sequencing logic, which is itself something they can comment on.

Final progress note for the end of the internship

On Day 13 or 14, send a closing version that includes the following:

• A count of comments received, closed and declined.
• The two or three changes that most improved the analysis, with before-and-after figures where you have them.
• What you would do with more time.
• A polite request for a short written comment on your work, if the mentor is willing. Do not ask for a reference you have not earned, and do not promise anything on the mentor’s behalf.

Lords University students: fitting mentor feedback into your own programme

Lords University describes itself on its About page as a private university in Alwar, Rajasthan, and states that it was established by a Rajasthan Legislative Assembly Act in 2018. Its Academics page lists a Computer Applications & IT department (Polytechnic, BCA, MCA, B.Tech) and a Management department (BBA, M.Com, MBA). Students from either group can use analytics skills, which makes the feedback routine above relevant whether your background is coding or business.

What the pages we can point to do not show is any internship, industrial training or project-work rule. There is no stated duration, credit value, evaluation method or position on online internships. So do not assume that a mentor’s comments, your tracker or a certificate will be accepted as part of your coursework. Treat this internship as extra practice unless your department confirms otherwise in writing.

It also helps to know where to look. The contact page lists the campus address at Chikani on the Alwar-Bhiwadi Highway and a Placement Cell email, but it gives no placement policy. The Academics page carries a general placement-assistance claim without data, so rely on your own evidence, such as the tracker and final report, rather than that line when you present your work to employers.

Verification steps for Lords University students

1. Email your department coordinator and ask whether any internship or project-work rule covers a voluntary online internship, and request the answer in writing.
2. Ask whether a mentor’s feedback or an external certificate can be recorded in any department file, and who signs it off.
3. Download the current 2026 brochure from the contact page and check whether it mentions internships for your programme.
4. Write to the Placement Cell (tpo@lordsuni.edu.in) asking whether they want to see project reports, and in what format.
5. Check your semester schedule so the 14 days do not clash with exams or practicals.
6. Keep every reply, because screenshots and emails are the proof you will need later.

Handling difficult feedback situations in analytics work

When the comment is vague

If a mentor says “make it better”, reply with two options: “Do you mean simplifying the charts or strengthening the evidence for the main finding?” Offering choices is quicker for them than composing an explanation.

When two comments conflict

One reviewer may want more detail while another wants a shorter report. Note both in the tracker, state your trade-off in the progress note and ask which should take priority for the audience.

When feedback arrives late

If a reply lands on Day 12, triage. Fix correctness issues first, document the rest as “next steps” in the final note, and do not rush a complete redo that you cannot check.

When the mentor is unavailable

Send the template anyway and ask for written comments on the three questions. Written replies are often more useful than a call because they can be pasted straight into the tracker.

Self-check scorecard for your feedback process

Score yourself at the end of Day 7 and again on Day 14. Give 0 for no, 1 for partly and 2 for yes.

A total of 13-16 means your process is solid. A score of 8-12 means one or two habits need tightening, usually the written request or the evidence links. Below 8, restart the tracker and rebuild it from your session notes.

Frequently Asked Questions

How many feedback sessions should I request in a 14-day data analytics internship?

Three short checkpoints plus a wrap-up is a realistic target: one around Days 1-2, one around Days 5-6, one around Days 9-10 and a closing conversation on Day 13 or 14. If the mentor can only give two slots, use the scope and findings checkpoints.

What should I send a mentor before a feedback session?

Send a short message with your goal, what you completed, up to three specific questions, view-access links to your files and one point where you feel unsure. Send it a day ahead so the mentor can read it without pressure.

How do I turn a comment like “improve the visuals” into a revision task?

Ask what the mentor noticed, then split the comment into measurable actions: limit the dashboard to four charts, add axis labels and units, and write a one-sentence headline. Put each action in its own tracker row with a day.

Should I act on every piece of mentor feedback?

Not necessarily, but respond to every one. Fix correctness issues first. If you decline a comment, such as one that needs data you do not have, mark it declined in the tracker and state the reason in your progress note.

What belongs in a progress note after a feedback session?

Include work completed, each comment with the planned task and day, anything you will not act on and why, a clarification question, and tracker counts for done, in progress and open. Keep it short enough to read in two minutes.

Will a Lords University department accept my tracker or mentor comments as coursework evidence?

That depends on a rule we cannot confirm from the pages cited here. Ask your department coordinator in writing whether a voluntary online internship, its report or its feedback records count for anything, and keep the reply.

How do I ask for feedback politely if my mentor replies slowly?

Keep the request small, give a clear deadline such as “by Day 6 evening so I can revise by Day 7”, and attach everything needed. If there is no reply, send one reminder with only your single most important question.

Can I use the CareerSwami internship to practise this feedback routine?

Yes, the 14-day structure suits the three-checkpoint rhythm described here. Plan your checkpoints at the start so that each falls in the stage of work where feedback changes the result most.

Related Data Analytics guides

• Patliputra University Students: Getting a Data Analytics Internship Without a Referral
• Central University of Himachal Pradesh Students: Analytics Internship Plan for Social Science Majors
• Assam Kaziranga University Students: Building a Dashboard Brief Before You Open Any Tool
• All Data Analytics internship guides