Project-Based Employment Philippines 2026: Rights, Contracts & When You Become Regular
Last materially reviewed: August 16, 2026
Regular employment is the default position under the Labor Code. Project employment is an exception to it — and because it is an exception, the employer is the one who has to prove it applies.
That framing matters, because most discussion of project employment starts from the opposite end: whether a particular contract is a scheme. This guide takes the other question. What does a valid project engagement actually require, and what evidence establishes it? If you suspect a project label is being used to prevent regularization, our guide on what endo is covers that pattern, and how to file a labor complaint covers the remedy.
Direct Answer
A project employee is one engaged for a specific project or undertaking whose completion or termination was determined at the time of engagement. Article 295 of the Labor Code makes this an express exception to regular employment, so the burden of proving it rests on the employer. Department Order No. 19, Series of 1993 sets out indicators of genuine project employment, including that the project’s duration be reasonably determinable and made clear at hiring, and that the employee’s termination be reported to the DOLE Regional Office within 30 days of separation. Where a project employee is continuously rehired for tasks vital to the employer’s usual business, the Supreme Court has held that regular status follows.
Project-Based Employment Validity Checklist
Before accepting a project-based label, check these five points. The more of them that are missing, the harder it is for the employer to prove genuine project employment under Article 295.
- Specific project: Does the contract identify an actual project, undertaking, client engagement or defined phase?
- Known at hiring: Was the project and the event that ends the engagement made clear when you were hired, not added later?
- Connected work: Is the work you actually perform tied to that identified project rather than to general continuing operations?
- Real completion event: Did employment end because that project or phase genuinely ended?
- Rehiring pattern: Have you been continuously rehired for the same core tasks that are vital to the employer’s usual business? If yes, regularization becomes a major issue under Supreme Court jurisprudence.
Important: This checklist is a screening tool, not a legal determination. A valid project arrangement is assessed from the contract, the actual project, the employer’s records, the employee’s work, and the rehiring history as a whole.
Decision Snapshot
| Question | Practical answer |
|---|---|
| Who this applies to | Employees engaged for a named project or undertaking rather than for continuing work, and employers who need the classification to hold up. It arises most often in construction, but the principles have been applied wherever project engagement is used — IT implementations, client-account ramp-ups, events and film production among them. |
| Core rule | Article 295 deems employment regular where the employee performs activities usually necessary or desirable in the employer’s usual business, “except where the employment has been fixed for a specific project or undertaking the completion or termination of which has been determined at the time of the engagement of the employee.” The determination must exist at engagement, not be supplied afterwards. |
| Main boundary | Project employment is not fixed-term employment and not independent contracting. A project employee is an employee, with the same statutory benefits; what differs is that the engagement lawfully ends when the identified project ends. Completion of a genuine project is not an authorized-cause termination and does not by itself trigger the separation pay that authorized causes carry. |
| Key evidence | The employment contract naming the specific project and stating its duration or the event that ends it; the project plan, client contract or work order proving the project exists; deployment and assignment records; the completion report or certificate; the DOLE termination report; and the rehiring history across engagements. |
| Deadline / rate / period | Under the D.O. 19 indicators, the termination of employment in the particular project should be reported to the DOLE Regional Office with jurisdiction over the workplace within 30 days of separation. The determination of the project’s completion must exist at the time of engagement. |
| First next step | Read the contract you actually signed and check whether it names a specific project and says how the engagement ends. If it states only a start and end date with no identified project, that is the single most important fact in the file — and it is what the Supreme Court relied on in Malicdem. |
Key Takeaways
- Regular is the default; project is the exception. The employer carries the burden.
- “Determined at the time of engagement” is the whole test. A project identified afterwards does not count.
- The duration must be determinable, not necessarily a fixed date. “Until the identified project is completed” can suffice; “six months” attached to nothing cannot.
- A dated contract with no named project is not a project contract.
- The DOLE termination report is a recognised indicator. Its absence, repeated across engagements, cuts against the classification.
- Continuous rehiring for vital tasks produces regular status — two conditions, both required.
- Project employees are employees. Full statutory benefits, and protection against dismissal before the project ends.
- Genuine completion is not dismissal, and not an authorized cause either.
Table of Contents
- Legal basis
- Project employment as an exception, and who must prove it
- What “determined at the time of engagement” requires
- The six indicators under D.O. 19
- The DOLE termination report
- Rehiring across successive projects: when project status converts to regular
- What project employment is not
- Ending the engagement: completion is not dismissal
- Evidence and documentation
- Common mistakes
- Practical examples
- What to do next
- Frequently asked questions
Legal Basis
| Authority | Rule supported | Type |
|---|---|---|
| Labor Code, Article 295 (formerly 280) | Regular employment as the default; project employment as an express exception where completion or termination was determined at the time of engagement; the seasonal exception; the one-year rule for casual employees. | Statute |
| Department Order No. 19, Series of 1993 — Guidelines Governing the Employment of Workers in the Construction Industry | The indicators of project employment, including the determinable duration, disclosure at hiring, freedom to work elsewhere between engagements, the 30-day DOLE termination report, and the completion bonus. | Department Order |
| Samson v. National Labor Relations Commission, G.R. No. 113166, 1 February 1996 | Sets out the D.O. 19 indicators of project employment as the framework for assessing the classification. | Supreme Court |
| Maraguinot, Jr. v. National Labor Relations Commission, G.R. No. 120969, 22 January 1998 | The two conditions under which a project or work-pool employee acquires regular status: continuous rehiring, and tasks vital, necessary and indispensable to the employer’s usual business. | Supreme Court |
| Malicdem v. Marulas Industrial Corporation, G.R. No. 204406, 26 February 2014 | Applies the two conditions; holds that contracts stating only effectivity dates and duties, with no identified project, do not establish project employment. | Supreme Court |
Project Employment as an Exception, and Who Must Prove It
Article 295 provides that “an employment shall be deemed to be regular where the employee has been engaged to perform activities which are usually necessary or desirable in the usual business or trade of the employer, except where the employment has been fixed for a specific project or undertaking the completion or termination of which has been determined at the time of the engagement of the employee or where the work or service to be performed is seasonal in nature and the employment is for the duration of the season.”
Read the grammar of that sentence. Regular employment is the rule, and project employment appears after the word except. That single structural fact drives most outcomes: where the classification is disputed, the employer is asserting the exception and therefore has to establish it. An employee does not have to disprove project status; the employer has to prove it.
The consequence in practice is evidentiary. If the employer cannot produce a contract identifying the project, cannot show the duration was determinable at hiring, and cannot show the engagement actually ended because the project ended, the exception fails and the default applies.
On what makes work “necessary or desirable” in the first place, and on how regularization operates by law, see our guide on casual employment and the necessary-or-desirable test.
What “Determined at the Time of Engagement” Requires
Every summary of project employment repeats this phrase. Few unpack it, and the unpacking is where cases are actually won and lost.
It is a requirement about timing. The determination must exist when the employee is engaged. A project scoped, named or documented after the fact does not retroactively make an earlier hire a project hire.
It is a requirement about the project, not only the dates. The thing determined is “a specific project or undertaking”. A contract that fixes a start and an end date but identifies no project has determined a period, not a project. In Malicdem v. Marulas Industrial Corporation the Supreme Court found precisely this: “there is no actual project. The only stipulations in the contracts were the dates of their effectivity, the duties and responsibilities of the petitioners as extruder operators, the rights and obligations of the parties, and the petitioners’ compensation and allowances.”
The duration must be determinable, not necessarily a calendar date. Under the D.O. 19 indicators the duration must be “reasonably determinable”. Projects rarely finish on a date fixed in advance, and the law does not require them to. What it requires is that the end be knowable by reference to something identified at the outset — the completion of a named undertaking, the delivery of a defined phase, the conclusion of a specific client engagement. “Until the ABC Tower fit-out is completed” is determinable. “For six months” attached to no project is not.
It has to be made clear to the employee. The second D.O. 19 indicator requires that the duration and the specific work be “defined in an employment agreement and is made clear to the employee at the time of hiring.” A determination that lives only in the employer’s internal planning does not satisfy it.
The Six Indicators Under D.O. 19
Department Order No. 19, Series of 1993 issued the Guidelines Governing the Employment of Workers in the Construction Industry. It was written for construction, and it remains the clearest official statement of what genuine project employment looks like. In Samson v. NLRC the Supreme Court set out its indicators, and they are worth having in full because no other single source collects them:
- “The duration of the specific/identified undertaking for which the worker is engaged is reasonably determinable.”
- “Such duration, as well as the specific work/service to be performed, is defined in an employment agreement and is made clear to the employee at the time of hiring.”
- “The work/service performed by the employee is in connection with the particular project/undertaking for which he is engaged.”
- “The employee, while not employed and awaiting engagement, is free to offer his services to any other employer.”
- “The termination of his employment in the particular project/undertaking is reported to the Department of Labor and Employment (DOLE) Regional Office having jurisdiction over the workplace within 30 days following the date of his separation from work, using the prescribed form on employees’ terminations dismissals suspensions.”
- “An undertaking in the employment contract by the employer to pay completion bonus to the project employee as practiced by most construction companies.”
Two of these deserve attention because they are so often missed.
Indicator 4 — freedom between engagements. A genuine project employee is not on standby for the employer between projects. Where a worker is required to remain available, is discouraged from taking other work, or is treated as continuously employed with gaps, the arrangement looks less like a series of project engagements and more like continuing employment interrupted for convenience. For the broader classification framework, see Regular vs Probationary vs Project vs Casual Employee in the Philippines.
Indicator 6 — the completion bonus. An undertaking to pay a completion bonus points toward genuine project employment because it presupposes a real completion event. Its absence is not fatal, but its presence is corroborative.
These are indicators, not a checklist where a fixed number must be ticked. They are read together with the statutory requirement and with the actual conduct of the parties.
The DOLE Termination Report
Indicator 5 deserves its own treatment, because it is the most practically decisive item on the list and the one employers most often overlook.
The indicator asks whether the termination of employment in the particular project was reported to the DOLE Regional Office having jurisdiction over the workplace within 30 days of separation, on the prescribed form.
Why it carries so much weight: it is a contemporaneous act. A contract can be drafted to say whatever the employer wants, and can be produced years later in a dispute. A report filed with a government office within 30 days of each project ending is a record made at the time, by the employer, treating the separation as what it claims the separation was. Where an employer has genuinely been running project engagements, the reports usually exist. Where the “projects” are a paper arrangement over continuing work, they usually do not.
Two cautions on how to read this.
A single missing report does not decide anything. It is one indicator among six, and the assessment is made on the whole picture.
The absence is most telling when it is a pattern. An employer claiming five successive project engagements over four years, with no termination report filed for any of them, is asking a tribunal to accept a classification its own records never reflected.
For employers, the operational point is simple: if you engage project employees, file the report each time, keep the acknowledgement, and keep it with the completion documents. It is the cheapest evidence in the file.
Rehiring Across Successive Projects: When Project Status Converts to Regular
This is a different question from the one the endo pages address, and the distinction is worth stating plainly.
Repeated short contracts covering the same continuing job — the five-month contract renewed indefinitely — is the endo pattern, and it is covered in our guide on endo. The question here is narrower and less obvious: what happens when the projects are genuine, but the same worker is engaged for one after another?
In Maraguinot, Jr. v. NLRC the Supreme Court set two conditions. A project or work-pool employee acquires regular status where:
- “There is a continuous rehiring of project employees even after cessation of a project”; and
- “The tasks performed by the alleged project employee are vital, necessary and indispensable to the usual business or trade of the employer.”
The Court restated the same test in Malicdem: once a project or work-pool employee has been “(1) continuously, as opposed to intermittently, re-hired by the same employer for the same tasks or nature of tasks; and (2) these tasks are vital, necessary and indispensable to the usual business or trade of the employer, then the employee must be deemed a regular employee.”
Three things follow.
Both conditions are required. Continuous rehiring alone does not convert status if the tasks are peripheral to the business. Vital tasks alone do not convert status if the engagements were genuinely intermittent.
“Continuously, as opposed to intermittently” is the operative contrast. A specialist engaged for three unrelated projects across five years, free to work elsewhere in between, is intermittent. Someone moved directly from project to project with no real break, performing the same core function, is continuous.
Conversion does not require bad faith. An employer can run entirely genuine projects and still end up with regular employees, simply because it has kept rehiring the same people for work central to what it does. That is not a penalty; it is what Article 295 says about work that is necessary or desirable to the usual business.
What Project Employment Is Not
| Not this | The difference | Where it is covered |
|---|---|---|
| Fixed-term employment | A fixed term is defined by a period agreed between the parties. Project employment is defined by an undertaking. A project engagement may have no calendar end date at all and still be valid. | Security of tenure |
| Independent contracting | A project employee is an employee. Being paid per project does not make someone a contractor; the four-fold test decides that, and control is the decisive element. | Employee vs independent contractor |
| Probationary employment | Probation is a trial period against disclosed standards under a different article. A project engagement is not a trial and does not end because the employee failed to qualify. | The six-month probation period |
| Casual employment | Casual is the residual category for work outside the usual business. Project work is frequently central to the business — that is why the exception has to be established rather than assumed. | Casual employment |
| Endo or contractualization | Endo is the misuse of short engagements to defeat regularization. Genuine project employment is lawful; the endo question only arises where the project is not real. | What is endo |
The through-line: a project employee has every right an employee has. Statutory benefits, safe working conditions, protection from dismissal without cause during the engagement. The classification affects when the employment lawfully ends, not what is owed while it runs.
Ending the Engagement: Completion Is Not Dismissal
When a genuine project ends, the employment ends with it. That is not a dismissal, and it does not require a just or authorized cause — the engagement simply reaches the terminus that was set at the beginning.
Three consequences follow, and they are frequently confused.
The twin-notice procedure does not apply. That process exists for dismissal for just cause. Completion of a project is not a disciplinary event.
Nor is it an authorized-cause termination. Redundancy, retrenchment, closure and the rest each carry a 30-day notice to the employee and to DOLE, and separation pay at the statutory rate. Project completion is a different mechanism, and the separation pay attached to authorized causes does not follow from it. What the employer must still do is settle final pay — earned wages, pro-rated thirteenth-month pay and any unused leave conversion due. See authorized-cause termination for the contrast, and final pay for what is owed on exit.
Ending the engagement before the project ends is a dismissal. This is the point most often missed. A project employee is protected during the engagement. Cutting it short requires a lawful ground and due process exactly as it would for anyone else — see legal termination versus illegal dismissal.
Evidence and Documentation
Because the employer carries the burden, the file is the case.
| Document | What it establishes |
|---|---|
| The employment contract for each engagement | Whether a specific project was named and how the engagement was said to end — the first thing any tribunal reads. |
| Project plan, client contract, purchase order or work order | That the project existed independently of the employment contract, with its own scope and timeline. |
| Deployment, assignment and site records | That the employee actually worked on the identified project rather than on general operations. |
| Completion report or certificate of project completion | That the project genuinely ended, and when — the event the engagement was keyed to. |
| DOLE termination report and its acknowledgement | A contemporaneous record that the employer itself treated the separation as project completion. Indicator 5. |
| The full rehiring history across engagements | Whether re-engagement was continuous or intermittent — the first Maraguinot condition. |
| Job description and organisational context | Whether the tasks are vital, necessary and indispensable to the usual business — the second condition. |
| Payslips and payroll records across engagements | Whether pay actually stopped between projects, or continued as if employment never broke. |
Common Mistakes
A contract with dates but no project. The most common defect, and the one that decided Malicdem. A period is not a project.
Naming the project only in an internal document. Indicator 2 requires it be defined in the employment agreement and made clear to the employee at hiring.
Treating “project-based” as a label that travels. Writing “project-based” in a contract for someone doing continuing core work does not create the exception. Classification follows the facts.
Never filing the DOLE termination report. Cheap to do, expensive to have skipped across five engagements.
Keeping people on standby between projects. This cuts against indicator 4 and pushes the arrangement toward continuous employment.
Assuming genuine projects protect against regularization forever. Maraguinot says otherwise where rehiring is continuous and the tasks are vital.
Withholding statutory benefits because someone is “only project-based”. A project employee is an employee.
Terminating mid-project without cause. That is a dismissal, and it needs a ground and due process.
Practical Examples
Example 1 — a valid project engagement. A software firm wins a contract to implement an ERP system for a named client, scheduled across roughly eleven months. It hires a data-migration specialist under a contract identifying the client engagement, describing the migration workstream, and stating that employment runs until that workstream is completed. She is free to take other work afterwards. On completion the firm issues a completion report and files the DOLE termination report within 30 days. This has the structure the law is looking for: a real undertaking, identified at hiring, disclosed to the employee, ending when the undertaking ended, and documented at the time.
Example 2 — dates without a project. A manufacturer hires a machine operator on successive contracts, each stating only a start date, an end date, duties and pay. No project is named anywhere. The operator runs the same production line throughout. This is the Malicdem fact pattern — the contracts determined a period, not a project, and the exception in Article 295 was never engaged.
Example 3 — genuine projects, continuous rehiring. A BPO staffs client account ramp-ups on a project basis. One team leader is moved directly from one client ramp-up to the next for four years with no real gap, always performing the same core function, which is what the company does for a living. Even if each ramp-up was a genuine project, both Maraguinot conditions look satisfied — continuous rather than intermittent rehiring, and tasks vital to the usual business. Regular status is the likely outcome.
Example 4 — cut short. An events company engages a production coordinator for a named festival running to October. In July, with the festival proceeding as planned, it ends her engagement because it has found someone cheaper. The project did not end, so the engagement did not reach its terminus. That is a dismissal and requires a lawful ground and due process.
What to Do Next
If you are an employee: get a copy of every contract you signed, and check the first page of each for a named project. Then write down your engagement dates and any gaps between them — continuity is half of the Maraguinot test. Ask, in writing, for the completion report and the DOLE termination report for each engagement that has ended.
If you think a project label is being used to prevent regularization: that is the endo question rather than the validity question — see what endo is, and how to file a labor complaint for the route, the forum and the deadlines.
If you are an employer: name the project in the contract, state how the engagement ends, disclose it at hiring, keep the project documentation separate from the employment file, file the DOLE termination report within 30 days each time, and review anyone who has been rehired continuously for core work — that population is where the classification is most exposed.
If the engagement was cut short before completion: treat it as a dismissal question, not a classification question, and see how to file an illegal dismissal case.
Related employment-status guide: When the dispute is whether the worker was truly employed by the company, compare the contract and actual working relationship using the Four-Fold Test for employer-employee relationships.
For the definition-first rule behind regularization, see regular employment meaning.
Frequently Asked Questions
What is project employment in the Philippines?
Employment for a specific project or undertaking whose completion or termination was determined at the time the employee was engaged. It is an express exception to regular employment under Article 295 of the Labor Code.
Who has to prove that someone is a project employee?
The employer. Regular employment is the default under Article 295, and project employment is the exception being asserted.
Does a project contract need a specific end date?
Not necessarily. The duration must be reasonably determinable — an identified completion event can be enough. What does not work is a period with no project attached to it.
Is project-based the same as fixed-term?
No. A fixed term is defined by an agreed period; project employment is defined by an identified undertaking.
Are project employees entitled to 13th-month pay and other benefits?
Yes. A project employee is an employee and receives the statutory benefits that go with employment.
When does a project employee become regular?
Under Maraguinot v. NLRC, where there is continuous rehiring even after a project ends and the tasks performed are vital, necessary and indispensable to the employer’s usual business. Both conditions are needed.
What is the DOLE termination report and does it matter?
It is a report of the employee’s separation filed with the DOLE Regional Office with jurisdiction over the workplace within 30 days, on the prescribed form. It is one of the D.O. 19 indicators of genuine project employment, and a consistent failure to file it across engagements weighs against the classification.
Do I get separation pay when a project ends?
Completion of a genuine project is not an authorized-cause termination, so the separation pay attached to authorized causes does not follow from it. Final pay — earned wages, pro-rated thirteenth-month pay and any leave conversion due — is still payable.
Can I be terminated before the project finishes?
Only on a lawful ground and with due process. Ending the engagement early is a dismissal, not a completion.
Does D.O. 19 apply outside construction?
It was issued for the construction industry. Its indicators have been treated as the reference framework for assessing project employment more broadly, and the Supreme Court set them out in Samson v. NLRC.
Related LaborCode.ph Guides
- Project employment — glossary definition
- Casual employment and the necessary-or-desirable test
- What is endo in the Philippines
- How to file a labor complaint over endo
- Security of tenure
- The six-month probation period
- Employee vs independent contractor
- Legal termination versus illegal dismissal
- Authorized-cause termination
- Final pay
Sources and Legal Citations
- Labor Code of the Philippines, Presidential Decree No. 442, as amended, Article 295 (formerly Article 280) — Regular and casual employment; the project and seasonal exceptions.
- Department Order No. 19, Series of 1993 — Guidelines Governing the Employment of Workers in the Construction Industry; indicators of project employment.
- Samson v. National Labor Relations Commission, G.R. No. 113166, 1 February 1996 — Enumeration of the D.O. 19 indicators of project employment.
- Maraguinot, Jr. v. National Labor Relations Commission, G.R. No. 120969, 22 January 1998 — The two conditions for a project or work-pool employee to acquire regular status.
- Malicdem v. Marulas Industrial Corporation, G.R. No. 204406, 26 February 2014 — Contracts stating only dates and duties, with no identified project, do not establish project employment.
Disclaimer
This article is for general educational and legal-information purposes only. It is not legal advice and does not create a lawyer-client relationship. Whether an engagement is genuine project employment depends on the contract, the existence and scope of the project, the conduct of the parties, the rehiring history and the specific facts, and outcomes are assessed case by case. For a binding determination, consult a qualified Philippine labor law practitioner or the Department of Labor and Employment.
