Internship & Apprenticeship Programs: An India Guide

Why Your Internship Program Deserves Real Structure

Most Indian SMBs discover early-career hiring by accident. A founder meets a bright final-year student at a campus event, a manager needs an extra pair of hands for three months, and suddenly there is an "intern" sitting in the office with no contract, no defined scope, no mentor, and a stipend that gets paid out of petty cash whenever someone remembers. Six months later nobody can say whether that internship program produced anything of value, whether the student's work belongs to the company, or whether the arrangement was even correctly classified.

That casual approach is getting harder to sustain. Skilling and the formalisation of early-career hiring have become live policy themes in India, and the ongoing transition to the consolidated labour codes has pushed employers of every size to be far more deliberate about who is on their premises, in what capacity, and under which set of obligations. At the same time, the talent economics have shifted: a well-run internship program is now one of the cheapest, lowest-risk ways for a 40-person company to build a pipeline of junior engineers, analysts, designers and sales associates who already know the product, the codebase and the culture on day one of full-time employment.

This guide is written for HR managers, founders and campus teams at Indian SMBs and startups. It covers the four categories you will encounter — intern, apprentice, management trainee and fixed-term employee — and how they differ on contract, pay, statutory treatment and conversion. It covers designing and budgeting an internship program, sourcing and selecting candidates, the agreement essentials, mentoring, curriculum, evaluation rubrics, conversion to full-time, offboarding, and the HR admin that holds it all together.

One important note before we start. Rates, thresholds, scheme eligibility criteria, portal processes and statutory obligations in this area change frequently and vary by state, sector and establishment type. Nothing here is legal advice. Treat every statutory point in this article as a prompt to verify the current position on the relevant official government portal or with a qualified employment lawyer or chartered accountant before you act.

What an Ad-Hoc Intern Actually Costs You

It is tempting to think of unstructured interns as free or nearly free. They are not. The costs are simply hidden in places your P&L does not show.

Manager time evaporates. An intern without a scoped project generates a constant stream of "what should I do now?" interruptions. A senior engineer who loses forty minutes a day to unscoped intern management for twelve weeks has burned roughly two full working weeks. At an SMB where that engineer's fully loaded cost is significant, this dwarfs the stipend.

Nothing ships. Ad-hoc interns are handed low-stakes busywork precisely because nobody has thought through what they could safely own. The intern leaves with no portfolio piece, the company leaves with no artefact, and the only output is a certificate nobody reads.

Your employer brand takes a quiet hit. Students talk. Campus placement cells keep informal notes on which companies waste their students' time. Two bad cohorts and your access to the good colleges in your city narrows considerably.

Classification risk accumulates. When an "intern" works full days on core production work for nine months at a fixed monthly payment with no learning plan, no academic linkage and no defined end date, you are inviting a very awkward conversation about whether that person was in substance an employee all along — with consequences for social security contributions, notice, gratuity accrual and more.

Conversion fails. The single biggest return on an internship program is a cheap, low-risk, high-signal hiring funnel. Ad-hoc programs convert almost nobody, because neither side has enough evidence to make the decision.

A structured internship program flips all five of those. It costs more to design once and far less to run every cycle after that.

The Four Categories: Intern vs Apprentice vs Trainee vs Fixed-Term Employee

The vocabulary in Indian workplaces is loose. People say "intern," "trainee," "apprentice" and "GET" almost interchangeably. Legally and administratively they are not interchangeable at all, and the distinction drives your contract, your payroll treatment and your risk.

Here is how the four categories generally differ. Verify the specifics against current law and your own facts before relying on any row.

A few practical readings of that table.

An intern is a learner first. The defining feature of a genuine internship is that the learning is the point and the work output is the by-product. The engagement is time-bound, usually tied to an academic calendar, supervised, and structured around a curriculum. If you strip out the learning and keep only the output, you no longer have an intern.

An apprentice sits inside a statutory framework. The Apprentices Act and the national apprenticeship schemes create a formal, registered relationship with prescribed obligations around contract registration, training curriculum, records, stipend and duration. This is not something you improvise. Establishments considering apprentices should check the current eligibility criteria, employer obligations, designated trades and portal processes on the official government apprenticeship portals, because these are periodically revised.

A management trainee is an employee wearing a training label. If you hire someone on your payroll, give them a joining date, a salary and a designation of "Management Trainee" or "Graduate Engineer Trainee," they are an employee from day one for practically all purposes. The trainee tag governs their development plan and pay band, not their legal status.

A fixed-term employee is a full employee with an end date. The labour code framework has given fixed-term employment a clearer shape, including expectations that fixed-term employees receive benefits comparable to permanent employees doing similar work, subject to applicable conditions. If your "six-month intern" is actually doing a regular job for a fixed period, a fixed-term employment contract is very likely the honest instrument.

How Misclassification Creates Risk

Misclassification is rarely malicious at an SMB. It happens because the cheapest-looking label gets applied by default. The risks that follow are real.

