A Legal Article

Project employment is common in Philippine industries such as construction, engineering, information technology, media production, events, business process outsourcing, logistics, manufacturing, shipbuilding, security services, consulting, and seasonal commercial operations. Employers often hire workers for a specific project, phase, account, campaign, contract, or undertaking. When the project ends, the employment supposedly ends as well.

But not every worker called “project-based” is legally a project employee. Under Philippine labor law, labels do not control. The real nature of the work, the agreement, the employer’s business, and the employee’s length and pattern of service determine whether a worker is genuinely project-based or already entitled to regular employment.

This article explains the rights of project-based employees to regularization in the Philippines, including the governing legal principles, tests used by courts and labor tribunals, signs of illegal project employment, remedies for workers, and practical guidance for both employees and employers.

I. Basic Rule: Philippine Labor Law Protects Regular Employment

The Labor Code recognizes different kinds of employment, including:

Regular employment;
Project employment;
Seasonal employment;
Casual employment;
Probationary employment;
Fixed-term employment, in limited cases.

The law does not prohibit project employment. A business may hire workers for a specific project or undertaking. However, the law does prohibit using project employment to defeat security of tenure.

The constitutional and statutory policy in the Philippines favors protection to labor, security of tenure, humane working conditions, and fair treatment. An employee cannot be dismissed without just or authorized cause and due process. If a worker is actually regular, the employer cannot avoid regularization by repeatedly issuing short-term project contracts.

II. What Is a Project-Based Employee?

A project-based employee is one whose employment has been fixed for a specific project or undertaking, the completion or termination of which has been determined at the time of engagement.

In simpler terms, project employment exists when:

The employee is hired for a specific project or undertaking;
The project is distinct and identifiable;
The employee knows, at the time of hiring, that employment will last only until the project or phase is completed;
The completion or termination of the project determines the end of employment;
The arrangement is not merely a device to avoid regularization.

The key is certainty and specificity. The worker must not merely be told, “You are project-based.” The project, scope, duration, or completion standard must be identifiable from the beginning.

III. Regular Employment Versus Project Employment

The distinction is crucial.

A regular employee performs work that is usually necessary or desirable in the usual business or trade of the employer, or has rendered at least one year of service, whether continuous or broken, with respect to the activity in which the employee is employed.

A project employee performs work for a specific project or undertaking whose completion or termination is known or determinable at the time of hiring.

The same kind of work may be regular in one context and project-based in another. For example:

A carpenter hired by a construction company for one building project may be a project employee.
A carpenter repeatedly assigned by the same company to project after project for many years may become regular, depending on the facts.
A software developer hired for a one-time system migration may be project-based.
A software developer continuously assigned to core product maintenance may be regular.
A camera operator hired for a single film shoot may be project-based.
A camera operator continuously engaged for the station’s ordinary programming may be regular.

The legal conclusion depends on the actual relationship, not merely the contract title.

IV. The “Necessary or Desirable” Test

One of the main tests for regular employment is whether the employee’s work is usually necessary or desirable in the usual business or trade of the employer.

If the employee’s work is integral to the employer’s ordinary business, the worker is often considered regular.

Examples:

A machine operator in a manufacturing company;
A call center agent handling the company’s regular client services;
A cashier in a retail business;
A cook in a restaurant;
A delivery rider directly employed by a logistics company for its usual delivery operations;
A maintenance technician in a company whose operations require continuous technical maintenance.

However, project employment may still be valid even if the work is necessary or desirable, if the worker is truly hired for a distinct project with a determinable end. This is especially common in project-driven industries such as construction. The question is whether the employment is genuinely tied to a specific project or whether the “project” label is a disguise.

V. The One-Year Rule

The Labor Code provides that an employee who has rendered at least one year of service, whether continuous or broken, shall be considered a regular employee with respect to the activity in which they are employed, and the employment shall continue while such activity exists.

This rule is often invoked by workers who are repeatedly hired under short-term contracts.

However, in project employment, the one-year rule must be carefully applied. A genuine project employee does not automatically become regular merely because the project lasted more than one year, if the employment was truly tied to a specific project or undertaking known from the start.

On the other hand, repeated rehiring for the same necessary or desirable work, especially without meaningful project specificity, can support regularization.

The practical question is not only “Did the worker serve one year?” but also:

Was the worker assigned to the same activity repeatedly?
Was the work necessary or desirable to the employer’s business?
Were the contracts specific and genuine?
Did the employer report project completion?
Was there a real end to each project?
Was the worker continuously retained despite supposed project endings?

VI. The Importance of a Specific Project or Undertaking

