A construction company can build a ₱100-million project from the ground up and still find itself on shaky ground because of something as simple as a poorly written employment contract.

It sounds strange, but it happens. Construction has its own rhythm. Projects start and end. Workers move from one site to another. Contractors and subcontractors work side by side. Deadlines mean long hours, and site supervisors make quick decisions on the spot. Sometimes the HR paperwork only catches up after the work has already begun.

That is one place where labor problems can start. A worker is called a “project employee,” but nobody can say clearly for which project. A subcontractor is treated as a convenient shield against liability. Ten-hour days become “normal.” A foreman says, “Do not come back tomorrow,” and a dismissal case is born.

None of these situations means the company has broken the law. In construction, the legal problem is often not that the company had no document — it is that the documents tell different stories. And when a dispute comes, the company has to prove what actually happened. Its own records can be its strongest defense or its biggest problem.

Here are ten traps worth watching, and what to do about each one.

1. “We are a Construction Company, So Everyone Is a Project Employee.”

Being in the construction business does not automatically make every worker a project employee. Under Article 295 of the Labor Code, a project employee is hired for a specific project or undertaking, and the end of that project was either fixed or could be determined when the worker was hired.

The Supreme Court recognizes that construction companies handle separate and distinct projects, so hiring people for a particular project is perfectly legitimate. The catch is that the worker must be told, at the time of hiring, which project it is and how long the work is expected to last. DOLE’s construction guidelines (Department Order No. 19, Series of 1993) point the same way: the work and its duration should be spelled out in the employment agreement and made clear from the start.

The end point does not have to be a calendar date. It can be tied to the completion of the project or of a particular phase, as long as the worker was properly informed.

So a contract that only says “You are hired as a project employee” is not enough. At minimum, the law requires it to identify the project, the phase, and the duration. As a matter of good practice, it should also spell out what happens once the work is done. DOLE’s construction guidelines also point to other useful indicators of genuine project employment: whether the worker is free to offer his services elsewhere while waiting for the next project, whether the contract promises a completion bonus (a common construction-industry practice), and whether the termination is properly reported to DOLE.

What to do: keep a project employment file for every project worker showing:

• the project name, location and owner;
• the worker’s position and assigned phase or work;
• the date of hiring and the expected end (or how it will be determined);
• the actual deployment; and
• the completion and separation dates.

Quick test: if the company calls someone a project employee, the documents should tell the same story.

2. “We have Hired Him Project After Project for Years, So He is Still a Project Employee.”

Sometimes, yes. The Supreme Court has held that being rehired for many projects does not, by itself, make a worker regular. What counts is whether each engagement was really tied to a distinct project whose scope and duration were made known at the start. In Dacles v. Millennium Erectors (2015), a mason hired for successive projects remained a project employee because his signed contracts named the projects and said his work would end on completion of the project or phase, and the company reported his termination to DOLE each time.

But the opposite can also happen. In Tomas Lao Construction v. NLRC (1997), workers were moved among related construction companies and rehired again and again for years, with a continuing need for their services. The Court held that they had become regular employees. The company had also handed out “project employment” contracts years into their employment, backdated, and the Court saw this as an attempt to get around security of tenure.

So repeated project employment is not automatically unlawful. The danger is not longevity by itself — it is evidence that the supposed project arrangement does not actually match how the company really runs its business. Repeated hiring becomes a serious warning sign when the company’s actual practices and records show continuing employment rather than genuinely separate project engagements. A project contract works best when it records the arrangement at the beginning, not when it is produced years later to explain an arrangement that was never documented.

Quick test: if this worker filed a complaint tomorrow, could we prove which project he was hired for, what work he was assigned to do, when that project or phase was expected to end, and what happened when it ended?

3. “The Project Ended, So His Employment Ended Automatically.”

The law allows project employment to end when the project, or the phase the worker was hired for, is completed. But “the project is finished” is a conclusion, not a fact. Completion is generally measured against the date originally agreed upon or indicated in the contract, or, if that period was extended, the date the extension ended — not simply whatever date management later decides to announce. The company should be able to show the facts behind it: which project the worker was assigned to, which phase, whether that phase was really completed, and when his work actually ended.

