Internship Weekly Log Template: Tasks, Skills Learned, Feedback, and Next Steps

A useful internship weekly log connects what you did with what you learned. It records tasks, evidence of skills practiced, feedback, and the next opportunity to improve.

That makes it different from a routine status report. Your supervisor may need to know whether a task is finished; your learning log should also show what you can now do, how independently you did it, and what still needs practice.

Use your institution's required form if one exists. The template below is a flexible working log you can adapt around those requirements.

Copyable internship weekly log

INTERNSHIP WEEKLY LEARNING LOG

Name:
Placement / team:
Week number:
Dates covered:
Supervisor:
Hours worked, if required:
Current learning objectives:

1. WORK AND CONTRIBUTIONS
Task / responsibility:
What I personally did:
Result or current status:
Evidence reference:
Level of support: observed / assisted / supervised / independent

2. SKILLS PRACTICED
Skill:
Situation in which I used it:
What I can demonstrate:
What remains difficult:

3. FEEDBACK
Date and source:
Feedback received, paraphrased or accurately quoted:
My understanding of the requested improvement:
Action I will take:

4. REFLECTION
One thing that worked:
One difficulty and how I responded:
What I would do differently next time:
Question to discuss with my supervisor:

5. NEXT WEEK
Learning objective:
Practice opportunity / next action:
Support or access needed:
How I will know I improved:

6. SUPERVISOR SUMMARY
Main contribution:
Learning progress:
Feedback action:
Decision or support requested:

Evidence and confidentiality check completed:

Repeat the task and skill fields only as needed. Three meaningful entries are usually more useful than an exhaustive account of every small action.

Completed fictional example

The following placement, people, tasks, hours, and feedback are entirely fictional.

Placement: Operations internship, Northbridge Design Studio
Week: 4, November 9–13, 2026
Supervisor: Maya, operations coordinator
Hours worked: 24, based on the example intern's time record
Learning objectives: Clean operational data accurately; write a concise issue summary; use feedback before the next submission.

Work and contributions

The intern did not claim to have redesigned the supplier process or saved a measured amount of money. Their contribution was a prepared review file and clearer information for the person making the decision.

Skills practiced

Data checking: I compared names and reference fields before flagging possible duplicates. I identified uncertain cases rather than merging records without approval. I still need help with entries that refer to different branches of the same supplier.

Written communication: I turned a list of purchase requests into a short summary. The first draft gave every item equal space. I can now explain why items awaiting an urgent decision belong at the top.

Meeting documentation: I recorded an owner and action for each decision. I confused a suggestion with an agreed action in one entry; the supervisor corrected it before circulation.

Feedback and response

Feedback, November 12: Maya asked me to lead the purchase summary with the three decisions needed, then place the background below them. This is a paraphrase, not a verbatim quotation.

Action: Reorder the next summary before review and check whether each opening bullet names a decision, owner, and required date.

Reflection

Keeping uncertain supplier matches separate worked well because it made the review easier to discuss. My main difficulty was deciding which purchase requests deserved attention first. Next time I will agree the priority rule before writing the full summary.

Question for supervisor: Should urgency follow the requested delivery date, the project dependency, or a combination of both?

Next week

Objective: Produce a clearer first draft of the purchase summary.
Practice: Prepare Tuesday's summary using the agreed priority rule.
Support: Fifteen minutes with Maya to confirm how blocked requests should be ranked.
Evidence of improvement: Compare whether the next review still requires the same structural rewrite. This is a practice check, not proof of complete mastery.

Turn activity into evidence of learning

“Used a spreadsheet” describes an activity. “Checked duplicate records, flagged uncertain matches, and applied an approved correction list” describes work you can explain and demonstrate.

Use this pattern:

I practiced [skill] by [specific action]. The evidence is [permitted reference]. I needed [support]. Next I will practice [remaining gap].

Record the support honestly. Observing a process, helping with it, and completing it independently are different stages of learning. The difference gives your supervisor useful information about what to assign next.

Evidence does not have to mean attaching confidential work. A safe internal reference, supervisor confirmation, or approved sanitized example may be enough. Follow the placement's rules before copying files into a personal system or submitting material to an external learning platform.

A concise supervisor summary

Your supervisor should be able to understand the week without reading every reflection. For the fictional example:

This week I prepared a supplier-duplicate review file, drafted the open
purchase-request summary, and recorded the team meeting actions.

I practiced data checking and concise operational writing under supervision.
Your feedback was to put required decisions before background information.
I will apply that structure to Tuesday's summary.

Please confirm the priority rule for requests blocked by missing information.

Ask for a specific decision or practice opportunity. “Any feedback?” is less focused than “Does this priority order match how you would assess the requests?”

Keep the log current without making it another project

Capture a few notes while the week is fresh: the task, the evidence reference, and one learning point. At the end of the week, choose the entries that connect to your objectives.

If every week records the same difficulty, change the practice plan. Repeatedly writing “need to improve communication” does not identify what to do. Ask to practice a specific behavior, such as opening the next update with the decision required.

In SelfManager.ai, daily tasks and comments can hold permitted work notes. Use the weekly log to interpret those notes against your learning objectives. It remains a manual learning record, not an accredited assessment or automatic proof of competence.

Common questions

Should the log include mistakes?

Include mistakes that reveal a useful learning point, with an accurate account of what happened and how you responded. Keep the focus on the work and improvement. Use the organization's normal reporting process for matters requiring immediate attention; do not wait for the weekly log.

What if I mostly observed this week?

Record what you observed, the questions you asked, and what you understand better. Then identify a suitable supervised practice opportunity. Do not describe observation as independent performance.

How long should each entry be?

Follow any placement requirement. Otherwise, write enough to connect action, evidence, feedback, and the next step. Repeating the full task history adds length without necessarily showing more learning.