Moonlighting Policy for Indian Employers: A Guide

A moonlighting policy is one of those documents that most Indian SMBs never needed until suddenly they did. For years, the question of whether an employee had a second job was largely theoretical for a 40-person company in Pune or Coimbatore — people came to an office, sat at a desk, and the working day had visible edges. Remote and hybrid work removed those edges, and the rise of freelance marketplaces, creator platforms and AI-assisted side income made a second stream of earnings both easier to build and easier to hide.

The result is that a lot of founders and HR managers now find themselves improvising. Someone notices a colleague's name on another company's website, or a manager sees output slipping, or an accountant spots something odd in a PF record. In the absence of a written policy, the reaction is usually emotional and disproportionate — either a panicked blanket ban that alienates the whole team, or a decision to ignore it entirely until it becomes a crisis.

This guide takes the middle path, which is also the defensible one. It covers what moonlighting and dual employment actually mean, where the genuine risks sit (conflict of interest, confidentiality, IP leakage, fatigue, misuse of company assets), what a workable policy contains, how to run a disclosure and approval process that people will actually use, and how to investigate a suspected undisclosed second job fairly — including why UAN and PF cross-checks are a weak signal on their own and should never be treated as conclusive proof. You will also find a model policy outline with sample clause language you can adapt.

What Moonlighting Actually Means — and What It Doesn't

The word "moonlighting" gets used loosely, and that looseness is where a lot of workplace conflict starts. If your policy does not define its terms precisely, managers will apply their own definitions, and you will end up with one team treating a weekend photography business as a firing offence while another quietly ignores a colleague working two full-time engineering jobs.

A working definition

For policy purposes, moonlighting means any paid or unpaid work, service, engagement or business activity that an employee undertakes for a party other than the employer, during or outside contracted working hours, while remaining in the employer's employment.

That definition is deliberately broad at the top, because the policy then narrows it through categories. Broad definition plus clear carve-outs is much easier to administer than a narrow definition that leaves a hundred edge cases undecided.

Dual employment is a narrower idea

Dual employment usually refers to holding two concurrent employer-employee relationships — two payrolls, two sets of statutory contributions, two organisations who each believe they have the person's full-time commitment. It is the highest-risk form of moonlighting and the one most likely to breach an employment contract's exclusivity clause.

A freelance design project on a Sunday is moonlighting but not dual employment. A second full-time role at a competing firm is both. Your policy should treat them differently, because the risk profile is genuinely different.

The activities that usually sit outside the policy

Most sensible policies exclude a set of activities from the disclosure requirement, so employees are not filing forms about their personal lives:

• Passive investments where the employee has no operational role
• Ownership of family property and rental income from it
• Unpaid participation in religious, community, sporting or cultural organisations
• Academic study, certifications and self-directed learning
• Family responsibilities, caregiving and domestic arrangements
• Personal creative work with no commercial exploitation and no link to the employer's business

Saying this out loud matters. It signals that the company is regulating conflict, not curiosity, which reduces the resentment a poorly framed policy generates.

Why Moonlighting Became a Live Issue for Indian SMBs

It is worth being honest about why this topic sharpened. Understanding the causes helps you write a policy that addresses real risk rather than a general feeling of unease.

Remote and hybrid work removed the visible boundary

When work moved to laptops and home desks, employers lost the incidental supervision an office provides. Nobody can see whether an employee is on a second company's video call at 3 pm, so output became the main signal — and output signals are noisy and lagging.

This is not a reason for surveillance. It is a reason for clearer expectations about availability, responsiveness and deliverables, which are good management practice regardless of moonlighting.

The economics of side income changed

Freelance platforms, content creation, online tutoring, small e-commerce operations and consulting through personal networks have all become more accessible, and AI tools compressed the time needed to produce design, code, copy and video work — which made small side projects viable in evening hours that previously would not have been enough.

For many employees, especially at junior and mid levels in high-cost metros, a side hustle is a financial necessity rather than a statement of disloyalty. A policy written on the assumption that side income signals disengagement will read as out of touch.