A valid project employment contract should identify the project with reasonable clarity.

The contract should state, where applicable:

The specific project or undertaking;
The phase of the project;
The employee’s position or role;
The expected duration or completion standard;
That employment ends upon completion of the project or phase;
The relation of the employee’s work to the project;
The place of assignment;
The basis for determining project completion.

A vague contract saying only “project-based employee” or “employment shall last for the duration of the project” may be insufficient if the project itself is not identified.

Examples of more specific project descriptions:

“Construction of Tower A, Phase 2 structural works, Makati site”;
“Migration of client X database from legacy platform to cloud environment”;
“Production of 12-episode online video series for client Y”;
“Three-month mall activation campaign for brand Z”;
“Installation and testing of conveyor system under contract no. 123.”

Examples of vague or suspicious descriptions:

“Company project”;
“Operations project”;
“As needed by management”;
“Client assignment”;
“Temporary account” without definite project scope;
“Until further notice.”

The more vague the project, the more likely the arrangement will be questioned.

VII. The Employee Must Know the Project Duration or Completion Standard at Hiring

For project employment to be valid, the employee must be informed at the time of engagement that employment is coterminous with the project.

This does not always require an exact calendar date. Some projects cannot be predicted with perfect accuracy. But the completion or termination of the project must be determinable.

For example, employment may end upon:

Completion of a building phase;
Delivery of a software module;
End of a client campaign;
Completion of filming;
Completion of installation works;
End of a specific contract with a client;
Completion of a research project.

If the employee is only told later that the work was project-based, the employer’s position becomes weaker. A project label cannot be imposed retroactively to defeat rights already acquired.

VIII. Project Employment in the Construction Industry

Construction is the classic example of lawful project employment. Contractors and subcontractors often hire workers for specific construction projects or project phases.

A construction worker may be hired for:

Excavation;
Structural works;
Electrical installation;
Plumbing;
Finishing;
Roadwork;
Bridge construction;
Renovation;
Demolition;
Site preparation.

Because construction projects naturally have a beginning and an end, project employment is recognized. But construction workers may still become regular in certain situations.

A construction worker may claim regular status when:

They are continuously rehired for many projects;
They perform tasks necessary and desirable to the employer’s construction business;
There is no real gap between projects;
The employer maintains a work pool;
The worker is repeatedly assigned as part of the employer’s regular workforce;
The contracts are vague or simulated;
The employer does not properly report termination after project completion;
The worker is retained even when no specific project exists;
The worker performs administrative or continuous office functions unrelated to any particular project.

Not all repeated rehiring automatically creates regular employment, but repeated and continuous engagement may show that the worker is part of the employer’s regular operations.

IX. Project Employment Outside Construction

Project employment is not limited to construction. It may also exist in other industries, such as:

1. Information technology

Examples:

Software migration project;
Cybersecurity audit;
App development for a specific client;
System integration;
Data cleanup project.

A developer hired for a specific deliverable may be project-based. But a developer doing ongoing maintenance of the employer’s core platform may be regular.

2. Media, film, and entertainment

Examples:

Film production;
Television season;
Advertising shoot;
Concert production;
Event livestream;
Documentary project.

A crew member hired for one production may be project-based. But personnel continuously used for the network’s regular programming may be regular.

3. Events and marketing

Examples:

Product launch;
Roadshow;
Mall activation;
Trade fair;
Campaign rollout.

Event staff may be project-based for a specific event. But full-time operations personnel repeatedly assigned to all events may be regular.

4. Business process outsourcing

A BPO worker may be assigned to a client account, but the mere existence of a client account does not automatically make the worker project-based. If the worker performs the employer’s regular business of providing outsourced services, and the employment arrangement is not tied to a distinct project with a determinable end, regular status may arise.

5. Manufacturing

A manufacturer may hire workers for a special production run, installation project, or temporary contract. But workers doing ordinary production-line tasks for the employer’s usual products are likely regular if the arrangement is continuous or necessary to the business.

X. Work Pool Employees

A recurring issue is the status of workers kept in a work pool.

A work pool exists when an employer maintains a group of workers who are repeatedly called for different projects. This is common in construction, entertainment, and project-based industries.

Being in a work pool does not always mean regular employment. Workers may remain project employees if they are engaged only for specific projects and are free between projects.

However, work pool employees may become regular when:

They are continuously and repeatedly hired;
They are expected to be available to the employer;
They perform tasks necessary and desirable to the employer’s usual business;
They are not meaningfully free to work elsewhere;
Their repeated rehiring shows they are part of the employer’s regular workforce;
There is no true project-to-project separation;
The employer uses the work pool to avoid regularization.