• Retrospective statutory exposure. If an engagement is later characterised as employment, contributions, benefits and dues may be assessed for the whole period, often with interest and penalties.
• Termination disputes. A person who believes they were an employee may contest an abrupt end of engagement, and the absence of a clean contract works against you.
• IP ownership gaps. Without a written assignment, ownership of code, designs and content produced by a non-employee can be genuinely unclear. This surfaces painfully during due diligence.
• Confidentiality gaps. Interns often see customer data, pricing and roadmaps. No agreement means no enforceable obligation.
• Due diligence findings. Investors and acquirers ask for the complete list of people who worked at the company and under what contracts. Twenty undocumented interns is a diligence item nobody wants.

The defence is simple and boring: pick the right category for the actual facts, paper it properly, keep the records, and pay on time.

Designing Your Internship Program: Objectives First

Before headcount, before budgets, before campus outreach, write down why you are running an internship program at all. The honest answer is usually one or more of these, and they lead to different designs.

1. Hiring pipeline. You want to convert. This design favours longer internships (10 to 24 weeks), real project ownership, heavy mentoring, and a rigorous evaluation rubric. Cohort size is small and selective.

2. Capacity augmentation. You need throughput on well-defined, bounded work — annotation, QA, research, data cleanup, content. This design favours shorter engagements, standardised task packets, clear quality gates, and less individual mentoring investment.

3. Employer brand and campus presence. You want visibility with target colleges. This design favours visible cohort projects, demo days, certificates, and alumni engagement.

4. Social and skilling contribution. You want to expand access to opportunity, often in tier-2 and tier-3 towns. This design favours structured curriculum, foundational skill-building, and partnership with training institutions — and may point toward the statutory apprenticeship route rather than internships.

Write the objective in one sentence, attach one number to it, and put both in the program charter. For example: "Our internship program exists to generate junior engineering hires; we will convert at least 40 percent of each cohort into full-time offers." Everything downstream — how many, how long, who mentors, how you evaluate — flows from that sentence.

Headcount Planning and Manager Capacity

The binding constraint on an internship program is almost never budget. It is mentor bandwidth.

A workable planning rule for most SMBs: one mentor supports at most two interns, and mentoring consumes roughly four to six hours of that mentor's week per intern during the first fortnight, settling to two or three hours a week thereafter. If you have six willing, capable mentors, your cohort ceiling is around eight to twelve, not twenty-five.

Build your headcount plan like this.

1. List candidate mentors by name. Not teams — names. A person who has not agreed is not a mentor.
2. Confirm their availability window against release calendars, audits, festival season and their own leave plans.
3. Multiply available mentors by your ratio to get the cohort ceiling.
4. Check seating, devices and access. Laptops are often the real bottleneck at an SMB. Decide early whether interns get company devices or use their own, and what that means for security.
5. Reserve buffer. Assume ten to fifteen percent of accepted interns will not join or will drop out early. Over-offer accordingly, within your ceiling.

Project Scoping: The Difference Between a Good and Bad Internship

If you do one thing well, do this. Interns who own a real, bounded piece of work produce value, learn fast, and give you genuine hiring signal. Interns without a project produce nothing and tell you nothing.

A good intern project has six properties.

• Bounded. Completable by a competent beginner in roughly 60 to 70 percent of the internship duration, leaving room for onboarding and slippage.
• Real. Someone in the business actually wants the outcome. If the project were cancelled, a real person would be disappointed.
• Non-blocking. The company's critical path does not depend on an intern shipping on time. This protects both sides.
• Observable. Progress can be seen weekly — a demo, a dashboard, a document, a merged pull request.
• Documented. A one-page brief exists before day one: context, problem, expected output, success criteria, data and tools available, out-of-scope items.
• Stretchy. Has an obvious "if you finish early, do this next" extension so strong interns are not left idle.

Write these briefs four to six weeks before the cohort starts. The single most common cause of a failed internship program is briefs written on day one while the intern watches.

Examples of well-shaped SMB intern projects: build an internal dashboard consolidating three existing reports; write the automated test suite for one module that currently has none; run a structured competitor teardown across fifteen products and produce a positioning memo; clean and standardise three years of vendor master data; produce and publish a set of help-centre articles for the ten most common support tickets; instrument the signup funnel and produce a drop-off analysis.

Duration and the Cohort Calendar

Indian academic calendars are not uniform, but they are predictable enough to plan around. Most institutions create three natural intake windows.

Two design decisions matter here.

Cohorts beat trickle. Bringing in six interns on the same Monday costs less total effort than six interns starting on six different Mondays. You run onboarding once, you run the curriculum once, and the interns support each other. Trickle intake also makes evaluation inconsistent.

Twelve weeks is the sweet spot for conversion. Under eight weeks and you barely get past ramp-up. Beyond sixteen weeks and the engagement starts to look, in substance, like employment — which may be perfectly fine, but then use the right instrument. If you regularly need six-plus months of full-time output, consider a fixed-term employment contract or the apprenticeship route instead of stretching an internship label.

Build a cohort calendar and work backwards. For a summer internship program starting in mid-May, a realistic timeline is: project briefs drafted by early February, campus outreach and applications in February, selection in March, offers rolled out by end of March, documentation and pre-onboarding in April, start in May.

Sourcing Interns in India: Four Channels That Work

You do not need a large campus budget. You need consistency in three or four channels.