Employers have real exposure

The employer's concerns are not imaginary either. Customer lists, product roadmaps, pricing logic, code and design assets can leak through a second engagement without anyone intending harm; fatigue affects quality and safety; and where an employee serves two masters in the same market, the conflict is direct and commercially damaging.

A good moonlighting policy holds both truths at once: outside income is normal and often legitimate, and certain outside work is genuinely incompatible with the role.

Harmless Side Work Versus Genuine Conflict

The practical test that works best is not "is the employee earning money elsewhere" but "does this activity create a conflict, a risk of disclosure, a drain on capacity, or a use of company resources."

Four questions that separate the two

1. Competition. Does the outside work serve a competitor, a customer, a supplier or a prospect of the company, or operate in an adjacent market the company is entering?
2. Confidentiality and IP. Could the activity use, expose or contaminate the company's confidential information, code, designs, client data or intellectual property?
3. Capacity and availability. Does it reduce the employee's ability to perform contracted duties, meet availability expectations, or work safely?
4. Resources and representation. Does it use company time, devices, accounts, brand or credentials, or imply the company's endorsement?

If all four answers are no, the activity is almost certainly harmless and should be approved as a matter of routine.

A practical activity classification table

The point of a table like this is that a manager can answer most questions without escalating, and an employee can predict the outcome before filing anything. Predictability is what makes disclosure processes work.

Grey areas you should name explicitly

Every company has a few grey zones. It helps to address them directly in the policy rather than leaving them to interpretation:

• Content creation. A technical channel or newsletter is usually fine, unless it discusses the employer's products, customers or internal practices.
• Teaching and training. Low risk, unless the course reproduces the company's proprietary material or methodology.
• Startup founding. The questions are whether it competes, whether company time or assets are used, and whether the employee is raising money or hiring while employed.
• Family businesses. Usually benign, but an employee who is a director or signatory of a vendor entity has a procurement conflict to manage.
• Gig work. Driving, delivery or task-based platform work is rarely a conflict, but it is a fatigue and availability question in safety-sensitive or shift-based roles.

What a Defensible Moonlighting Policy Contains

A policy is defensible when it is clear, consistently applied, proportionate to the risk, and aligned with the employment contract. Length is not the measure. A well-structured four-page policy beats a fifteen-page document nobody reads.

The core sections

• Purpose and scope, including whether it extends to contractors and consultants
• Definitions of moonlighting, dual employment, conflict of interest, confidential information, company assets and working hours
• Guiding principle — the company does not object to lawful outside activity in principle, but requires disclosure and prohibits conflict
• Permitted, restricted and prohibited categories, as per the table above
• Disclosure obligation — what, when, in what form, and the duty to update
• Approval workflow — who decides, on what criteria, within what timeline, and how decisions are recorded
• Confidentiality and intellectual property, reaffirming the contractual position on work created during employment
• Working hours, availability and fatigue, including a duty not to let outside work impair performance or safety
• Company assets and systems — no use of company devices, accounts, licences, data, brand or premises
• Consequences of breach, as a graduated framework rather than a single threat
• Review and governance — policy owner, review cycle, and record keeping

Sample clause language you can adapt

The wording below is illustrative. Have your own counsel review anything you adopt, and check that it sits consistently with your offer letters, employment agreements, standing orders where applicable, and any NDA or IP assignment already signed.

Guiding principle clause

The Company recognises that employees may have interests, commitments and sources of income outside their employment. The Company does not seek to restrict lawful personal activity that has no bearing on the employee's duties. This policy exists to identify and manage situations where outside activity creates an actual or potential conflict with the Company's interests, compromises confidential information or intellectual property, or affects the employee's ability to perform their role.

Disclosure clause

Employees must disclose, in writing through the designated HR system, any engagement, employment, directorship, partnership, consultancy, freelance assignment, business ownership or regular paid activity undertaken for any party other than the Company, whether or not remunerated, and whether or not performed outside working hours, except for the categories listed as exempt in Annexure A. Disclosure must be made before the activity commences, or within fifteen days of this policy taking effect for activities already in progress. Employees must promptly update their disclosure if the nature, scope, client or time commitment of the activity changes materially.

