Transfer Between Projects Without Consent

Transfer of an employee from one project to another without the employee’s consent is generally governed by the terms of employment, service rules, standing orders, appointment letter, and the nature of the employer’s business. A transfer is not automatically illegal merely because the employee does not agree to it. Courts generally distinguish between a legitimate administrative transfer and a transfer that is made as a punitive, mala fide, discriminatory, or contractually impermissible measure.

Where an appointment is not tied exclusively to a particular project, location, or assignment, an employer ordinarily has considerable discretion to deploy an employee according to business requirements. However, that discretion is subject to applicable law and cannot ordinarily be exercised arbitrarily or for an improper purpose.

1. Meaning of Transfer Between Projects

A project-to-project transfer occurs when an employee who is working on one project, department, client assignment, or business unit is moved to another project.

For example, an employee appointed as a software engineer may initially work on Project A and later be assigned to Project B. If the appointment letter permits deployment across projects, the employer may generally make such a change without obtaining separate consent each time.

The legal position becomes more complicated where:

• the employee was specifically appointed for a particular project;
• the employment contract restricts deployment;
• the transfer substantially changes the employee's contractual duties;
• salary or important employment conditions are reduced;
• the transfer is effectively punitive;
• the transfer is discriminatory or mala fide; or
• applicable standing orders or service rules require compliance with particular procedures.

2. Consent Is Not Always Necessary

An employer-employee relationship ordinarily includes an implied requirement that the employee perform duties reasonably assigned by the employer, subject to the contract and applicable service rules.

Therefore, absence of employee consent alone does not invalidate a transfer.

In B. Varadha Rao v. State of Karnataka, the Supreme Court recognised transfer as an ordinary incident of service and observed that an employee holding a transferable post cannot generally claim a vested right to remain at a particular place.

Similarly, in Shilpi Bose v. State of Bihar, the Supreme Court emphasised that courts should ordinarily be slow to interfere with transfers made by competent authorities in administrative exigencies.

The same principle can apply to project transfers where the employee's appointment is not restricted to a particular project.

3. Contractual Terms Are Important

The first document to examine is the appointment or employment contract.

For example, a clause stating that:

"The employee may be assigned to any project, department, client location or business unit according to organisational requirements"

can give the employer substantial authority to transfer the employee.

Conversely, if the contract expressly states that the employee is appointed exclusively for a specified project, an attempt to move the employee elsewhere may raise a contractual issue.

The court will therefore examine the actual terms of employment rather than merely the employee's preference.

4. Transfer Cannot Be Used as Punishment in Disguise

A transfer may become legally vulnerable when it is not genuinely administrative but is imposed as punishment for misconduct.

In Somesh Tiwari v. Union of India, the Supreme Court dealt with a transfer alleged to have been motivated by mala fides. The Court explained that an order ostensibly framed as an administrative transfer may be interfered with where it is vitiated by mala fides or is based on extraneous considerations.

Thus, an employer should not use a project transfer as an informal substitute for disciplinary proceedings.

For example, moving an employee to an undesirable project solely because the employee complained about harassment, exercised a legal right, or participated in a protected activity could raise serious legal concerns.

5. Mala Fide Transfers

A transfer can be challenged where there is evidence that the employer acted with an improper motive.

However, merely alleging mala fides is generally insufficient. Courts normally require convincing material demonstrating that the transfer was made for an improper purpose.

In State of U.P. v. Gobardhan Lal, the Supreme Court stated that transfer is ordinarily an incident of service and that interference should be limited to cases involving mala fides, violation of statutory provisions, or similar exceptional circumstances.

Therefore, an employee's dissatisfaction with a new project does not by itself establish mala fide conduct.

6. Transfer Must Comply With Statutory or Service Rules

The employer's power is not unlimited.

If statutory rules, certified standing orders, service regulations, or a collective bargaining agreement govern deployment, the employer must comply with those provisions.

A transfer contrary to a mandatory statutory requirement can be challenged even though transfers are ordinarily matters of administrative discretion.

In Union of India v. S.L. Abbas, the Supreme Court reiterated that transfer is ordinarily a matter for the employer/competent authority and that courts should not substitute their own judgment regarding where an employee should be posted.

7. Transfer and Change in Nature of Employment

There is an important distinction between:

Project reassignment:
The employee continues to perform substantially similar work under the same employment relationship.