There is also a reporting step that companies often forget. Under DOLE’s construction guidelines, the termination of a project employee should be reported to the DOLE Regional Office within 30 days after separation, using the prescribed form. In a 2021 decision (Toyo Seat Philippines Corporation v. Velasco), the Supreme Court treated the submission of these reports as an indicator of project employment. It is not the deciding test by itself. The main question remains whether the worker was really hired for a specific project whose scope and duration were made known at the start. Still, missing reports weaken the company’s position.

Also watch the other direction. Keeping a worker on long after the project or phase has ended can lead a court to treat him as a regular employee.

What to do: when a project or phase ends, prepare a short Project Completion and Separation Record stating the project, the phase, the worker’s assignment, the completion date and his last day of work. Then file the DOLE termination report on time. The goal is not to create paperwork after a dispute. It is to write down the facts while they are fresh.

Quick test: did we identify the project and the worker’s assignment when he was hired, and did we properly report his termination when that project or phase ended?

4. “They are Not Our Employees. They are the Subcontractor’s Workers.”

Construction projects usually run in layers: project owner, general contractor, subcontractor, workers. So management often thinks, “Those workers belong to the subcontractor. Not our problem.”

Labor law is not quite that simple. Subcontracting parts of a project is a recognized practice in construction, and in a legitimate arrangement the workers are generally the subcontractor’s employees. In the construction industry, these arrangements are governed by DOLE’s construction guidelines and PCAB contractor licensing. (For construction contracting arrangements within the licensing coverage of the Philippine Contractors Accreditation Board, or PCAB, DOLE’s construction-specific rules apply rather than the general contracting framework under Department Order No. 174, Series of 2017, as DOLE clarified in Department Circular No. 01, Series of 2017.) But the Labor Code’s rules on contracting still apply, and two of them matter a great deal:

• Shared responsibility. A legitimate subcontractor does not completely shield the company that hired it. In appropriate circumstances, the principal may be held solidarily liable with the subcontractor for the workers’ unpaid wages, without prejudice to other liabilities that may arise under applicable labor and social legislation. A contract can decide who ultimately bears the cost between the two companies, but it cannot take away the workers’ right to collect.
• “Labor-only contracting” is prohibited. This exists where either of two things is true: the subcontractor lacks substantial capital or investment in tools, equipment or machinery and its workers do the kind of work directly related to the company’s main business; or, separately, the subcontractor simply has no real control over how its workers do the job, regardless of its capital. Either one, on its own, is enough for the law to treat the company as the workers’ actual employer.

What to do: before awarding a subcontract, check whether the subcontractor:

• holds a valid PCAB license;
• has its own equipment, tools and capital;
• has its own supervisors who direct its workers, and decides the manner and method of the work itself;
• pays wages on time and remits SSS, PhilHealth and Pag-IBIG contributions; and
• follows safety rules on site.

Then build these checks into the subcontract itself, such as the right to ask for payroll and contribution records. A PCAB license is a good start, but it is not conclusive proof of a legitimate arrangement — the actual arrangement on site is what counts.

5. “He is Field Personnel Because He Works at the Construction Site.”

It sounds logical, but it can be costly. “Field personnel” is a legal category with real consequences: under the Labor Code, it covers non-agricultural employees who regularly work away from the employer’s principal place of business and whose actual hours of work in the field cannot be determined with reasonable certainty. Employees who truly fall in this category are not covered by the rules on overtime, holiday pay and night shift differential.

Working at a construction site does not automatically place someone in this category. The Supreme Court has explained, in a case involving a bus driver (Auto Bus Transport Systems v. Bautista, 2005), that being away from the main office is not enough by itself — what matters is whether the employer can determine his actual hours with reasonable certainty, and whether his time and performance are genuinely supervised. A carpenter working fixed hours under a foreman’s watch is very different from a roving inspector whose hours no one can check. A site engineer, a driver and a project coordinator may each fall on a different side of the line, depending on how closely their time is actually monitored.

The answer comes from the worker’s actual arrangement, not from the title on his ID or a blanket label in the contract. Companies that tag everyone on site as “field personnel” and skip overtime pay risk paying back wages for up to three years.

Quick test: can the company determine with reasonable certainty when this worker actually works, and does it genuinely supervise his time and performance?

6. “Overtime Is Just Part of Construction.”