Exclusivity and prohibited activity clause

Employees shall not, during the term of their employment, enter into any employment, contract for service or engagement with any other employer or entity that is in competition with the Company, that is a current or prospective customer or supplier of the Company, or that would require the employee to render services during the Company's contracted working hours, without the prior written approval of the Company.

Confidentiality and IP clause

No outside activity may involve the use, reproduction, adaptation or disclosure of the Company's confidential information, trade secrets, source code, designs, client data, pricing information, methodologies or other intellectual property. Any intellectual property created by the employee in the course of employment, or using Company resources, information or time, shall vest in the Company in accordance with the employee's employment agreement.

Company assets clause

Company-provided devices, software licences, email accounts, communication tools, subscriptions, premises and networks are provided solely for Company work. They may not be used for any outside activity, including activity that has been disclosed and approved.

Availability and fatigue clause

Employees are expected to be available and responsive during agreed working hours and to maintain the standard of performance required by their role. Outside activity must not result in fatigue, reduced availability, missed commitments or any compromise to health and safety. Where the Company reasonably believes that outside activity is affecting performance or wellbeing, it will raise this with the employee and may review any approval previously granted.

Consequences clause

Failure to disclose a reportable activity, or engaging in a prohibited activity, may result in action under the Company's disciplinary framework, which may range from a documented conversation to termination of employment depending on the seriousness of the matter, the harm caused or risked, and the employee's explanation. Any action will follow a fair process in which the employee is informed of the concern, given the material relied upon and a reasonable opportunity to respond before a decision is taken.

A note on enforceability

Whether a particular restrictive clause can be enforced against an employee in India depends on the wording of the contract, the nature of the restriction, when it operates, and the specific facts. Restrictions that operate during employment are generally treated differently from those that operate after employment ends, and post-employment restraints on trade are treated cautiously.

Two practical implications follow. Do not draft a clause that assumes automatic enforceability; draft one that is reasonable and proportionate, because that is what survives scrutiny. And take legal advice before acting on a suspected breach, particularly before terminating anyone — an early conversation with a lawyer costs far less than a contested termination.

Building the Disclosure Process People Will Actually Use

A moonlighting policy lives or dies on disclosure. If disclosure feels like a confession that invites punishment, nobody discloses and the policy produces nothing except a false sense of control.

Design principles for disclosure

• Make it routine, not exceptional. Ask at onboarding, at annual acknowledgement, and at role changes.
• Approve generously and quickly. If most disclosures clear in a few days, people disclose. If approvals take three weeks and half get refused without reasons, they stop.
• Give reasons for refusals, and where possible a condition that would make the activity acceptable.
• Keep it confidential. Disclosures contain personal financial information; restrict access to HR and the approving manager.
• Offer an amnesty window of thirty to sixty days at launch for existing undisclosed activities outside the prohibited category.

The amnesty point matters more than most companies expect. Launch a policy that makes non-disclosure a disciplinary matter without giving people a way to come clean, and you convert a manageable transparency problem into a permanent concealment problem.

The disclosure and approval workflow, step by step

1. Employee submits a disclosure through a standard form capturing the nature of the activity, the counterparty's name and industry, expected hours per week and timing, expected duration, whether any company client, supplier or competitor is involved, whether any company asset or information would be used, and the start date.
2. HR checks completeness within two working days and routes it. Incomplete forms go back with specific questions rather than a blanket rejection.
3. HR classifies the activity as permitted, restricted or prohibited. Clearly permitted items are auto-acknowledged without manager involvement.
4. The reporting manager assesses operational impact — availability during agreed hours, effect on deliverables, any client overlap they know of, and any performance concerns already on record.
5. A second reviewer handles restricted items. A function head, the founder, or a legal contact assesses conflict, confidentiality and IP risk, and records a short written rationale.
6. A decision issues in writing within ten working days — approved, approved with conditions, deferred pending more information, or declined with reasons.
7. Conditions are recorded and acknowledged in the system: no work during core hours, no company devices, no named clients, a review date.
8. Approvals are re-confirmed annually, alongside the policy acknowledgement cycle.
9. Change triggers re-disclosure. Any material change in scope, client or hours must be declared, and HR reviews open disclosures when someone changes role, joins a sensitive project or moves into a client-facing position.