The more control and continuity the employer exercises, the stronger the claim for regular status.

XI. Repeated Renewal of Project Contracts

Repeated renewal is one of the strongest indicators that project employment may be improper.

A worker may be hired under a three-month project contract, then another three-month contract, then another, for years. If each contract covers the same role, same workplace, same supervisor, and same business function, the arrangement may be considered a scheme to prevent regularization.

Signs of disguised regular employment include:

Continuous service with no meaningful break;
Same job title across contracts;
Same work location;
Same immediate superior;
Same business function;
No identified project deliverable;
Contracts renewed automatically;
Employee remains after supposed project completion;
Payroll and benefits continue without interruption;
Employee is included in regular staffing schedules;
Employee performs core business tasks;
The employer cannot prove actual project completion.

Repeated project contracts are not illegal by themselves. They become legally vulnerable when the supposed projects are not real, distinct, and determinable.

XII. Project Employees and Security of Tenure

Project employees also have security of tenure, but within the nature of project employment.

A genuine project employee cannot be dismissed before project completion except for just or authorized cause and due process. The employer cannot simply terminate the worker at will before the project ends.

The employment of a project employee validly ends when the project or phase is completed. In that case, the end of the project is not considered illegal dismissal.

However, if the project employee is terminated before project completion without lawful cause, there may be illegal dismissal.

Likewise, if the employee is actually regular and is dismissed because a “project contract” expired, there may be illegal dismissal.

XIII. End of Project Versus Termination

The end of a genuine project is different from dismissal.

If the employment ends because the project has been completed, the employer is not necessarily dismissing the worker for cause. The employment simply reaches its agreed endpoint.

But the employer must be able to prove:

The project was real and specific;
The employee was hired for that project;
The employee knew the employment was coterminous with the project;
The project or phase was actually completed;
The end of employment coincided with project completion;
The arrangement was not a device to avoid regular employment.

If the employer cannot prove these, the worker may argue that the termination was illegal.

XIV. Notice and Reporting Requirements

Employers are generally expected to document project employment properly. In project employment, especially in industries where DOLE reporting is required, employers should report termination due to project completion to the appropriate labor office.

Failure to report project completion is not always by itself conclusive proof of regular employment, but it is an important factor. It may weaken the employer’s claim that the worker was truly project-based.

Proper documentation protects both sides. For the employee, it clarifies rights and the expected end of employment. For the employer, it helps prove the legitimacy of project employment.

XV. Project Employee Rights During Employment

Project employees are employees. They are not independent contractors merely because they are project-based.

They are entitled to labor standards and statutory benefits, where applicable, such as:

Minimum wage;
Overtime pay;
Holiday pay, subject to rules;
Premium pay for rest day or special day work;
Service incentive leave, subject to qualifications;
13th month pay;
Social security coverage;
PhilHealth coverage;
Pag-IBIG coverage;
Safe and healthful working conditions;
Protection against illegal wage deductions;
Protection against discrimination and harassment;
Right to self-organization, where applicable;
Due process in disciplinary actions;
Final pay upon separation;
Certificate of employment upon request.

A project employee may be temporary in duration, but not outside labor law.

XVI. 13th Month Pay for Project Employees

Project employees are generally entitled to 13th month pay if they are rank-and-file employees and have worked for at least one month during the calendar year, subject to applicable rules.

The amount is usually proportionate to the basic salary earned during the year.

An employer cannot deny 13th month pay merely by calling the worker project-based.

XVII. Service Incentive Leave

A project employee may be entitled to service incentive leave if they meet the legal requirements and are not excluded by law or applicable rules.

Generally, employees who have rendered at least one year of service may be entitled to five days of service incentive leave with pay, unless they already enjoy equivalent or better leave benefits or fall under exceptions.

The computation can become fact-specific for project employees, especially where service is intermittent.

XVIII. Social Security, PhilHealth, and Pag-IBIG

Project employees should be covered by mandatory social legislation. Employers must generally register and remit contributions for covered employees.

Failure to remit contributions may expose the employer to liability.

A worker should check contribution records, especially if they have worked under repeated project contracts. Missing contributions may support a broader claim of labor law violations, although contribution issues are usually handled by the respective agencies.

XIX. Wages and Labor Standards

Project employment does not justify subminimum wages or unpaid overtime.

Project employees must be paid according to:

Applicable minimum wage orders;
Hours of work rules;
Overtime rules;
Rest day and holiday pay rules;
Wage payment requirements;
Occupational safety standards.