Deadlines are real. Concrete must be poured, inspections must be completed, and a delayed project needs more hours. But a deadline does not erase the overtime rules. For covered employees, work beyond eight hours on an ordinary day earns an additional pay of at least 25% of the hourly rate, and work on rest days and holidays carries higher premiums. If the company knows about the extra work or allows it, it should be paid.

The bigger risk is often the records. Imagine this:

• Payroll: 8 hours
• Gate log: in at 6:00 a.m., out at 8:00 p.m.
• Supervisor’s report: night work completed
• Worker: “I worked 12 hours.”

Now the worker does not have to rely on his word alone. The company’s own records raise the question.

What to do: regularly compare attendance, overtime forms, payroll and project reports. If they tell different stories, find out why before someone else does.

7. “He is Daily-Paid, So There is Nothing Else to Worry About.”

“Daily-paid” describes how a worker is paid. It does not decide what he is entitled to. Depending on his status and the work he actually does, the company may need to account for:

• the regional minimum wage;
• overtime pay, holiday pay and rest-day premiums;
• night shift differential;
• service incentive leave (for those who qualify);
• 13th month pay; and
• SSS, PhilHealth and Pag-IBIG contributions.

A common mix-up: 13th month pay is not reserved for monthly-paid staff. A daily-paid rank-and-file worker who has rendered at least one month of service within the calendar year is generally entitled to it too. Construction payroll can be complicated, with workers paid daily, weekly or per task. That is exactly why the better question is not “How much do we pay him per day?” but “What is this worker’s status, and what follows from it?”

8. A Safety Program That Exists Only on Paper

Construction is inherently hazardous: falls, excavations, electrical work, scaffolding, heavy equipment, falling objects. That is why safety is central to labor compliance in the industry.

Every construction project is required to have a Construction Safety and Health Program (CSHP). This traces back to DOLE’s Department Order No. 13, Series of 1998, and sits within the broader framework of the Occupational Safety and Health Standards Law (Republic Act No. 11058) and its implementing rules, which DOLE has continued to update, most recently through Department Order No. 252, Series of 2025. DOLE can order work stopped where there is imminent danger. The filing process has also changed: under DOLE Labor Advisory No. 03, Series of 2026, the CSHP is now submitted through the DOLE Online Compliance Portal, and the approved program must be posted at the worksite and made accessible to workers. Government projects can follow a different route (DPWH projects typically go through DPWH), so check the current DOLE advisory for the process that applies to your project.

But a CSHP is not merely a document to secure before construction begins. It is supposed to be the project’s operating safety program, governing what actually happens on site. If the program requires protective gear, yet workers are routinely allowed to skip it because the project is behind schedule, the company has a much bigger problem than incomplete paperwork.

Quick test: if DOLE inspected our site tomorrow, would what they see match what our safety program says?

9. Letting the Foreman Become the Company’s “Labor Arbiter.”

Site decisions have to be quick. A foreman sees two workers fighting. A project manager runs out of patience with a worker who keeps ignoring instructions. Then someone says, “Do not come back tomorrow.”

To the worker, that sounds like a dismissal. And in a dismissal case, the company carries the burden of proving that there was a valid reason and that the proper process was followed. That process generally means giving the employee a written notice of the charge, a real chance to explain, and a written decision.

The answer is not to stop supervisors from managing. It is to define their role clearly:

1. Supervisor: reports the incident and records the initial facts.
2. Project Manager: documents what happened and recommends action.
3. HR or Management: investigates and follows the required procedure.
4. Authorized Officer: makes the final decision.

Supervisors should not tolerate misconduct. If a worker’s continued presence poses a serious and imminent threat to life or property, sending him off the site right away may be necessary — but legally, that act is a preventive suspension, not a dismissal. DOLE’s construction guidelines give this its own rules: the suspension cannot last longer than 15 days (shorter than the 30 days allowed outside construction), and within that window the company must set a date, time and place for a fact-finding hearing where the worker can be heard, with counsel or a representative if he wants one. Only after that process can the company decide to reinstate him, extend the suspension with pay, or terminate his employment. The foreman’s job is simply to document what happened on the spot and hand it to HR immediately, so that 15-day clock is used properly. A site removal should never be treated as the end of the matter, and never dressed up afterward as the dismissal itself.

10. The Company’s Own Records Become the Worker’s Evidence.

This may be the most important lesson of all. Construction companies produce a lot of records: contracts, project assignments, time records, gate logs, biometrics, GPS data, payroll, overtime forms, accomplishment reports, safety and incident reports, subcontractor records, and even emails and Viber or other work chats.