What to capture in your disclosure register

A simple register makes governance and audit straightforward:

Assessing Risk Without Overreacting

Not every disclosure needs the same scrutiny. A simple matrix helps HR apply proportionate effort and helps you demonstrate consistency if a decision is ever challenged.

A risk-assessment matrix

Score the factors and treat the highest single factor as the driver. One high factor — say, direct competitor — should trigger full review regardless of how low the others are. A cluster of low factors should move quickly through to approval.

Fatigue and working hours deserve real attention

Capacity is often treated as an afterthought, but it is the factor most likely to affect the employee's health and your delivery quality. Someone working a full week plus twenty freelance hours is heading for burnout or missed deadlines.

Handle it as a wellbeing conversation, not a disciplinary one: ask about total weekly hours, check that core-hours availability is holding, and be firm in safety-sensitive roles where fatigue is a physical risk.

Roles where a tighter line is justified

Some positions warrant stricter treatment, and saying so in the policy is fairer than applying a hidden standard:

• Senior leadership and anyone with fiduciary or board responsibilities
• Sales and account management roles that own customer relationships
• Finance, procurement and vendor management, where a family connection creates a direct conflict
• Engineering and product roles with access to core IP and architecture
• Roles handling regulated or sensitive personal data, and safety-critical operational roles

For everyone else, the default should lean towards permission with disclosure.

Investigating Suspected Undisclosed Dual Employment

This is where companies most often get into trouble — not because investigating is wrong, but because it is done hastily, on thin evidence, and without giving the employee a fair chance to explain.

Start with what actually triggered the concern

Legitimate triggers include a sustained drop in performance, repeated unavailability during agreed hours, a client or partner mentioning the employee's involvement elsewhere, a public professional profile listing a concurrent role, or an anomaly surfaced through a routine statutory process. Illegitimate triggers include anonymous gossip treated as fact, a manager's hunch about someone they dislike, or a social media post about a hobby. Write down what triggered the review before you start — that record disciplines the process.

The problem with treating PF and UAN data as proof

A UAN and PF cross-check — noticing that contributions appear against an employee's UAN from more than one establishment — is the detection method most discussed in Indian HR circles. It deserves careful handling, because it is far less conclusive than it appears.

Common innocent explanations include:

• Overlapping notice periods and joining dates. A previous employer may deposit a final month's contribution after the employee has joined you, creating an apparent overlap that is purely administrative.
• Delayed or backdated remittances. Employers sometimes file late; the deposit date does not reliably indicate when the service occurred.
• Employer-side data errors. Wrong dates of exit, wrong UAN mapping, or a contribution filed against the wrong member ID.
• Duplicate UANs. Employees who worked under different Aadhaar or PAN linkages at different times may have more than one UAN, and merges take time.
• Genuinely part-time or short-duration engagements that the employee may believe are covered by an existing approval.
• Name and identifier mismatches, particularly with common names or inconsistent spellings across records.

There are also fairness and privacy considerations. Statutory data is collected for social security administration, not for surveillance of employees. Using it as an investigative tool should be limited to a genuine, documented concern, handled by named individuals, kept confidential, and never used as a routine screening sweep across the whole workforce.

The practical rule is simple: treat a PF or UAN anomaly as a question to ask, never as an answer you already have. It can justify opening a conversation. It cannot, on its own, justify a conclusion or a termination.

What remote work monitoring can and cannot legitimately do

Similar caution applies to monitoring tools. Aggregate, role-appropriate measures — deliverable completion, response times during agreed hours, attendance at scheduled commitments — are reasonable management information, provided employees are told about them in advance.

