Industry
IBPAP
IBPAP is the IT and Business Process Association of the Philippines, the industry’s main trade association and the source of the sector’s official-ish headcount and revenue figures.
How it works
Use IBPAP numbers as order-of-magnitude context. They revise targets. They are not a regulator. DOLE and NPC do not report to them. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.
Example: IBPAP trims a 2028 target while leaving a nearer-year target almost intact: read both lines before you write a think piece about collapse.
How it differs
IT-BPM industry is the sector. PEZA is a government incentive regime.
Common errors
Citing an old $59B target as if it were current law.
In practice
Treat IBPAP as a week-one operating object. Use the sector fact as context for a slate, not as proof about one person. Headcount in the millions does not staff your Tuesday. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have ibpap yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.