On-Call or Project-Based Work After Training: Employment Classification and Legal Risks

1) Why this topic matters

Many organizations “train” workers first, then shift them into on-call, per-project, per-output, or consultancy arrangements to stay flexible and reduce costs. In the Philippines, that transition can create serious exposure because labels do not control—what matters is the real relationship. If the post-training setup functions like employment, the worker can be deemed a regular employee with security of tenure and full statutory benefits, regardless of what the contract calls them.


2) Core legal framework (high-level)

Philippine labor classification is shaped mainly by:

  • Labor Code provisions on employment status and security of tenure (commonly discussed under the “regular vs non-regular employment” rules).
  • Rules on probationary employment, project employment, fixed-term employment, casual/seasonal employment.
  • DOLE rules on contracting/subcontracting (and the continuing scrutiny of labor-only contracting).
  • Jurisprudence (Supreme Court decisions) applying tests like the four-fold test and control test.

This article focuses on the post-training shift into on-call/project-based work and the risks that follow.


3) The non-negotiable principle: substance over form

In disputes, adjudicators look past contract titles (“freelancer,” “project-based,” “on-call,” “talent,” “consultant”). A worker may still be found an employee if the factual indicators point to employment.

The “four-fold test” (widely used)

Courts commonly examine:

  1. Selection and engagement (who hired whom and how),
  2. Payment of wages (how compensation is paid),
  3. Power of dismissal (who can terminate and on what grounds),
  4. Power of control (most important): who controls not just the result but the means and methods of doing the work.

If the company controls the manner, schedule, standards, tools, and workflow the worker must follow, the relationship tends to look like employment.

“Economic reality” signals (often persuasive)

Even when “control” is debated, these facts increase risk:

  • Worker is economically dependent on one client,
  • Work is integrated into the business,
  • Worker cannot meaningfully negotiate terms,
  • Worker is subject to internal policies like an employee.

4) Understanding common post-training arrangements

A) Probationary employment (including “training” that is really probation)

If the worker is being prepared to do the job and evaluated for retention, this often functions like probationary employment (typically up to 6 months in many roles). Key compliance points:

  • Reasonable standards for regularization must be made known at the time of engagement.
  • Termination during probation must be based on just cause or failure to meet standards, with due process.

Risk pattern: Calling someone a “trainee” while assigning real productive work under supervision and then “ending training” to avoid regularization can be challenged as a circumvention of security of tenure.


B) Apprenticeship / learnership vs. “training” in ordinary work

Philippine law recognizes formal training arrangements (e.g., apprenticeship/learnership) with strict requirements (program registration/approval, allowable occupations, duration limits, wage rules, etc.). Many “training” setups in offices and service roles do not qualify and may be treated as normal employment.

Risk pattern: If the training is not under a compliant program and the worker performs productive work for the business under company control, the worker may be treated as an employee entitled to wages and benefits.


C) Project employment (legitimate—but commonly misused)

Project employment is valid when employment is tied to a specific project or undertaking with a defined scope and determinable completion (or phase). Typical compliance expectations:

  • The worker is engaged for a specific project, not the business generally.
  • The project and duration/phase are clearly communicated at hiring.
  • When the project ends, the engagement ends because the project ends—not because management chooses to stop calling the worker.

Where it goes wrong post-training:

  • Worker does the company’s usual and necessary work continuously.
  • “Projects” are just internal labels for ongoing operational work.
  • Repeated re-hiring for the same role with no real project boundaries.

Legal exposure: The worker may be deemed regular if the work is necessary/desirable to the business and the engagement becomes continuous or repeated in a way that indicates a continuing need for the role.


D) Fixed-term employment (possible, but tightly scrutinized)

Fixed-term contracts can be valid if the term is knowingly and voluntarily agreed and not used to defeat security of tenure. If the fixed term is repeatedly renewed for ongoing necessary work, it may be attacked as a workaround.

Risk pattern after training: “Training contract” → then a chain of short fixed-term renewals for a role that is plainly ongoing.