Covert screen recording, keystroke logging, webcam capture, reading personal communications or installing monitoring on personal devices are a different matter. They are disproportionate for this purpose, corrosive to trust, and create their own legal and privacy exposure. If the reason for wanting them is "someone might have a second job," the answer is a better performance conversation, not more software.

The investigation workflow, step by step

1. Record the trigger and pause. Write down what prompted the concern, who raised it, and when. Do not act on the same day on an emotional reaction.
2. Assess whether there is a real issue. Is there an actual performance, availability, confidentiality or conflict problem, or only a suspicion that someone earns money elsewhere? If the latter, a policy reminder and a disclosure prompt may be the whole response needed.
3. Appoint an impartial reviewer. Someone not personally involved in the dispute or the reporting line, where the organisation's size allows. In a small company, this may mean the founder plus an external HR or legal advisor.
4. Gather only proportionate information. Attendance and availability records, deliverable history, performance documentation, publicly available professional profiles, and — only where justified — statutory records. Do not access personal accounts, personal devices or private communications.
5. Preserve and date the material. Keep copies of what you relied on, with dates. If you later need to show fairness, the file is your evidence.
6. Put the concern to the employee in writing. Set out the specific concern, share the material being relied upon, and invite a written or in-person explanation within a reasonable period — typically five to seven working days.
7. Hold a fair hearing. Let the employee explain, bring documents, and correct factual errors. Take notes and share them. Where your policy or standing orders provide for a companion or representative, honour that.
8. Consider the explanation genuinely. If the employee produces evidence that an overlap is an administrative artefact, or that a previous employer filed late, accept it and close the matter with a written note.
9. Take legal advice before any serious action. Particularly before suspension, withholding of dues, or termination. What your contract says, what your standing orders require, and what the facts actually establish all matter.
10. Decide proportionately and record the reasoning. Match the outcome to the seriousness, the harm caused or risked, the employee's explanation and their record.
11. Communicate the outcome in writing and explain any appeal route.
12. Close the loop. Correct any process gap the case exposed — an unclear clause, a missing disclosure prompt, a manager who did not escalate.

Natural justice is not optional

Whatever the technical legal position in a given case, an investigation that denies the employee notice of the allegation, sight of the evidence, a real chance to respond and an impartial decision-maker is a bad investigation. It will not withstand challenge, and everyone else in the company will notice. Fair process is also practically useful: it surfaces the innocent explanations thin evidence misses, and in genuine cases it produces a record you can rely on.

Proportionate Consequences

The instinct after discovering an undisclosed second job is to reach for termination. That is sometimes right and often not. Consistency across cases matters more than severity in any single case.

A proportionate-response framework

Things to avoid

• Withholding salary or statutory dues as punishment. Wages earned are wages earned, and unilateral deductions create separate exposure.
• Announcing the case internally, before conclusion or at all in identifying detail.
• Applying different standards to senior and junior employees, or to people the founder likes and does not like.
• Acting on a single data point without giving the employee a chance to explain it.
• Applying a policy retrospectively to conduct that predates its communication.

Document what you decided and why

For each case, keep a short decision note: the concern, the material considered, what the employee said, the decision and the reasoning. This is not bureaucracy — it is what lets you show, a year later, that you applied the same standard to two different people.

Why a Blanket Ban on Moonlighting Usually Backfires

Plenty of companies respond to this topic by adding a sentence that prohibits all outside work, full stop. It is understandable and usually counterproductive.

What actually happens

• Disclosure collapses. People with harmless side activities stop telling you, so you lose the visibility the policy was meant to create.
• Enforcement becomes arbitrary. You cannot police every weekend tuition class, so the ban lands on whoever gets noticed — which looks like, and often is, selective treatment.
• It reads as distrust. A ban framed around loyalty rather than conflict tells a capable employee the company assumes the worst about them.
• It hurts hiring and retention. Candidates ask about outside-work policy, and a blanket prohibition puts an SMB at a disadvantage against employers who handle it maturely.
• It does not address the actual risk. Someone determined to work for a competitor will not be stopped by a clause they have already decided to breach. The clause only catches the honest.

What to do instead