In construction and other high-risk industries, occupational safety obligations are particularly important.

XX. Probationary Versus Project Employment

Probationary employment and project employment are different.

A probationary employee is hired for a regular position but is under observation for qualification standards during the probationary period. If the employee meets the standards and continues working beyond the probationary period, the employee becomes regular.

A project employee is hired for a specific project, and employment ends when the project ends.

An employer should not confuse the two. A contract cannot say “probationary project employee” in a way that hides the actual nature of the work. The substance of the arrangement controls.

XXI. Fixed-Term Employment Versus Project Employment

Fixed-term employment is based on a definite period, such as six months or one year. Project employment is based on completion of a project or undertaking, although it may also estimate a period.

Fixed-term employment is valid only under limited conditions and cannot be used to defeat security of tenure. If the fixed period is imposed by the employer on a worker performing regular work, the employee may be deemed regular.

A “project contract” that is really just a fixed three-month renewable contract for regular work may be challenged.

XXII. Casual Employment Versus Project Employment

A casual employee performs work that is not usually necessary or desirable to the employer’s usual business. If a casual employee works for at least one year, whether continuous or broken, the employee becomes regular with respect to the activity performed.

A project employee, by contrast, is tied to a specific project or undertaking.

Employers sometimes use the terms casually, but the law treats them differently.

XXIII. Seasonal Employment Versus Project Employment

Seasonal employees are hired for work that recurs during a season, such as agricultural harvests, peak tourism periods, or holiday production.

Seasonal employees may become regular seasonal employees if repeatedly hired for the same seasonal work over time. This means they may have regular status during the season and a right to be rehired when the season returns, depending on the facts.

Project employment is tied to a specific project, not merely a recurring season.

XXIV. Independent Contractor Versus Project Employee

An independent contractor is not an employee. A project employee is an employee.

The difference matters because independent contractors are generally governed by civil or commercial contracts, while employees are protected by labor law.

Factors suggesting employment include:

Employer controls not only the result but also the means and methods of work;
Worker follows company schedule;
Worker uses company tools;
Worker is supervised by company managers;
Worker is integrated into the workforce;
Worker receives wages through payroll;
Worker is subject to discipline;
Worker has no substantial business of their own.

An employer cannot avoid regularization by calling a worker an “independent contractor” if the relationship is actually employment.

XXV. Legitimate Job Contracting and Project Employment

Some workers are deployed to a principal through a contractor. In this setup, the worker may be an employee of the contractor, not the principal, if the contractor is legitimate and independent.

However, if the contractor is engaged in labor-only contracting, the principal may be deemed the real employer.

A worker assigned to a project through an agency should examine:

Who pays wages;
Who controls the work;
Who supplies tools and equipment;
Whether the contractor has substantial capital;
Whether the contractor carries an independent business;
Whether the worker performs tasks directly related to the principal’s business;
Whether the contracting arrangement is legitimate or labor-only.

Regularization may be claimed against the true employer depending on the facts.

XXVI. Indicators That a Project Employee Is Actually Regular

A worker labeled project-based may be considered regular if:

The work is necessary or desirable to the employer’s usual business;
The employee has served for at least one year in the same activity;
The employee is repeatedly rehired for the same role;
The contracts are continuously renewed;
The project is not clearly identified;
The project has no determinable completion;
The employee works even after project completion;
The employee is included in regular schedules;
The employee reports to regular supervisors;
The employee performs the same work as regular employees;
The employee is not free between projects;
The employer does not report project completion;
The employment arrangement appears designed to prevent regularization;
The worker occupies a position needed in the employer’s regular operations.

No single factor is always decisive. Labor tribunals examine the totality of circumstances.

XXVII. Indicators of Valid Project Employment

Project employment is more likely valid when:

The project is specific and identifiable;
The employee was informed at hiring that employment ends upon project completion;
The contract clearly identifies the project or phase;
The work is connected to that project;
The project has a real endpoint;
The employee’s service ends when the project ends;
The employer reports completion where required;
There are real gaps between projects;
Rehiring is not automatic;
The employee is not maintained as part of a permanent workforce;
The employer’s business is project-driven;
Documents consistently support the project arrangement.

XXVIII. The Burden of Proof

In labor disputes, the employer usually bears the burden of proving that the employee’s dismissal was valid and that the employment arrangement was lawful.

If the employer claims that the worker was a project employee, it must prove the factual basis of project employment.

Useful employer evidence may include:

Written project employment contracts;
Project documents;
Client contracts;
Work orders;
Notices of project completion;
DOLE reports;
Payroll records;
Assignment records;
Project timelines;
Employee acknowledgment of project terms;
Proof that the employee’s work ended with project completion.

For employees, useful evidence may include:

Repeated contracts;
Payslips;
IDs;
Schedules;
messages from supervisors;
Certificates of employment;
Attendance records;
Proof of continuous service;
Proof of same duties across contracts;
Comparisons with regular employees;
Organizational charts;
Company announcements;
Evidence that no specific project existed.

XXIX. Regularization: What It Means

Regularization means recognition that the employee is a regular employee, with security of tenure and rights attached to regular employment.

A regular employee cannot be dismissed merely because a contract expires. Termination must be based on:

Just causes, such as serious misconduct, willful disobedience, gross neglect, fraud, breach of trust, commission of a crime against the employer or immediate family, or analogous causes; or
Authorized causes, such as redundancy, retrenchment, closure, disease, or installation of labor-saving devices.

Due process is also required.

Regularization may also entitle the employee to benefits enjoyed by regular employees, depending on company policy, collective bargaining agreement, or law.

XXX. Does a Project Employee Automatically Become Regular After Six Months?

No. The six-month rule is commonly associated with probationary employment, not project employment.

A project employee does not automatically become regular after six months if the project employment is genuine.

However, if the project label is invalid and the employee is actually performing regular work, the employee may be deemed regular from the start or upon meeting legal standards, depending on the facts.

XXXI. Does a Project Employee Automatically Become Regular After One Year?

Not always.

The one-year rule is important, but a genuine project employee may remain project-based even if a project lasts more than one year.

However, an employee who has rendered at least one year of service, whether continuous or broken, in an activity necessary or desirable to the employer’s business may have a strong claim to regularization, especially if there is no genuine project basis.

The longer and more continuous the service, the stronger the regularization argument becomes.

XXXII. Can a Project Employee Be Dismissed Before the Project Ends?

Yes, but only for lawful cause and with due process.

A project employee may be terminated before project completion for just cause, such as serious misconduct or gross neglect, if procedural due process is followed.

A project employee may also be affected by authorized causes, such as genuine redundancy or closure, if legal requirements are met.

Without lawful cause, early termination may be illegal dismissal.

XXXIII. Are Project Employees Entitled to Separation Pay?

If the project ends as agreed, project employees are generally not entitled to separation pay merely because the project has been completed, unless provided by:

Contract;
Company policy;
Collective bargaining agreement;
Established employer practice;
Specific law or regulation;
Authorized cause termination rules.

However, if the employee is actually regular and is dismissed under the guise of project completion, remedies for illegal dismissal may apply.

If the project employee is terminated due to an authorized cause before completion, separation pay may be required depending on the cause.

XXXIV. Final Pay of Project Employees

Upon completion of the project or separation, a project employee may be entitled to final pay, including:

Unpaid salary;
Pro-rated 13th month pay;
Unused leave conversion, if applicable;
Refundable deposits or cash bonds, if any and lawful;
Other benefits under contract, policy, or law.

The employee may also request a certificate of employment.

Final pay is different from separation pay. Final pay covers amounts already earned or legally due.

XXXV. Certificate of Employment

A project employee may request a certificate of employment stating the nature and duration of employment and the type of work performed.

The certificate should not falsely characterize employment to defeat rights. If the employee disputes the project label, the certificate may become evidence in a labor case.

XXXVI. Illegal Dismissal Claims by Project Employees

A project employee may file an illegal dismissal complaint when:

They were dismissed before project completion without cause;
The supposed project ended but the project was not real;
The employee was actually regular;
The employer repeatedly used project contracts to avoid regularization;
The worker was dismissed after asserting labor rights;
The termination was discriminatory or retaliatory;
Due process was not observed.

Possible remedies include:

Reinstatement without loss of seniority rights;
Full backwages;
Recognition as regular employee;
Separation pay in lieu of reinstatement, when appropriate;
Unpaid wages and benefits;
Damages and attorney’s fees in proper cases.

XXXVII. Constructive Dismissal

Constructive dismissal occurs when an employee is forced to resign or stop working because continued employment becomes impossible, unreasonable, or unlikely due to the employer’s acts.

A project employee may claim constructive dismissal if:

The employer suddenly stops giving assignments despite continuing work;
The employer reduces pay to force resignation;
The employee is transferred to an impossible or unsafe assignment;
The employer refuses to renew because the worker asserted rights;
The employer imposes unreasonable conditions;
The employer harasses the worker after a regularization demand.

Constructive dismissal is fact-specific and must be supported by evidence.