1. Direct college relationships. Pick three to six colleges in your city and build real relationships with the training and placement officers. TPOs value predictability far more than brand: a company that comes back every year with the same clear ask, pays stipends on time, and issues certificates promptly gets first call on good students. Offer something back — a guest lecture, a workshop, a resume clinic, a project mentorship for a final-year team.

2. Internship and job portals. The general job boards and the internship-specific platforms give you volume and reach beyond your city. Expect a heavy application load and plan a filtering mechanism before you post. Volume without a filter is worse than no volume.

3. Employee referrals. Your junior employees graduated recently and know good juniors. A small referral incentive for interns who successfully complete — not merely who join — is cheap and works well.

4. Alumni of your own program. Interns who did not convert but performed well are excellent sources of referrals, and some become strong candidates a year later when they graduate. This is why offboarding well matters.

Two channels worth a mention: hackathons and open-source or community contributions can produce exceptionally well-matched candidates for technical roles, because you see the work before you see the resume. And for the apprenticeship route specifically, industrial training institutes and polytechnics are the natural partners, and the official apprenticeship portals include mechanisms to connect establishments with candidates. Verify current portal functionality and processes directly, as these are updated periodically.

A Lightweight Selection Process

The classic SMB mistake is running an interview loop designed for senior hires on a 20-year-old with no work history. It filters for confidence and coaching, not potential.

A proportionate four-stage process for hiring interns in India looks like this.

Stage 1: Structured application (10 minutes of candidate time). Ask for a resume plus three short written answers. Good questions: "Describe something you built or organised and what went wrong"; "Which part of this role are you least prepared for?"; "What do you want to be able to do by the end of this internship that you cannot do now?" These answers filter better than CGPA.

Stage 2: A small work sample (60 to 120 minutes of candidate time). A short take-home that mirrors real work. Keep it strictly under two hours — anything longer is exploitative and depresses your acceptance rate. Publish a clear rubric internally so two reviewers score the same submission similarly.

Stage 3: A conversation (30 to 45 minutes). Walk through their work sample, one past project, and one hypothetical. Assess curiosity, coachability, communication and ownership. Have two interviewers where possible, and write scores independently before discussing.

Stage 4: Mentor fit check (15 minutes). The person who will actually mentor them should speak to them before the offer. A mentor who did not choose their intern rarely invests properly.

Score on a fixed set of four or five attributes, record the scores in your ATS or HRMS, and make the decision from the scores. This matters for fairness and it matters if anyone ever asks you to justify selection decisions.

The Internship Agreement: What It Must Contain

Every intern signs a written agreement before day one. No exceptions, including for founders' relatives and "just two weeks" arrangements. A sound internship agreement for an Indian SMB typically covers the following.

• Parties and nature of engagement. Names the company and the intern, states that this is a time-bound internship for learning purposes and does not constitute employment, and does not create any obligation of employment on either side.
• Duration. Start date and end date, plus how extension works if both sides want it.
• Location and working hours. On-site, hybrid or remote; expected daily hours; expectations around holidays and leave; whether attendance is tracked.
• Stipend. Amount, frequency, payment date, the mode of payment and the conditions attached (for example, pro-rating for partial months and treatment on early exit).
• Reporting and mentorship. Named mentor or supervisor and the reporting line.
• Scope of work. A short description or a reference to an attached project brief.
• Confidentiality. Definition of confidential information, obligations during and after the internship, and return or deletion of materials at the end.
• Intellectual property assignment. Clear assignment to the company of work product created during and in connection with the internship, with a cooperation clause for any further documents needed. This clause is not optional. Without it, ownership arguments become genuinely difficult, especially for non-employees.
• Data protection and acceptable use. How company systems, customer data and devices may be used, and what happens on exit.
• No-employment clause. Explicit statement that completion does not entitle the intern to employment, and that any future offer will be a separate agreement.
• Termination. Either party may end the internship with short notice; company may end immediately for misconduct or breach; consequences for stipend and certificate.
• Certificate. What the intern receives on satisfactory completion and what "satisfactory" means.
• Governing law and jurisdiction.
• Emergency contact and declarations. Including a declaration of current enrolment status where relevant, and any conflict-of-interest disclosure.

Have a lawyer review the template once. Then reuse it for every cohort, changing only the schedule (name, dates, stipend, project, mentor). A reviewed template used consistently is worth far more than bespoke documents drafted in a hurry.

For apprentices, the instrument is different: a statutory apprenticeship contract in the prescribed form, registered as required under the applicable framework. Do not substitute your internship template. Check the current prescribed format and registration process on the official portal.

Stipend Strategy and a Worked Cost Model

Should you pay interns? For any engagement of meaningful duration where the intern is doing real work on your premises or systems, yes. Unpaid internships narrow your pool to students who can afford to work for free, which is both unfair and bad for quality. They also make the "this is genuinely a learning engagement" story harder to tell if anyone examines it.

How much? Stipend levels in India vary enormously by city, function, seniority and sector, and any specific number quoted in an article dates badly. Set yours using a process rather than a benchmark someone else published.

1. Ask your target colleges' placement cells what comparable companies paid last cycle. TPOs will usually tell you, and their data is current and local.
2. Ask your own recent junior hires what they were offered as students.
3. Check current listings on internship portals for the same role, city and duration.
4. Anchor to your own junior salary band. A common internal logic is to set the monthly stipend as a fraction of the monthly cost-to-company of the entry-level role the internship feeds into, on the reasoning that an intern delivers a fraction of the output.
5. Decide your position — at, below or above the local median — and be able to explain why.