• Prohibit the specific categories that create real harm: competitors, customers and suppliers, work during contracted hours, and anything using company assets or confidential information.
• Require disclosure for everything else that is commercial and regular, and approve most of it.
• Be explicit that approval is the expected outcome for low-risk activity, and say so in the policy text itself.
• Publish the criteria you use, so decisions look like judgement rather than mood.
• Fix the underlying drivers where you can. If a large share of your team needs a second income, that is compensation and career-path information you should act on.

A well-run disclosure process also surfaces useful information — who is building skills the company could use, who is under financial pressure, who is quietly preparing to leave. A ban simply pushes all of that out of sight.

Guidance for Managers

Most moonlighting situations are first noticed by a line manager, and most mishandled ones are mishandled at that moment. Give managers short, concrete guidance.

What managers should do

• Treat a disclosure as normal. Thank the employee, ask about hours and client overlap, and route it through the process without editorialising.
• Focus on work, not morality. Assess impact on deliverables and availability, not whether someone should need a second income.
• Raise performance issues as performance issues, with evidence — not as an accusation about a second job.
• Escalate rather than investigate. A manager who suspects undisclosed dual employment tells HR; they do not run their own inquiry or question colleagues informally.
• Keep it confidential, and apply the same standard to everyone on the team, including high performers.

What managers should not do

• Give informal verbal approvals that bypass the process; approvals must be recorded
• Demand to see outside contracts, invoices or bank statements
• Access personal devices, personal accounts or private communications
• Draw conclusions from a professional networking profile, which is often out of date
• Threaten consequences before the process has run

A short script for the first conversation

Something like this keeps the conversation factual and fair:

"I want to raise something directly rather than let it sit. Over the last six weeks, I have noticed [specific, evidenced observation — missed standups, delayed deliverables, unavailability between 2 and 5 pm]. I also want to check whether you have any outside commitment that we should have on record under the outside-work policy. There is no assumption here; if there is something, the process is disclosure and in most cases it gets approved. What is going on from your side?"

Naming the observation, naming the policy, and stating the likely outcome up front is what makes the conversation productive rather than defensive.

Rolling Out a Moonlighting Policy Without Creating Panic

How you introduce the policy shapes how people read it for years afterwards.

• Draft with input from a couple of managers and, if you can, a few employees; it surfaces edge cases you had not considered.
• Get it legally reviewed alongside your existing employment contracts, so the documents agree with one another.
• Announce the reasoning first — why the policy exists, what it does not cover, and that approval is the expected outcome for low-risk activity.
• Open the amnesty window of thirty to sixty days, stating plainly that good-faith disclosures within it will not attract disciplinary action.
• Brief managers on the categories, the escalation route, and the things they must not do.
• Collect acknowledgements from every employee, with a dated record.
• Review after six months — volume of disclosures, approval rate, decision times, and any category causing repeated confusion.

Then track a handful of numbers: disclosures filed by category, the approval rate, median time to decision, the share of employees with a current acknowledgement on file, and how many investigations found an innocent explanation. That last ratio is the useful one — if most reviews end in administrative explanations, your triggers are too sensitive and you are spending trust for nothing.

Model Moonlighting Policy Outline

Use this as a skeleton and adapt it to your contracts, sector and size.

1. Purpose — why the policy exists, and the balance between personal freedom and legitimate business interests.
2. Scope — all employees including probationers, trainees and interns; state how it applies to consultants.
3. Definitions — moonlighting, dual employment, conflict of interest, confidential information, IP, company assets, contracted working hours, competitor, customer, supplier.
4. Guiding principles — disclosure over prohibition, proportionality, confidentiality, consistency.
5. Categories of outside activity — exempt, disclosable, restricted, prohibited, with examples.
6. Disclosure obligations — what, when, how, the duty to update, and the launch amnesty window.
7. Approval process — roles, criteria, timelines, outcomes, appeal route.
8. Conditions that may attach to approval — no work in contracted hours, no company assets, no named clients, hours cap, review date.
9. Confidentiality and intellectual property — cross-reference to the employment agreement, NDA and IP assignment.
10. Working hours, availability and fatigue — core hours, responsiveness, safety, and the right to review approvals.
11. Use of company assets and systems — devices, accounts, licences, premises, brand, credentials.
12. Monitoring and privacy — what the company does and does not do, and the proportionality principle.
13. Breach and consequences — the graduated framework and the commitment to fair process.
14. Roles and responsibilities — employee, manager, HR, function head, legal.
15. Governance — policy owner, review cycle, record retention, access to disclosures.