XXXVIII. Floating Status and Project Employees

“Floating status” usually arises when work is temporarily unavailable, common in security services, agencies, and project/client-based operations.

For project employees, a genuine end of project may end employment. But if the worker is actually regular or maintained in a work pool, prolonged non-assignment may raise legal issues.

An employer cannot indefinitely keep a regular employee without work or pay to avoid termination obligations. If the employee is truly project-based and the project has ended, the relationship may end, subject to proper documentation.

XXXIX. Retaliation for Demanding Regularization

An employer may not lawfully dismiss, blacklist, harass, or penalize an employee for asserting labor rights.

A project employee who is suddenly not renewed after asking about regularization may still need to prove that the non-renewal was illegal or that the project arrangement was not genuine. Evidence of retaliation can strengthen the case.

Useful evidence includes:

Messages about the regularization request;
Timing of termination;
Replacement by another worker doing the same job;
Continued existence of the same work;
Statements by supervisors;
Prior renewals before the complaint.

XL. Regularization and Company Benefits

Once regular status is recognized, the employee may claim benefits provided to regular employees, depending on the source of the benefit.

Benefits may arise from:

Law;
Employment contract;
Company policy;
Employee handbook;
Collective bargaining agreement;
Established practice.

Examples:

Leave benefits;
Health insurance;
Rice subsidy;
Meal allowance;
Transportation allowance;
Performance bonus;
Retirement benefits;
Seniority-based benefits.

Not every benefit automatically applies retroactively, but regularization may affect entitlement depending on the facts and policy language.

XLI. Union Rights of Project Employees

Project employees may have rights to self-organization and collective bargaining, depending on the nature of their employment and bargaining unit.

Temporary status does not automatically erase labor rights. However, eligibility, bargaining unit inclusion, and voting rights in certification elections can become complex where workers are project-based, seasonal, or intermittent.

If project employees perform work comparable to regular employees and are repeatedly engaged, they may have stronger arguments for inclusion in appropriate labor representation issues.

XLII. Occupational Safety and Health

Project employees are entitled to safe and healthful working conditions.

This is especially important in construction, manufacturing, logistics, shipbuilding, mining-related services, and field operations.

Employers must provide appropriate safety measures, training, protective equipment, and compliance with occupational safety standards. Project status does not excuse unsafe conditions.

A project employee injured at work may have rights under employees’ compensation, social security, company policy, and civil or criminal law depending on the circumstances.

XLIII. Discrimination and Harassment

Project employees are protected against unlawful discrimination and harassment.

An employer cannot use project status to justify discrimination based on sex, gender, pregnancy, disability, age, union activity, religion, or other protected grounds.

Pregnant project employees, for example, may not be dismissed simply because of pregnancy. If a genuine project ends, that is a separate matter; but pregnancy cannot be the reason for termination or non-renewal where work continues and the project label is pretextual.

XLIV. Maternity, Paternity, Solo Parent, and Other Statutory Benefits

Project employees may be entitled to statutory benefits if they meet the legal conditions. These may include:

Maternity benefits;
Paternity leave;
Solo parent leave;
Special leave benefits for women, where applicable;
Service incentive leave;
Social security benefits;
Employees’ compensation benefits.

The availability and computation of benefits may depend on length of service, contributions, employment status, and applicable rules.

XLV. Effect of Signing a Project Employment Contract

Signing a project employment contract does not automatically defeat a regularization claim.

The law looks at reality. A worker may sign project contracts because they need work and have little bargaining power. If the arrangement is contrary to law, the employee may still challenge it.

However, signed contracts are evidence. A clear, specific, and consistently implemented project contract strengthens the employer’s defense. A vague or repeated contract may strengthen the employee’s claim.

Employees should keep copies of all contracts, amendments, notices, payslips, IDs, and communications.

XLVI. Quitclaims and Waivers

Employers sometimes require project employees to sign quitclaims, waivers, or releases at the end of each project.

A quitclaim is not automatically invalid. But Philippine labor law treats quitclaims with caution. A waiver may be disregarded if:

The employee was forced or pressured;
The consideration was unconscionably low;
The employee did not understand the document;
The waiver covers future rights;
The waiver was used to defeat labor standards;
The employee did not actually receive the amounts stated;
The arrangement was contrary to law.

A quitclaim does not necessarily prevent a worker from later claiming regularization or illegal dismissal if the facts support the claim.

XLVII. Evidence Employees Should Preserve

A project-based worker who suspects illegal non-regularization should preserve:

Employment contracts;
Appointment letters;
Project assignment notices;
Company ID;
Payslips;
Payroll records;
Attendance records;
Timekeeping screenshots;
Work schedules;
Emails or chats from supervisors;
Job descriptions;
Performance evaluations;
Certificates of employment;
Photos of workplace postings;
Proof of repeated rehiring;
Proof of same tasks across contracts;
Names of co-workers and supervisors;
Company policies;
Notices of project completion or lack thereof;
Proof that the work continued after termination.

Documentation often determines the outcome of labor disputes.

XLVIII. Employer Best Practices

Employers that genuinely need project employment should:

Use written contracts;
Identify the specific project or phase;
State the completion standard;
Inform employees at hiring of project duration or endpoint;
Avoid vague “project” descriptions;
Avoid continuous renewals for regular work;
Keep project documents;
Report project completion where required;
Pay all statutory benefits;
Avoid using project contracts as substitutes for probationary or regular employment;
Separate project roles from regular plantilla roles;
Conduct legal audits of long-serving project workers;
Regularize workers who perform continuing core functions;
Train HR and managers on lawful classification.

A poorly documented project arrangement can become costly in litigation.

XLIX. Employee Practical Guide: How to Assess a Regularization Claim

A project-based employee may ask:

What exact project was I hired for?
Was the project identified in my contract?
Was I told when or how the project would end?
Did I continue working after the project supposedly ended?
Have I been repeatedly rehired?
Do I perform the same work as regular employees?
Is my work necessary to the company’s usual business?
Have I served at least one year in the same activity?
Does the company keep me continuously scheduled?
Can I work elsewhere between projects?
Did the employer report project completion?
Was I dismissed even though the work continues?
Was I replaced by another project worker doing the same task?
Are my contracts vague or identical except for dates?
Did I sign quitclaims after each renewal?

The more “yes” answers to these questions, the stronger the possible regularization claim.

L. Filing a Labor Complaint

A project employee who believes they were illegally denied regularization or illegally dismissed may file a complaint with the appropriate labor office or arbitration body.

Common claims include:

Illegal dismissal;
Regularization;
Nonpayment of wages;
Nonpayment of overtime;
Nonpayment of holiday pay;
Nonpayment of 13th month pay;
Non-remittance of benefits;
Damages;
Attorney’s fees.

The process may involve mandatory conciliation and mediation before formal adjudication. If unresolved, the case may proceed before the labor arbiter.

Workers should act promptly because labor claims may be subject to prescriptive periods.

LI. Remedies If the Employee Wins

If the worker proves that they were actually regular and illegally dismissed, possible remedies include:

Reinstatement without loss of seniority rights;
Full backwages;
Recognition of regular status;
Payment of wage differentials;
Payment of unpaid benefits;
13th month pay deficiencies;
Service incentive leave pay, if applicable;
Damages in proper cases;
Attorney’s fees;
Separation pay in lieu of reinstatement, where reinstatement is no longer viable.

If the worker proves labor standards violations but not regular status, monetary awards may still be granted.

LII. Prescription of Claims

Labor claims must be filed within legal prescriptive periods. The applicable period depends on the nature of the claim.

For example:

Money claims under the Labor Code generally have a three-year prescriptive period.
Illegal dismissal claims are commonly treated differently from ordinary money claims and must be pursued within the applicable period recognized by law and jurisprudence.
Social security, PhilHealth, Pag-IBIG, and employees’ compensation issues may have separate agency procedures and timelines.

Because deadlines can be outcome-determinative, workers should not delay.

LIII. Common Myths

“Project-based employees can be fired anytime.”

False. A project employee cannot be dismissed before project completion without lawful cause and due process.

“If you signed a project contract, you can never become regular.”

False. The actual nature of work controls.

“Project employees have no benefits.”

False. Project employees are entitled to labor standards and statutory benefits.

“After six months, every project employee becomes regular.”

False. The six-month rule applies mainly to probationary employment. But invalid project employment may result in regular status.

“After one year, project employees always become regular.”

Not always. Genuine project employment can last more than one year. But long, repeated, or continuous service may support regularization.

“End of contract is always valid.”

False. If the contract is a device to avoid regularization, ending it may be illegal dismissal.

“Construction workers can never become regular.”

False. Construction workers may become regular depending on repeated rehiring, nature of work, and employer practice.

“No written contract means project employment.”

False. Lack of a clear written project contract may actually weaken the employer’s project employment defense.

LIV. Illustrative Situations

Situation 1: Genuine project employee

A structural welder is hired for the steel works phase of a specific building project. The contract identifies the site, phase, and completion standard. When the steel works phase ends, the welder’s employment ends.