E) Casual, seasonal, and intermittent/on-call work

  • Seasonal employment fits truly seasonal industries/activities.
  • Casual employment covers work not usually necessary or desirable to the employer’s usual business, but it can convert to regular if it reaches thresholds and the work becomes necessary/desirable and continuous.
  • On-call/intermittent work can exist, but it is risky when the worker is effectively on standby under company control, or the work is a continuing business need.

Key issue: “On-call” is not a magic category. If the worker is effectively part of the workforce and regularly summoned to do core business tasks, classification risk increases.


F) Independent contractor / freelancer / consultant (valid only if genuinely independent)

A legitimate independent contractor usually:

  • Controls how to do the work,
  • Can subcontract/hire assistants (subject to client constraints),
  • Uses own tools/resources (often),
  • Bills by invoice, pays own taxes as self-employed,
  • Can serve multiple clients,
  • Is judged mainly by deliverables, not attendance.

High-risk red flags (common post-training):

  • Mandatory time-in/time-out, fixed schedules, required attendance in meetings like staff.
  • Required compliance with employee handbook as if an employee.
  • Performance management identical to employees (disciplinary memos, HR sanctions).
  • Company provides tools, email, system access, and supervises day-to-day steps.
  • Exclusivity (no other clients) without true independence.

G) Contracting/subcontracting and manpower agencies (additional risk layer)

If workers are supplied by a contractor, the arrangement must avoid labor-only contracting and comply with DOLE rules (e.g., sufficient capitalization, control over its workers, substantial work/service, registered contractor, etc.). If found labor-only, the principal may be treated as the employer.

Post-training risk pattern: A company “trains” people itself, then “places” them under a contractor arrangement to continue the same work under the same supervisors. This can look like an attempt to evade employer obligations.


5) The special problem of “on-call after training”

What “on-call” often looks like in practice

After training, the company says:

  • “We’ll call you when needed.”
  • “You’ll be paid per task/per day/per output.”
  • “No employer-employee relationship.” But the worker:
  • Must remain available during certain hours,
  • Must respond quickly or face removal,
  • Uses company systems and follows step-by-step procedures,
  • Is supervised by company team leads,
  • Performs core operational work.

Legal risk: “waiting time” and control

If the worker is required to remain available under constraints and is effectively controlled, that “standby” can be treated as compensable time in some contexts, and—more importantly—it strengthens the argument that the worker is an employee, not an independent contractor.


6) Regularization risk: the “necessary and desirable” factor

A major driver of Philippine employment disputes is whether the work is necessary or desirable to the employer’s usual business. Post-training, if the worker is doing:

  • customer support in a customer support business,
  • sales for a sales-driven company,
  • production work for a production operation,
  • content/marketing as part of marketing operations,
  • admin roles that are integral and continuous, then “project-based” or “on-call” labels become harder to defend if the company shows an ongoing need for the role.

7) What employers can be liable for if misclassification is found

If the worker is declared an employee (often regular), potential exposure includes:

A) Money claims and benefits

  • Wage differentials (including minimum wage compliance where applicable),
  • Holiday pay, service incentive leave, 13th month pay (as applicable),
  • Overtime pay, night shift differential (if hours qualify),
  • Rest day premium (if applicable),
  • SSS, PhilHealth, Pag-IBIG contributions (and potential penalties/assessments),
  • Other company policy benefits if proven to be enjoyed by similarly situated employees.

B) Illegal dismissal exposure

If the relationship is employment and the worker is cut off because they were “no longer called”:

  • It may be treated as dismissal.
  • If there is no just/authorized cause and due process, the company may face reinstatement/backwages (or separation pay in lieu, depending on circumstances) and damages/attorney’s fees in some cases.

C) DOLE enforcement and administrative risk

  • Compliance inspections can lead to compliance orders and directives to rectify labor standards violations.

D) Reputational and operational risk

  • Workforce instability, labor disputes, and documentation scrutiny in future audits and disputes.

8) Common post-training fact patterns—and how they’re usually viewed

Pattern 1: “Training allowance” then on-call daily operations

High risk. If training was effectively work, and post-training is the same job under supervision, it resembles continuous employment.