When a labor case comes, these do not disappear. They become evidence. And when a worker claims he was not paid what he earned, it is generally the company that must prove it paid.

Imagine a worker who says he worked 12 hours a day, and a company that says it was only eight. Then the worker presents gate records, supervisor messages and project reports showing he stayed on site much longer. Now the company has to explain its own documents.

Good labor compliance is not just about having documents. It is about having consistent documents that match what really happened. Because many labor money claims prescribe within three years, payroll and time records should generally be kept for at least that long — though some records, particularly those tied to workplace safety, may carry longer retention periods under other rules.

A Simple Six-Step Routine

The answer is not another 50-page HR manual that nobody reads. Start with a simple system built around how your company actually works:

1. Keep an employee status file. For every worker, record whether he is regular, probationary, project-based or covered by another lawful arrangement, together with the supporting documents.
2. Keep a project employment matrix. Track each worker by project, phase, position, start date, expected end and actual end date.
3. Check subcontractors before awarding, not after a complaint. Review the PCAB license, equipment, workforce, payroll and contribution practices, and safety compliance. Do not choose on price alone.
4. Make payroll and site records talk to each other. Compare attendance, overtime, payroll and project reports regularly.
5. Audit your safety program against real site practice. Ask not only “Do we have a CSHP?” but “Are we actually following it?”
6. Train your supervisors. A foreman does not need to be a lawyer, but he should know that “Do not come back tomorrow” can have legal consequences, how to report misconduct, when to call HR, and that safety rules do not bend because the project is behind schedule. In many labor cases, the first person to create the evidence is not HR. It is the site supervisor.

The Bottom Line

Construction companies have a real business need for flexibility. Projects start and finish, manpower needs change, and specialized work goes to specialized contractors. The law recognizes that. But the flexibility comes with a responsibility: the company must be able to show that the arrangement it says exists is the arrangement that actually exists.

Most construction labor disputes are not caused by one dramatic violation. They come from small gaps that pile up: a generic contract, a missing project assignment, a subcontractor that supplies nothing but manpower, an overtime record that does not match the gate log, a verbal dismissal, a safety program nobody follows, a project that “ended” with no completion record. Each looks like a minor administrative issue. Together, they can become a very expensive dispute.

A building does not succeed because someone remembers to lay the foundation after the walls are up. Labor compliance works the same way. Before a worker steps onto the site, the company should already know who he is, what his status is, what project he is assigned to, who supervises him, how his time will be recorded, what he will be paid, what safety rules apply, and what happens when his assignment ends.

The best labor defense is rarely built after the complaint is filed. It is built into the contract, the project records, the payroll, the timekeeping, the subcontract and the safety program, long before anyone walks into the NLRC.

Selected Legal Authorities

• Labor Code of the Philippines: Art. 82 (field personnel), Art. 87 (overtime), Art. 94 (holiday pay), Art. 95 (service incentive leave), Arts. 106–109 (contracting and subcontracting, including the liability of principals in appropriate circumstances), Art. 295 (regular and project employment), Art. 297 (just causes for termination) and Art. 306 (money claims), as renumbered
• DOLE Department Order No. 19, Series of 1993 (Employment of Workers in the Construction Industry)
• DOLE Department Circular No. 01, Series of 2017 (Scope of Department Order No. 174)
• DOLE Department Order No. 13, Series of 1998 (Occupational Safety and Health in the Construction Industry), as supplemented by later OSH issuances
• Republic Act No. 11058 (Occupational Safety and Health Standards Law), its implementing rules as revised by DOLE Department Order No. 252, Series of 2025, and DOLE Labor Advisory No. 03, Series of 2026
• ALU-TUCP v. NLRC, G.R. No. 109902 (August 2, 1994); Tomas Lao Construction v. NLRC, G.R. No. 116781 (September 5, 1997); Auto Bus Transport Systems, Inc. v. Bautista, G.R. No. 156367 (May 16, 2005); Dacles v. Millennium Erectors Corporation, G.R. No. 209822 (July 8, 2015); Toyo Seat Philippines Corporation v. Velasco, G.R. No. 240774 (March 3, 2021). This list is illustrative and not an exhaustive statement of every authority bearing on the topics discussed.