Whatever you land on, pay it on a fixed date every month, exactly like payroll. Late stipends are the fastest way to destroy an internship program's reputation on campus.

A worked example: budgeting a six-intern summer cohort

The figures below are illustrative placeholders, not market rates. Replace every number with your own researched inputs. The purpose is to show the shape of the model and the line items SMBs forget.

Assume a 12-week summer internship program, six interns, hybrid working, one city.

Now put that against outcomes. Suppose three of the six convert to full-time offers and all three join.

• Fully loaded cost per converted hire: 6,98,800 / 3 = Rs 2,32,933
• Direct cash cost per converted hire: 4,57,600 / 3 = Rs 1,52,533

Compare that to what you would pay an external recruitment agency for three junior hires, plus the ramp-up cost of someone who has never seen your codebase or your customers. In most SMBs the internship program wins on both cost and quality of match — but only if the conversion rate is real. At a 1-in-6 conversion rate the same program costs nearly Rs 7 lakh per hire and you should redesign it.

Sensitivity: what conversion rate does to your cost per hire

The lesson is not "convert everyone." It is that conversion rate is the dominant variable in program economics, and that selection quality and project quality — not stipend level — are what move it.

Payroll and Statutory Treatment: What to Verify

This is the section where you should be most careful and least willing to accept generic internet guidance, including this article's.

The statutory treatment of stipends and of interns, apprentices and trainees in India depends on a set of facts that differ from company to company: the substance of the relationship, the size and nature of your establishment, the state you operate in, the sector, whether the person is engaged under the statutory apprenticeship framework, and the current position under the applicable central and state legislation as the labour codes are implemented. Rates, thresholds and coverage criteria are revised from time to time.

Here is the honest, practical framing.

Determine substance, not label. The starting question is always whether the relationship is, in substance, a genuine learning engagement or employment. Regulators and courts look at duration, control, the nature of the work, whether the person does the same work as employees, whether there is a real training component, and academic linkage.

Then work through the checklist with a qualified advisor. For each engagement type you plan to use, get a written view on:

• Whether stipend payments attract provident fund, employees' state insurance or other social security contributions in your specific circumstances.
• Whether any tax deduction at source applies to stipend payments in your facts, and how the payment should be reported.
• Whether professional tax applies in your state to the payments you are making.
• Whether minimum wage legislation applies to the engagement, and how that interacts with the category you have chosen.
• What the applicable shops and establishments act in your state requires in terms of hours, weekly off, records and registers for people on your premises.
• Whether the person must be included in any statutory registers, returns or headcount thresholds.
• For apprentices, what the current apprenticeship framework requires on contract registration, prescribed stipend, records, returns and duration, and what obligations attach to establishments of your size.
• Gratuity, leave and other benefit accrual questions for anyone you classify as a fixed-term employee.

Document the answer. Keep the advice on file with the date. When rules change or your headcount crosses a threshold, revisit it. A one-page internal note saying "as of [date], based on advice from [advisor], we treat intern stipends as follows" is worth enormous amounts during an audit or a diligence process.

Run stipends through a system, not a bank app. Whether or not stipends run through your formal payroll cycle, they should be processed with the same discipline: a register of who is owed what, attendance or completion evidence, an approval step, a payment record, and a payslip-equivalent statement to the intern. This is exactly what an HRMS is for, and it also makes the eventual accounting and audit trail painless.

National Apprenticeship Schemes: What SMBs Should Know

India's apprenticeship framework rests on the Apprentices Act and is operationalised through national apprenticeship schemes and official portals administered by the relevant ministries. For SMBs, the headline is that this framework exists specifically to make structured, on-the-job skilling economically viable for employers, including through support mechanisms for participating establishments.

Because the details — eligibility, designated and optional trades, prescribed stipend rates, any employer support or reimbursement mechanisms, registration steps, record-keeping and return obligations, and obligations triggered at particular establishment sizes — are set out in the legislation, rules and scheme guidelines and are periodically revised, this article deliberately does not quote figures, percentages or section numbers. Do not rely on numbers you find in blog posts, including recycled ones. Go to the official apprenticeship portals and, where the answer matters, take professional advice.

What you can plan for structurally.

• Registration comes first. Establishments generally need to be registered on the relevant portal before engaging apprentices, and apprenticeship contracts are registered as prescribed.
• Trades and curriculum are defined, not invented. Apprenticeship training follows prescribed trades and curricula rather than a job description you write yourself.
• Records and returns are part of the deal. Expect obligations around maintaining training records and filing periodic returns.
• Stipend is prescribed, not negotiated. The framework sets out how apprentice stipends are determined and revised.
• There is a defined completion outcome. Apprentices who complete may receive a recognised certificate, which is one of the genuine advantages of this route for candidates.
• Obligations can scale with headcount. Whether an establishment is required to engage apprentices, and in what proportion, depends on criteria that change; check where your establishment currently stands.