Change in contractual employment:
The employer attempts to impose materially different duties, reduce remuneration, alter status, or otherwise change fundamental contractual conditions.

A simple reassignment between projects is more likely to be upheld where the employee's designation, salary, grade and essential terms remain unchanged.

If the new project involves substantially different responsibilities, a significant contractual change may require closer legal examination.

8. Transfer Cannot Ordinarily Be Challenged Merely Because It Causes Inconvenience

Courts generally recognise that organisational decisions can cause inconvenience to employees.

In Mrs. Shilpi Bose v. State of Bihar, the Supreme Court held that transfer orders made in public interest and for administrative reasons should ordinarily not be interfered with merely because they cause hardship to the employee.

The same principle is relevant to project assignments: an employee's preference for the existing project does not ordinarily create a legal right to remain there.

9. Relevant Supreme Court Case Laws

1. B. Varadha Rao v. State of Karnataka, (1986) 4 SCC 268

The Supreme Court treated transfer as an ordinary incident of service and recognised that an employee generally cannot claim a vested right to serve at a particular place.

Relevance: A project transfer can ordinarily be made where the employee holds a transferable position.

2. Shilpi Bose v. State of Bihar, 1991 Supp (2) SCC 659

The Supreme Court held that transfer orders made by competent authorities for administrative reasons should ordinarily not be interfered with by courts.

Relevance: Lack of employee consent does not by itself invalidate an administrative transfer.

3. Union of India v. S.L. Abbas, (1993) 4 SCC 357

The Supreme Court observed that transfer is an incident of service and that the competent authority is normally best placed to decide where an employee should be posted.

Relevance: Courts generally do not substitute their judgment for the employer's administrative decision.

4. State of U.P. v. Gobardhan Lal, (2004) 11 SCC 402

The Supreme Court held that interference with transfer orders may be justified in exceptional situations such as mala fides or violation of statutory provisions.

Relevance: An employer's transfer power remains subject to legal limitations.

5. Somesh Tiwari v. Union of India, (2009) 2 SCC 592

The Supreme Court considered the effect of mala fide considerations behind a transfer and emphasised that an administrative order can be invalid where the power is exercised for an improper purpose.

Relevance: A project transfer cannot lawfully be used as a disguised punishment or for collateral reasons.

6. National Hydroelectric Power Corporation Ltd. v. Shri Bhagwan, (2001) 8 SCC 574

The Supreme Court reiterated the general principle that transfer is an incidence of service and that courts should exercise restraint in interfering with administrative transfers.

Relevance: Where service conditions permit mobility, reassignment can generally be made without obtaining fresh consent.

10. When Can an Employee Challenge the Transfer?

A project transfer may be legally questionable where the employee can establish one or more of the following:

1. The appointment contract restricts deployment to a particular project.
2. Mandatory service rules have been violated.
3. The transfer amounts to a material alteration of employment conditions.
4. The transfer is mala fide.
5. The transfer is actually being imposed as a punishment without following disciplinary procedure.
6. The decision is discriminatory or retaliatory.
7. The transfer violates a statutory protection applicable to the employee.
8. The employer lacks authority under the applicable employment framework to make the transfer.

11. Practical Legal Test

For determining whether a project transfer without consent is lawful, the following sequence is useful:

Step 1 – Examine the appointment letter
Check transfer, mobility, deployment and project-assignment clauses.

Step 2 – Check service rules/standing orders
Determine whether any formal procedure applies.

Step 3 – Compare the two projects
Check whether designation, salary, grade, working hours and essential duties remain substantially the same.

Step 4 – Determine the reason for transfer
Administrative/business requirements are generally treated differently from punitive or retaliatory motives.

Step 5 – Check for mala fides or discrimination
Look for evidence showing that the stated reason is not the real reason.

Step 6 – Check statutory protections
Particular categories of employees or workplaces may be subject to additional statutory requirements.

Conclusion

Transfer between projects without the employee's consent is not automatically unlawful. Where the employment contract permits deployment and the employee continues in substantially the same employment, designation and remuneration, an employer will ordinarily have considerable authority to reassign the employee according to genuine business or administrative requirements.

However, that power is not absolute. A transfer may become challengeable when it violates contractual or statutory provisions, substantially alters employment conditions, is discriminatory or mala fide, or is used as a disguised disciplinary punishment. The legality therefore depends principally on the employment contract, applicable service rules, nature of the new assignment, and actual reason behind the transfer.