This may be valid project employment.

Situation 2: Disguised regular employee

A graphic designer signs “project contracts” every three months for three years, works at the company office daily, reports to the same manager, produces regular marketing materials, and is immediately replaced when the latest contract ends.

This may support a claim for regularization and illegal dismissal.

Situation 3: Long project but still project-based

An engineer is hired for a specific infrastructure project expected to last two years. The contract clearly identifies the project, and employment ends when the project is completed.

The length alone does not automatically make the engineer regular.

Situation 4: Repeated construction rehiring

A mason is hired by the same construction company for successive projects over seven years, with minimal gaps, same supervisors, and continuous assignment. The company maintains him in a work pool and calls him whenever work is available.

The result depends on facts, but the mason may have a strong regularization argument.

Situation 5: BPO account-based worker

A customer service representative is told they are project-based because they are assigned to a client account. The account continues indefinitely, the worker performs the company’s usual outsourced service, and contracts are repeatedly renewed.

The worker may argue that the arrangement is regular employment, not genuine project employment.

LV. Special Issue: Client-Based or Account-Based Employment

Employers sometimes classify workers as project-based because their work depends on a client contract or account.

A client account may be a legitimate project in some cases, especially if the engagement is specific, time-bound, or deliverable-based. But not every client account creates project employment.

Questions include:

Is the client contract for a specific project or ongoing service?
Was the employee hired only for that client contract?
Was the end of the client contract known or determinable?
Does the employer regularly provide the same service to many clients?
Is the employee’s work part of the employer’s usual business?
Was the employee transferred to another account after the supposed project?
Were contracts repeatedly renewed without real project completion?

Calling a regular business account a “project” does not automatically make employees project-based.

LVI. Special Issue: Project-Based Managers and Professionals

Managers, engineers, consultants, designers, accountants, analysts, and other professionals may also be project employees if hired for a specific undertaking.

However, high skill or professional status does not automatically remove labor protection. The same tests apply:

Was there an employer-employee relationship?
Was the project specific?
Was the endpoint known?
Was the work part of regular business?
Was the worker repeatedly engaged?

Some professionals may be independent contractors rather than employees, but this depends on control, tools, method of payment, independence, and integration into the business.

LVII. Special Issue: Remote and Online Project Workers

Remote work has increased project-based arrangements.

A remote worker may be project-based if hired for a specific deliverable, such as designing a website, creating a campaign, or completing a research assignment.

But a remote worker may be regular if they:

Follow fixed daily hours;
Report to company supervisors;
Use company systems;
Perform continuing business functions;
Receive regular wages;
Are integrated into the company’s operations;
Work continuously for the employer.

Remote status does not determine employment status. The nature of the relationship does.

LVIII. Regularization Without a Written Appointment

An employee may become regular by operation of law even without a written regularization notice.

Employers sometimes fail to issue regular appointment papers despite continuous regular work. The absence of a regularization letter does not prevent legal regular status if the facts and law support it.

Likewise, a contract saying “project-based” does not prevent regularization if the arrangement is unlawful.

LIX. Management Prerogative and Its Limits

Employers have management prerogative to organize their workforce, hire for projects, and structure operations. But management prerogative must be exercised in good faith and in accordance with labor law.

It cannot be used to:

Circumvent security of tenure;
Misclassify regular employees;
Avoid statutory benefits;
Retaliate against workers;
Discriminate;
Dismiss employees without cause.

Project employment is lawful only when genuinely project-based.

LX. Conclusion

Project-based employment is recognized in the Philippines, but it is not a loophole to avoid regularization. A worker is not project-based simply because the contract says so. The project must be specific, real, and determinable. The employee must know at the time of hiring that employment is tied to that project. The end of employment must correspond to actual project completion.

A project employee may become entitled to regularization when the work is necessary or desirable to the employer’s usual business, when service reaches one year with respect to the same activity, when contracts are repeatedly renewed, when the supposed projects are vague or fictitious, or when the employee is effectively part of the employer’s regular workforce.

Project employees are also entitled to labor standards and statutory benefits. They cannot be dismissed before project completion without lawful cause and due process. If they are actually regular employees, termination based on “end of project” or “end of contract” may amount to illegal dismissal.

For employees, the most important steps are to preserve documents, check the real nature of the work, and act promptly if rights are violated. For employers, the best protection is honest classification, clear project documentation, lawful payment of benefits, and regularization of workers who perform continuing core functions.

The central rule is substance over form: Philippine labor law looks beyond labels and protects employees according to the true nature of their work.