When does the apprenticeship route suit an SMB better than an internship program? Broadly, when you need longer-duration, hands-on skill development in operational, technical or trade roles; when you want a recognised certification outcome for the candidate; and when you are building a repeatable pipeline into roles that do not require a specific degree. Internships suit shorter, project-based, knowledge-work engagements tied to academic calendars.

Many SMBs eventually run both: an internship program for their engineering, product, design and analytics pipeline, and apprenticeships for operations, support, manufacturing or field roles.

Pre-Onboarding and Week One

The gap between offer and joining is where internship programs quietly lose people. Students accept multiple offers and drop the ones that go quiet. Fill that gap.

Between offer and joining:

• Send the signed agreement, a welcome note and the joining checklist within 48 hours of acceptance.
• Collect documents once, digitally: identity proof, address proof, bank details for stipend payment, college identity card or proof of current enrolment where relevant, a passport photograph, and emergency contact details. Collect only what you need and store it securely.
• Send a short pre-read pack two weeks ahead: what the company does, who the customers are, the product in ten minutes, and any tool or language they should be comfortable with.
• Have the mentor send one personal message a week before the start date. This single act measurably reduces drop-off.
• Create accounts, provision devices and set up access before day one, not on day one.

Week one, day by day. A tight first week does more for output than any amount of mid-programme correction.

Two non-negotiables in week one: every intern completes the safety, security, confidentiality and workplace conduct briefings and this is recorded; and every intern leaves Friday with a written project plan they wrote themselves. If they cannot articulate the project, the brief was not good enough — fix it in week two, not week eight.

Mentors and Buddies: The Engine of the Program

An internship program is a mentoring program with a stipend attached. Get this wrong and nothing else matters.

Separate the two roles.

• The mentor is accountable for the intern's work: sets the project, unblocks, reviews output, gives feedback, writes the evaluation and makes a conversion recommendation. Usually a senior individual contributor or a team lead.
• The buddy is accountable for the intern's experience: answers the "silly" questions, explains unwritten norms, has lunch with them in week one, and notices when someone is struggling. Usually a junior employee, often a former intern themselves.

Splitting these roles means the intern has a safe place to admit confusion without it going into their evaluation.

Publish mentor expectations in writing. A mentor charter for a 12-week internship program might read:

• One 45-minute one-to-one every week, at a fixed time, never cancelled without rescheduling in the same week.
• One 15-minute daily check-in in weeks one and two, tapering after.
• Written feedback within two working days on any submitted work.
• A written mid-point review at week six and a final review in the last week.
• Escalate to the program manager within 48 hours if the intern is off track, disengaged, or if there is any conduct concern.
• Attend the demo day and the cohort closing.

Support your mentors. Most first-time mentors at an SMB have never been taught to give developmental feedback. A 90-minute mentor briefing before the cohort starts — covering how to scope work, how to give specific feedback, how to avoid doing the work for them, what to escalate, and what unconscious bias looks like in evaluation — pays for itself immediately.

Recognise mentoring. Log mentor hours. Reflect mentoring in performance conversations. Thank mentors publicly at the closing event. Mentoring that is invisible in the performance system stops happening by the third cohort.

A 12-Week Internship Curriculum Outline

Use this as a skeleton and adapt it to function. The structure matters more than the specific content: a defined arc from context, to supervised contribution, to independent ownership, to handover.

Weeks 1–2: Orientation and first contribution. Company, product and customer context. Tooling and environment. Security and conduct training. A deliberately small first task that ships within the first ten days — a documentation fix, a small bug, a single report. The goal is one visible win early, because early wins drive engagement for the rest of the programme.

Weeks 3–4: Guided project work. Intern begins the main project under close supervision. Weekly plan reviewed by mentor. Introduce the company's craft standards — code review conventions, writing style guide, data hygiene, whatever applies. Add one cross-functional exposure session per week: a sales call recording, a support queue hour, a customer interview.

Weeks 5–6: Increasing independence and mid-point review. Intern owns their weekly plan; mentor reviews outcomes rather than directing steps. Week six is the formal mid-point review with a written rubric score and an explicit statement of whether they are on track for a pre-placement offer, and what would have to change.

Weeks 7–9: Ownership and depth. The intern drives the core of the project. Introduce a second, smaller stretch task to test breadth. Have them present to a stakeholder outside their immediate team — this is the single best test of communication and of whether they understand the "why."

Weeks 10–11: Completion, quality and documentation. Feature complete or analysis complete. Testing, edge cases, review cycles. Written documentation and a handover note that a stranger could follow. This week separates strong candidates from average ones more reliably than any interview.

Week 12: Demo, review, decision, offboarding. Cohort demo day to a broad internal audience. Final written evaluation. Conversion decision communicated. Exit interview, feedback survey, asset return, access revocation, certificate issue, alumni group invitation.

Layer three lightweight recurring elements across the whole programme: a 30-minute weekly cohort session (a leader speaks, or interns present to each other), a peer learning pair-up so interns review each other's work, and a shared cohort channel where questions are answered publicly so everyone learns once.

Evaluation: A Simple Rubric That Holds Up

Evaluate on a small number of observable dimensions, scored the same way for every intern, at mid-point and at the end. Five dimensions on a four-point scale is enough.

Rules that make the rubric worth having.

