Internship Weekly Report Format: Template, Daily Log and Samples
The internship weekly report format is a one-page record of your week: what you worked on, what came out of it, what you learned and what slowed you down, signed by your supervisor. Written every Sunday it takes 15 minutes; written at the end of the internship it takes days, and it shows.
Departments call it a weekly report, weekly progress report, internship diary, log book or log sheet. The content is nearly the same. If your department has its own format, use it and fill it with the content below.
Why departments and supervisors ask for weekly reports
- Proof of work. A certificate says you were there. Weekly reports show what you did, week by week.
- Supervision from a distance. Your faculty supervisor cannot visit the company, so the report is how they follow your progress.
- Early warning. If you have no real tasks, a report in week 2 lets someone fix it. A complaint in week 11 is too late.
- Your final report, half written. Twelve honest weekly reports are most of the material for it.
What goes in an internship weekly report format
| Field | What to write | Example |
|---|---|---|
| Header | Name, roll number, company, track, week number and dates | Week 3 of 12, 7 to 11 July |
| Supervisor | Company supervisor’s name and designation | [Name], Senior Developer |
| Hours | Days and hours worked | 5 days, 25 hours |
| Tasks completed | One line per task: verb, object, result | Built the login API; merged after review |
| Outcomes | What works now that did not on Monday | Login live on staging; 1 bug closed |
| Evidence | Commits, pull requests, screenshots, posts | PR #14, staging link, screenshot folder |
| Learning | One or two specific things you can now do | How refresh tokens expire and renew |
| Blockers | What slowed you, what you tried, who you asked | Waiting for client API keys; raised Tuesday |
| Next week | Two to four planned tasks | Password reset; auth tests |
| Sign-off | Supervisor signature or approval email | Signed and dated |
Internship weekly report format: copy-paste template
INTERNSHIP WEEKLY REPORT Name: [ ] Roll / Reg. No: [ ] Programme, semester: [ ] University: [ ] Company: [ ] Track: [ ] Week: [ ] of [ ] Dates: [ ] to [ ] Company supervisor: [Name, designation] Days / hours worked: [ ] 1. Tasks completed - [Verb + what + result] - [ ] 2. Outcomes and deliverables [What now exists or works that did not on Monday] 3. Evidence [Links to commits, PRs, designs, posts or a screenshot folder] 4. What I learned [One or two specific skills, a sentence each] 5. Blockers and help needed [Problem, what you tried, who you asked, status] 6. Plan for next week - [ ] Supervisor remarks: ____________________ Supervisor signature and date: __________
Internship daily report format (diary or log book)
Some departments want a daily diary or log book, on paper or online, instead of or as well as weekly reports. Even if yours does not, a two-minute daily log makes the weekly report easy.
Date | Hours | Task | Output / link | Notes, blockers [dd/mm] | [5] | [Set up project, read codebase] | [README notes] | [Node version mismatch, fixed] [dd/mm] | [ ] | [ ] | [ ] | [ ] [dd/mm] | [ ] | [ ] | [ ] | [ ] Supervisor initials (weekly): ______
Filled sample: week 3 of a web development (MERN) internship
An illustrative example for an intern on a booking app. Write yours from your own work.
Track: Web Development (MERN) Week: 3 of 12 Company supervisor: [Name], Senior Developer Days / hours worked: 5 days, 25 hours 1. Tasks completed - Built signup and login endpoints (Express, MongoDB) with hashed passwords and JWT; merged after code review. - Connected the React login form to the API, with validation and error messages. - Fixed the booking list showing past dates by adding a date filter to the query. - Wrote 6 Jest unit tests for the auth routes. 2. Outcomes Users can sign up, log in and stay logged in on staging. One reported bug closed. 3. Evidence PR #12 (auth API), PR #15 (login form), PR #16 (date fix); staging link; screenshots in /week-03. 4. What I learned How access and refresh tokens differ, and why the refresh token sits in an httpOnly cookie. How to answer review comments on the same branch. 5. Blockers Admin dashboard design not final, so admin routes are on hold. Raised with supervisor on Wednesday. 6. Next week - Password reset with expiring links - Admin routes once the design is approved - Tests for booking endpoints
Short sample: digital marketing intern, week 5
Tasks: Wrote and scheduled 9 Instagram and Facebook posts for a client's two-week calendar. Built a Meta lead-form campaign draft with 2 audiences; supervisor launched it Thursday. Summarised last month's page insights on one sheet. Outcomes: Calendar filled to month end. Campaign live; first results next week. Evidence: Calendar link, campaign screenshot, insights sheet. Learned: How to read cost per lead, and why carousels out-reached link posts on this page. Blockers: Product photos late from client; used approved stock for 2 posts. Next week: Report campaign results; draft 3 reel scripts.
How to describe tasks, outcomes, learning and blockers
A good report lets someone who was not there tell exactly what you did. Compare:
| Part | Vague | Specific |
|---|---|---|
| Task | Worked on the website. | Built the contact form with validation and email notification; merged in PR #21. |
| Task | Did SEO. | Rewrote title tags and meta descriptions for 12 service pages. |
| Outcome | Made good progress. | Login and signup work on staging; 2 of 3 planned tasks done. |
| Learning | Learned a lot about React. | Learned to lift state into a parent so two forms share data. |
| Blocker | Had some issues. | Server build failed on a Node version mismatch; fixed by pinning the version in .nvmrc. |
| Plan | Continue working. | Finish password reset and write tests for the auth routes. |
Start each line with a verb, name the thing you touched, and end with a result or a link.
Supervisor sign-off and keeping evidence
- Get sign-off every week. Send the report on Friday or Monday and ask for a signature or a one-line approval email.
- Keep a folder per week (week-01 to week-12) with screenshots, exported files and a list of commit, post or design links.
- Capture results, not just code: the working page, the published post, the dashboard number.
- Ask before sharing client work outside your department, and never include passwords or private data.
At Ezitech, each intern’s public profile on portal.ezitech.org lists completed tasks with dates, and a named mentor reviews work every week, so your task list and review notes already exist when you write the report your department wants. See the internship programme for how the 3 months work.
From 12 weekly reports to the final internship report
A 3-month internship gives you about 12 weekly reports, and they map onto the sections most departments’ final report formats include:
| Final report section | Take it from |
|---|---|
| Company introduction and your role | Week 1 report and your offer letter |
| Work done | Tasks and evidence, all weeks |
| Skills learned | “What I learned”, grouped by theme |
| Problems faced and solutions | Blockers, with how each was resolved |
| Results and contribution | Outcomes, with screenshots from your weekly folders |
| Conclusion | Your last two reports and supervisor remarks |
Our internship report format guide has the full structure and a free .docx template. Your coordinator will also want your internship letter from university and completion certificate on file.
Tools and a 15-minute Sunday routine
Google Docs (one heading per week) is easiest to share. Google Sheets suits a daily log: one row per day, filtered by week. Notion works if you like a page per week in a database. Then every Sunday:
- Minutes 1 to 5: read your daily log, commits, posts or task list.
- Minutes 6 to 10: fill in tasks, outcomes and evidence links; file the screenshots.
- Minutes 11 to 13: write one learning and any blocker.
- Minutes 14 to 15: write next week’s plan, export a PDF and send it for sign-off.
Web development interns can check each week against our 12-week web development internship plan.
Internship weekly report questions
How do I write a weekly report for an internship?
List each task as verb, object and result, add outcomes with evidence links, one thing you learned, any blocker and next week’s plan. Keep it to a page and get it signed the same week.
What is the difference between an internship diary and a weekly report?
A diary or log book records each day briefly, often by hand. A weekly report summarises the week with outcomes, learning and plans. Some departments ask for one, some for both.
How long should an internship weekly report be?
One page is enough for most weeks. If your department’s format sets fields or a page limit, follow it.
Who signs the internship weekly report?
Usually your company supervisor, and sometimes your faculty supervisor too. Your department’s format says which signatures it needs.
Can I write all my weekly reports at the end of the internship?
You can, but they will be vague, the dates will be guesses and your supervisor may refuse to sign twelve at once. Fifteen minutes a week is far less work.
What should I write if I did not finish my tasks this week?
Write what you finished, what is left, why, and your plan to close it. An honest blocker reads better than a report that hides one.
Related guides
Internship report format
The final report structure, with a free .docx template.
Internship certificate format
What a completion certificate should contain.
Internship letter from university
Request letter, NOC and acceptance letter templates.
Web development internship: 12-week plan
A week-by-week plan for a 3-month web internship.
Turn an internship into a full-time offer
Use your internship record to ask for a role.
Want weekly reviews built into your internship?
Ezitech’s 3-month internship has a named mentor reviewing your work every week, and a public profile listing your completed tasks with dates. Onsite in Rawalpindi or remote.