Annexures: exempt activities, disclosure form fields, and the assessment criteria used by reviewers.

Frequently Asked Questions

Is moonlighting illegal in India?

Moonlighting is not a criminal matter; it is primarily a contractual and employment question. Whether a particular second engagement breaches the employee's obligations depends on what the employment contract says, what the employer's policy provides, and the facts of the case. Certain statutory provisions restrict concurrent work in specific contexts, so employers should take legal advice rather than assume a general prohibition applies.

Can we terminate an employee purely because a second PF contribution shows up against their UAN?

That would be unwise. PF and UAN anomalies frequently arise from overlapping notice periods, late filings, wrong exit dates, duplicate UANs or record-matching errors, and they are a question to ask rather than proof of anything. Put the concern to the employee in writing, share the material, consider their explanation properly, and take legal advice before any serious action.

Should our moonlighting policy apply to contractors and consultants?

Usually a lighter version applies. Independent contractors are typically free to serve multiple clients, so the sensible focus for them is conflict of interest, confidentiality, IP ownership and any specific non-compete terms agreed in their service contract. Applying a full employee-style exclusivity requirement to a genuine contractor can also undermine their independent status.

How do we handle an employee who runs a family business?

Family businesses are extremely common and usually pose no issue at all. The situations that need managing are where the family entity is a vendor, customer or competitor of your company, or where the employee holds a decision-making role in procurement, finance or sales. Require disclosure, then manage the specific conflict — recusal from related decisions, for example — rather than prohibiting the arrangement.

What if an employee's side hustle is content creation or a personal brand?

Generally treat it as a disclosable but permitted activity. The conditions worth attaching are that the employee does not discuss the company's products, customers, internal practices or confidential information; does not imply the company endorses their content; and does not create it during contracted working hours or on company devices. Many employers find a visible, respected creator on the team is an asset in hiring.

Can we require employees to declare their total outside income?

You generally do not need the numbers, and asking for them creates a privacy burden with little benefit. What matters for a moonlighting policy is the nature of the activity, who the counterparty is, and the time commitment. Collect what the assessment actually requires and no more.

How often should employees re-confirm their disclosures?

Annually is the common cadence, usually bundled with the yearly policy acknowledgement cycle. On top of that, employees should have a standing obligation to re-disclose whenever the scope, client or hours of an approved activity change materially, and HR should review open disclosures when someone changes role or joins a sensitive project.

Conclusion

A moonlighting policy is not really about catching people. It is about making a genuinely difficult subject predictable — for the employee weighing up a freelance project, for the manager who notices something and does not know what to do, and for the founder who needs to protect customer relationships and intellectual property without turning the company into a suspicious place to work.

The version that works is specific rather than sweeping. Define the terms. Name the categories that are fine, the ones that need a conversation, and the narrow set that genuinely cannot be allowed. Make disclosure easy, quick and mostly successful. Investigate rarely, fairly, and never on a single data point. Match consequences to actual harm, and take legal advice before you act on a suspected breach. Treat privacy and proportionality as real constraints, not obstacles.

The policy is only as good as the process that runs it. A document nobody has acknowledged, disclosures sitting in email threads, and approvals that exist only as a manager's memory will not help you when a real conflict appears.

If you are putting this in place, CozyHR can carry the administrative weight: circulating the policy and capturing acknowledgements with a dated record, running a structured disclosure form with routing and approvals, keeping a searchable register of declarations and conditions, and prompting annual re-confirmation alongside your other HR workflows. Worth a look when you are ready to move from a document to a working process.