• Mentor scores first, independently. Then a calibration conversation across mentors before anything is shared with interns. Calibration is where you catch the mentor who scores everyone a 4 and the one who scores everyone a 2.
• Every score needs one piece of evidence. "3 on communication — his week-seven stakeholder presentation was clear and he handled two hard questions well." No evidence, no score.
• Mid-point review must be honest. A mid-point review that says "doing great" followed by a final review that says "not converting" is a failure of management, not of the intern. Tell people at week six exactly where they stand.
• Score the person, not the project. An intern given a badly scoped project should not be penalised for it. That is a program defect.
• Store scores in your HRMS. They are the raw material for your conversion decisions, your program ROI analysis, and any future rehire consideration.

Converting Interns to Full-Time: Doing It Fairly

Intern to full-time conversion is where the internship program pays for itself. It is also where SMBs are sloppiest.

Decide the bar before the cohort starts. Write down what earns a pre-placement offer: for example, an average rubric score of 3.0 or above with no dimension below 2, plus a stated headcount need in a team that wants them. Publishing the bar to interns at kickoff is one of the highest-trust things you can do.

Separate three distinct questions.

1. Did this person meet the performance bar? A rubric question, answered by evidence.
2. Do we have an approved role for them? A budget and workforce planning question, entirely separate.
3. When can they actually start? An academic question — most students cannot join until they graduate.

Conflating these produces the worst outcome: a strong intern told "we'll see" and left dangling until they accept something else.

Make the offer early and concretely. For final-year interns finishing in, say, June, deciding in week twelve and issuing a written offer within a week is a genuine competitive advantage. Include the role, the compensation, the location, the start date (or a start window tied to graduation), the conditions such as degree completion and background verification, and a response deadline that is generous rather than coercive.

Bridge the gap. If the offer start date is six months after the internship ends, keep the relationship warm: add them to a low-traffic alumni channel, invite them to a product launch, send a note when something they built ships, and have their future manager check in once a quarter. Silent gaps are where accepted offers go to die.

Handle non-conversion with respect. Most interns will not convert, and most non-conversions are about headcount rather than ability. Say so plainly. Give them the written evaluation, tell them specifically what would make them a strong candidate later, offer to be a reference, and mean it. An intern who was turned down kindly and honestly refers people to you for years.

Get the paperwork right at conversion. Conversion is a new relationship, not a continuation. Issue a fresh employment contract, complete standard onboarding including statutory enrolments as applicable, set the correct start date for benefits and leave accrual, and confirm with your advisor how, if at all, the internship period is treated for any service-linked entitlements. Do not assume it carries over, and do not assume it does not — confirm and document.

Offboarding, Certificates and the Alumni Pipeline

The last week of an internship is the week most companies drop the ball. It is also the week that determines what interns say about you for the next five years.

A complete intern offboarding checklist:

• Final rubric evaluation completed and shared with the intern in a conversation, not just a PDF.
• Project handover: documentation, code merged or archived, credentials handed over, a written handover note, a named owner for whatever they built.
• Exit interview: fifteen minutes, three questions — what worked, what did not, would you recommend this internship program to a friend and why.
• Anonymous cohort feedback survey covering project quality, mentor availability, learning, logistics and stipend timeliness.
• Assets returned: laptop, access cards, any hardware. Logged.
• Access revoked on the last day: email, code repositories, cloud consoles, CRM, shared drives, internal chat, VPN. Every one, verified.
• Final stipend released on the normal payment date, pro-rated correctly, with a statement.
• Certificate issued within one week of completion, with the correct dates, project title and mentor sign-off. Prompt certificates are remembered; delayed ones become a grievance.
• Recommendation or reference commitment recorded, so the mentor remembers what they promised.
• Alumni list updated in your HRMS with their contact details, evaluation scores, conversion decision and rehire eligibility.

The alumni pipeline is an underrated asset. A four-year-old internship program with 60 alumni is a warm network of candidates, referrers, future customers and future colleagues. Maintain it deliberately: a low-volume alumni channel, a note when the company hits a milestone, and a message every hiring season telling them what roles are open.

Measuring Program ROI

If you cannot measure your internship program, you cannot defend its budget. Track a small set of metrics per cohort and compare across cohorts.

Two comparisons make the numbers meaningful. First, cost per converted hire versus your cost per hire through other channels for the same roles. Second, 12-month retention and performance of intern-converted hires versus externally hired juniors. In most SMBs that run a serious internship program for two or three years, converted interns retain longer and ramp faster — and that is the argument that wins the budget conversation.

How an HRMS Carries the Admin Load

The reason most SMB internship programs stay ad-hoc is administrative friction. Every cohort means chasing documents over email, tracking attendance on a spreadsheet, making individual bank transfers, and typing certificates by hand. Doing that three times a year for a dozen interns is genuinely painful, so people stop doing it properly.

An HRMS removes most of that friction. Practically, here is what should be systematised.

Separate records with the right classification. Interns, apprentices, trainees and fixed-term employees should each be a distinct employment type in the system, with their own fields, workflows, document requirements and reports. This is the single most important configuration decision, because it drives everything downstream — who appears in which statutory report, who accrues which benefits, and who shows up in headcount.

