The legal position, stated plainly
Moonlighting became a live issue for Indian employers when remote work made a second job practical to hide, and several large IT companies made public statements about it. The public argument was noisier than the legal position, which is fairly simple.
There is no central law in India that prohibits a private sector white-collar employee from holding a second job. What exists are narrow, specific provisions that catch particular categories of worker, and a general principle that your employment contract can restrict what your employees do with their time.
That is the whole framework. Everything else is drafting and enforcement.
What the statutes actually cover
Three sources come up, and only one of them is likely to apply to the kind of employee most foreign companies hire in India.
Section 60 of the Factories Act 1948. This prohibits an adult worker from being required or allowed to work in any factory on any day on which they have already been working in another factory. It is a real prohibition and it is squarely about factories. It does not reach a software engineer working from a flat in Pune.
State Shops and Establishments Acts. Several state Acts restrict a person from working in more than one establishment, or in an establishment and a factory, beyond the total daily and weekly hours the Act permits. The Delhi Act is the usual example cited. These are state statutes with state-specific wording, so the answer depends on where your employee sits. This is the provision most likely to be relevant to an office or remote worker, and it is framed around total hours worked rather than around loyalty or exclusivity.
The employment contract. For most employers this is the operative source. An exclusivity clause, a clause requiring full time and attention, a conflict-of-interest clause, or a restriction on outside engagement without written consent. If the clause is there and it is clear, you have a contractual basis to act. If it is not there, you largely do not, whatever your policy handbook says.
There is no fixed statutory penalty for moonlighting as such, because there is no offence of moonlighting. What you have is a potential breach of contract, and the remedies that flow from that.
Where the real risks sit, and they are not the second job itself
Employers tend to frame moonlighting as a loyalty problem. The exposures that actually cost money are narrower and more concrete.
Competition. An employee working for a competitor, in any capacity, is the case where the interest is obvious and the response is easy to justify. This is worth naming separately in the policy rather than folding into a general restriction.
Confidential information and IP. The serious version. Code, customer data, designs or documents moving between two employers, or work produced for you on time and equipment that a second employer might later claim. Your IP assignment clause is doing more work here than your exclusivity clause. We cover the cross-border version in contractor IP assignment across US, India and EU jurisdictions, and the same drafting logic applies to employees.
Hours and capacity. Two full-time jobs is forty additional hours a week that have to come from somewhere. This is the one that turns into a performance conversation, and it is often the cleanest ground to stand on, because it is measurable and does not require you to prove anything about the second employer.
Company resources. Second-job work done on your laptop, your VPN, your cloud account. Easy to evidence and hard to defend.
Note what is missing from that list: the mere existence of another source of income. An employee who teaches a weekend course, writes, or holds equity in a friend’s company is not creating any of these exposures, and a policy that treats them identically to a competitor engagement is a policy people will ignore.
How dual employment surfaces
Employers rarely go looking. The data tends to arrive on its own, usually through one of three routes.
Provident Fund. The most common. An employee is meant to hold one Universal Account Number for life. When two PF-covered employments run simultaneously, contributions arrive against the same UAN from two different establishment codes, or the second employer generates a duplicate UAN that later has to be merged. Either way the overlap becomes visible in the record, and it typically comes to light during an exit, a transfer, or an EPFO reconciliation.
Background verification. At the next job. The employment history check picks up an overlap the candidate did not declare. Our background verification guide covers what these checks actually pull.
Tax records. Form 26AS and the annual information statement show TDS deducted by every deductor. Two salary deductors in one financial year is visible to the employee’s own tax record, and to anyone the employee shows it to.
None of these is a monitoring programme, and building one is generally a worse idea than it sounds. Surveillance of employees creates its own exposure under India’s data protection framework and does more damage to the people complying than to the people you are worried about.
Writing a policy that holds up
The instinct is a blanket ban. It is usually the weaker option.
Blanket bans are widely ignored, which produces two problems. The employees who comply are, by definition, the ones who were never the risk. And enforcement becomes selective, because you cannot act on every breach you do not know about, so when you do act it looks arbitrary and is harder to defend.
A disclosure-and-approval policy works better. The shape:
Require written disclosure of any outside engagement, employment, consulting, directorship or business, before it starts.
Approve or refuse on stated grounds. Refuse where the engagement is with a competitor, uses company resources or confidential information, overlaps with working hours, or would take the employee’s total hours beyond what the applicable state Act permits. Approve otherwise, and put the approval in writing.
Say what does not need approval. Passive investment. Unpaid volunteering. Writing or speaking that does not touch company confidential information. Carving these out makes the rest of the policy credible.
Set the consequence. Breach is a disciplinary matter under the ordinary process, not automatic termination. Automatic termination clauses are the ones that get read down.
Match the contract. The policy is only as good as the clause in the signed employment contract it rests on. If the contract has no exclusivity or conflict clause, add it for new hires and take advice before applying a new policy to existing ones, because unilaterally imposing a new restriction on an existing contract is its own question. Our India employment contract clauses guide covers where this sits among the other clauses that matter.
If you decide to act
Run it as a disciplinary process. That means: put the allegation to the employee in writing with the specifics, give a genuine opportunity to respond within a stated time, actually consider the response, and record the decision and its reasoning.
The temptation is to skip this because the evidence looks obvious. A LinkedIn profile listing two employers is not proof of a contractual breach, and a termination built on it without process is the version that gets challenged and reversed. The process is not a formality; it is what makes the outcome hold.
Where the employee is a workman under the Industrial Relations Code 2020, the procedural bar is higher again. Whether someone is a workman turns on the nature of their duties rather than their title or seniority, so do not assume an engineer is outside it.
And consider whether termination is the response you want. In a fair number of cases the second engagement is small, non-competing and disclosed late out of awkwardness rather than concealed. A warning, a disclosure, and a documented file is a proportionate outcome that leaves you a stronger position if it happens again.
If you hire in India through an EOR
Worth being clear about who owns what. The EOR is the legal employer, so the employment contract and any exclusivity clause are issued in the EOR’s name, and a disciplinary process runs through the EOR. You direct the work and you decide what the policy should be, but you do not unilaterally terminate someone the EOR employs.
Two practical consequences. First, read the EOR’s standard employment contract before your first hire signs it, and check that the exclusivity and conflict-of-interest clauses say what you want them to say. Standard templates vary and some are thin here. Second, agree in advance how a conduct issue gets escalated, because discovering the escalation path during an incident is worse than agreeing it in the onboarding call.
The short version
No central law bans moonlighting for private sector employees in India. The Factories Act provision is about factories. Some state Shops and Establishments Acts limit total hours across establishments. Beyond that, your contract is your restriction.
Write a disclosure-and-approval policy rather than a ban, name competition and confidential information as the specific grounds for refusal, back it with a clause in the signed contract, and run any enforcement as a proper disciplinary process. That combination is enforceable, defensible, and considerably less work than the alternative.