Pattern 2: “Project-based” but role is constant, projects are just internal buckets

High risk. “Project” must be real and bounded; ongoing operational work undermines the classification.

Pattern 3: Paid per output, but strict schedule + daily supervision

High risk. Payment style doesn’t negate employment if control is present.

Pattern 4: Freelancer with deliverables, flexible method, multiple clients

Lower risk (but not zero). Documentation and actual practice must match independence.

Pattern 5: Agency/contractor arrangement after company training

High to very high risk if the company continues to supervise and the contractor lacks real control/substantial business independence.


9) Practical compliance guidance for businesses (Philippine context)

Step 1: Decide what you truly need

  • If you need ongoing core work with supervision and schedules → you likely need employment (regular or probationary).
  • If you need a discrete deliverable with autonomy → consider a genuine independent contractor.
  • If you need work tied to a true project with a defined endpoint → project employment can be appropriate.

Step 2: Align documentation with reality (and fix reality first)

Contracts help, but day-to-day practice matters more.

For project employment:

  • Identify the project name, scope, phases, estimated duration, and completion criteria.
  • Make clear the engagement is for that project/phase.
  • Avoid using project employees as general staff fillers for ongoing operations.

For independent contractor:

  • Define deliverables and acceptance criteria, not schedules.
  • Avoid timekeeping, HR discipline processes, and “employee-like” supervision.
  • Allow reasonable autonomy; avoid exclusivity unless truly justified and consistent with contractor status.
  • Use invoicing and appropriate tax handling consistent with contractor status.

For on-call arrangements (if used at all):

  • Be cautious: if you impose standby requirements and control, you may be creating employment.
  • If you need standby coverage, consider a compliant employment model (e.g., part-time employment where applicable, properly documented schedules, proper wage and benefits treatment).

Step 3: Avoid “training” as a workaround

If the person is already doing productive work under company control, treat them consistently with lawful employment or a properly structured training program that truly qualifies.

Step 4: Contracting/subcontracting: treat it as high-risk territory

  • Ensure the contractor is legitimate and exercises control over its workers.
  • Avoid supervising contractor personnel as if they are your employees.
  • Ensure compliance with DOLE contracting rules and documentation.

10) Practical guidance for workers

If you are labeled “on-call” or “project-based” after training, the following facts tend to matter in assessing your rights:

  • Do you follow a fixed schedule set by the company?
  • Are you supervised on how to do the work (not just what output is needed)?
  • Are you integrated into teams, using company tools/systems, doing core business work?
  • Can you take other clients or jobs without penalty?
  • Were you effectively “terminated” by being stopped from being called, with no due process?

Keep records: messages assigning shifts/tasks, policies you were required to follow, proof of supervision, payslips/remittances, and duration/continuity of service.


11) Risk checklist: “Post-training on-call/project-based” classification

The more “Yes” answers, the higher the risk that the arrangement is employment:

  • □ Company dictates work hours or requires availability windows
  • □ Company controls methods/processes step-by-step
  • □ Work is part of the company’s usual business
  • □ Worker is embedded in teams and reporting lines
  • □ Worker cannot refuse tasks without penalty
  • □ Worker uses company tools, email, systems as standard
  • □ Worker is subject to HR discipline rules
  • □ Engagement continues or repeats over a long period
  • □ “Projects” are not clearly bounded with real endpoints
  • □ Worker is economically dependent on the company

12) Key takeaways

  • On-call after training is legally sensitive in the Philippines because training often demonstrates control, and on-call setups often preserve it.
  • Project-based classification requires a real, defined project—not just work labeling.
  • Independent contractor status requires genuine independence in means and methods, not just a contract clause.
  • Misclassification can trigger regularization, monetary claims, and illegal dismissal exposure, plus social protection contribution issues.

This article is for general legal information in the Philippine context and is not a substitute for advice on specific facts. If you share a concrete scenario (industry, tasks, control/schedule, contract terms, duration), the analysis can be tailored into a practical risk assessment format.

Disclaimer: This content is not legal advice and may involve AI assistance. Information may be inaccurate.