Digital onboarding and document collection. Send a link, the intern uploads identity proof, bank details, enrolment proof and photograph, e-signs the internship agreement, NDA and IP assignment, and the system stores everything against their record with an audit trail. No email attachments, no lost PDFs.

Attendance and leave, appropriate to the category. Interns typically need simple presence tracking rather than full shift management: check-in, check-out, geo or IP-based verification for hybrid arrangements, and a simple leave request flow with the mentor as approver. This record also matters if stipend is pro-rated for absence.

Stipend runs on a schedule. Process stipends as a defined run with the correct treatment for the category, pro-rating for partial months, an approval step, bulk bank transfer or payment file, and a stipend statement to each intern. Same date, every month, no exceptions.

Mentor allocation and check-ins. Map each intern to a mentor and buddy in the system, schedule the recurring one-to-ones, and log completion so the program manager can see at a glance which mentor pairs have gone quiet.

Structured evaluations. Configure the rubric as a form, trigger it automatically at mid-point and end of programme, route it to the mentor, and store the scores against the intern record for calibration, conversion decisions and cohort analytics.

Certificates and letters. Generate internship completion certificates, letters of recommendation and pre-placement offer letters from templates with merged fields, so week-twelve admin is minutes rather than days.

Conversion without re-entry. When an intern converts, the record should transition to a full employee record carrying forward the existing data — no re-collection of documents, no duplicate profile, no lost history.

Alumni and rehire tracking. Keep completed interns in a searchable alumni pool with their evaluation scores and rehire eligibility flags, so next year's hiring manager can find them.

Compliance-ready records. Registers, document retention, access logs and a clean audit trail — so that when an auditor, an investor or a labour inspector asks who worked here in the last three years and under what terms, the answer takes ten minutes rather than ten days.

This is exactly the kind of repetitive, deadline-bound, document-heavy work that SMB HR teams should not be doing by hand — particularly during a labour-code transition where accurate classification and clean records matter more than they used to.

Common Mistakes SMBs Make

Hiring interns without a written project brief. The brief is the program. Without it, you are paying a stipend for the privilege of interrupting your senior staff.

Treating the internship as a nine-month unpaid trial. Long, low-paid, open-ended engagements doing core production work are the classic misclassification pattern. If you need the output for nine months, hire the person properly.

No written agreement. Especially with referrals from friends and family, where the informality feels natural. This is where IP and confidentiality gaps come from.

Missing the IP assignment clause. Discovered years later during diligence, when the intern who wrote a key module is unreachable.

Late or irregular stipends. The single fastest way to lose a campus relationship. Treat stipend dates like payroll dates.

Mentors who did not volunteer. Assigning mentorship as a punishment or a default produces disengaged mentors and abandoned interns.

Assessing on personality rather than evidence. Without a rubric, evaluations drift toward "I liked them," which is both unfair and a poor predictor.

No mid-point honesty. Interns who hear "great job" for eleven weeks and "no offer" in week twelve tell everyone about it.

Conflating performance and headcount in the conversion message. If you have no budget, say you have no budget. Do not let a strong performer conclude they were not good enough.

Onboarding on day one instead of before day one. Interns who spend their first three days waiting for a laptop and a login lose a quarter of a short internship.

Copying stipend rates or scheme details from blog posts. Rates, thresholds and scheme rules change. Verify on official portals every cycle.

Running the apprenticeship route informally. Calling someone an apprentice without going through the statutory registration and record-keeping process gives you the obligations without the benefits.

Never closing the loop. No exit interview, no cohort feedback, no changes for next time. Programs that do not iterate degrade.

Keeping everything in spreadsheets. It works for one cohort. It fails silently at three cohorts a year, and it is precisely what fails an audit.

A 90-Day Rollout Plan for Your First Cohort

If you are starting from nothing, here is a sequence that works.

Days 1–15: Charter and classification. Write the one-sentence objective and the target metric. Decide which categories you will use — internship program, apprenticeship, trainee, fixed-term — and for which roles. Get a qualified advisor's written view on the statutory treatment for each in your circumstances. Set the budget envelope.

Days 16–30: Design. Confirm named mentors and the cohort ceiling. Write project briefs — one per intern slot, reviewed by someone other than the author. Finalise the internship agreement template with legal review. Decide the stipend using the five-step process. Build the cohort calendar backwards from the start date.

Days 31–50: Sourcing and selection. Publish the role. Activate campus, portal and referral channels. Run the four-stage selection process. Score, calibrate, decide.

Days 51–70: Offers and pre-onboarding. Issue agreements within 48 hours of acceptance. Collect documents digitally. Send the pre-read pack. Mentor sends a personal note. Provision devices and accounts.

Days 71–75: Mentor enablement. Run the 90-minute mentor briefing. Publish the mentor charter. Set up the rubric, the check-in schedule and the reporting dashboard in your HRMS.

Days 76–90: Launch and stabilise. Run week one to the day-by-day plan. Confirm every intern leaves week one with a written project plan. Hold the first Friday cohort session. Fix any project brief that is not landing — immediately, not at mid-point.

Then run the cycle again, and change three things based on the cohort feedback. Two cohorts in, you have a program. Four cohorts in, you have a pipeline.

Frequently Asked Questions

1. Do we legally have to pay interns in India? The right question is not "must we pay" but "what is this relationship in substance." If someone is doing real work under your direction for a meaningful period, paying a stipend is both the fair practice and the safer practice, and it materially widens your candidate pool. Whether any statutory minimum applies depends on how the engagement is classified, your establishment type, your state and the current legal position — verify this with a qualified advisor rather than relying on a general rule. Unpaid arrangements that involve full-time production work are the highest-risk pattern.

2. What is the difference between a trainee and an apprentice? "Trainee" is usually an internal designation for an employee in an early-career development track — a management trainee or graduate engineer trainee is an employee from day one with a full employment contract. An "apprentice" in the strict sense is engaged under the statutory apprenticeship framework, with a registered contract, a prescribed trade and curriculum, prescribed stipend rules, and record-keeping and return obligations. Using the words loosely is fine in conversation and dangerous in contracts.

3. How long should an internship program run? Eight to twelve weeks is the practical sweet spot for most SMBs: long enough for a real project and a real hiring signal, short enough to stay clearly an internship. Under six weeks you get little beyond ramp-up. Beyond about sixteen weeks, ask honestly whether you are describing employment, and if so use a fixed-term employment contract or the apprenticeship route instead.

4. Can we ask interns to sign a non-compete or a bond? Restrictive covenants that operate after an engagement ends are treated cautiously under Indian law, and imposing bonds or penalties on students is both commercially unwise and reputationally damaging on campus. Focus instead on what is genuinely protective and enforceable in substance: confidentiality obligations, IP assignment, and sensible restrictions on soliciting employees or customers. Have your lawyer review any restrictive clause before you use it.

5. Do interns count in our headcount for statutory thresholds? It depends on the specific statute, the definition it uses, and how the engagement is classified. Several Indian labour statutes have different definitions of "employee," "worker" and "workman," and thresholds can be triggered on different bases. This is exactly the kind of question to put in writing to your advisor, and to revisit whenever your headcount changes materially or the labour code implementation position moves.

6. What should an intern stipend be? There is no single right number, and any figure quoted online dates quickly. Set it through a process: ask the placement cells at your target colleges what comparable employers paid last cycle, ask your own recent junior hires, check live listings for the same role and city, anchor to a fraction of the entry-level role's monthly cost, and decide whether you want to sit at, above or below the local median. Then pay it on a fixed date every month.

7. How do we make intern-to-full-time conversion fair? Publish the bar at kickoff, evaluate against a written rubric with evidence for every score, calibrate across mentors before communicating anything, tell interns honestly at the mid-point where they stand, and separate the performance decision from the headcount decision when you communicate the outcome. Issue written offers quickly, and give a generous response window.

8. What records must we keep for interns and apprentices? At minimum, keep the signed agreement, identity and bank details, attendance records, stipend payment records and statements, evaluation forms, the completion certificate and evidence of access revocation on exit. For apprentices, the statutory framework prescribes additional records and returns — check the current requirements on the official apprenticeship portal. Retain records for the period your advisor recommends and store them securely, since they include personal data.

9. Can a remote internship program work for an SMB? Yes, with three conditions: a tightly written project brief, a mentor who genuinely commits to the check-in cadence, and deliberate cohort connection — a weekly group session and a shared channel. Remote internships fail when they are treated as the same programme minus the office. Also think through device provisioning, data access controls and how you evidence attendance.

10. Should a 30-person company bother with a structured internship program? Especially a 30-person company. Small firms cannot outbid larger employers for experienced junior talent, but they can offer something bigger companies cannot: real ownership, direct access to founders, and visible impact. A structured internship program converts that advantage into a hiring pipeline at a fraction of agency cost. The structure is what makes it repeatable rather than accidental.

Bringing It Together

A good internship program is not a favour you do for students and it is not free labour. It is a deliberately designed system with five moving parts: correct classification, scoped real work, committed mentors, honest evaluation, and clean administration. Get those five right and everything else — conversion, campus reputation, program economics — follows.

The wider context makes this more urgent than it used to be. Skilling and the formalisation of early-career hiring are live themes in Indian policy, the labour code transition has raised the premium on accurate classification and clean records, and the apprenticeship framework exists precisely to make structured on-the-job training viable for smaller employers. SMBs that treat interns as an afterthought will find the afterthought increasingly expensive. SMBs that build a real internship program will find they have quietly solved junior hiring for the next five years.

Start smaller than you think. One cohort of four interns, four written project briefs, four willing mentors, one rubric, one certificate template, one stipend run on a fixed date. Run it, measure it, fix three things, run it again.

And put the admin somewhere it cannot rot. If your interns, apprentices, trainees and fixed-term employees live in the same system as your permanent staff — with the right classification, digital onboarding, attendance, stipend runs, evaluation forms, certificate generation and a clean audit trail — the program stops being a quarterly scramble and becomes something your team actually looks forward to.

If that sounds like the version of early-career hiring you want to run, CozyHR was built for exactly this kind of Indian SMB reality. Take a look at how CozyHR handles employment types, digital onboarding, attendance, stipend and payroll runs, documents and compliance records, and see whether your next intern cohort could run itself. Start a free trial or book a walkthrough with our team — and either way, verify the statutory specifics for your establishment with a qualified advisor before your cohort starts.