Staffing a Philippine Security Services Company: Licensing First, Twelve-Hour Shifts, and Who the Employer Really Is

The Personal Licence Is a Condition of Employment, Not Onboarding Paperwork — and That Rewrites Hiring, Rostering and Discipline

In private security, individual deployment credentials are a precondition of employment: a person without them cannot be posted. That reads like a recruitment filter, but it actually rewrites four separate things — how you structure an offer, how probation works, how the roster system behaves, and how discipline has to run.

Boundaries first, so this does not duplicate two other pieces. The regulatory framework for the industry and for firearms, which regulator owns what, which documents an occupier should verify and what a guard may not do are covered in gun laws and security guards in the Philippines (written for occupiers engaging guards), which is written from the buyer's side and takes the opposite view to this one. What two-tier licensing means on the supply side, why deployable headcount always trails headcount on the books, and how training and insurance enter the cost base are in the supply side of a security services company. This guide covers only the employment end: hiring, rostering, employer identity on deployment, what happens when there is no post, and exit.

Structure the offer as a conditional engagement. Because deployment credentials are a precondition, the engagement documents must state three things: that obtaining and continuously maintaining the required credentials is a condition of continued employment, that no deployment occurs before they are held, and what the person's status and remuneration are during the waiting period. Are they in training, or not yet engaged? The obligations differ entirely, and leaving it vague turns into an unreconcilable account a few months later. For vetting see what an NBI clearance is and conducting lawful pre-employment checks; for the general hiring and onboarding sequence see the full hiring process in the Philippines.

The hardest question is what happens when credentials lapse mid-employment, and three wrong answers recur. The first is rostering as usual, which is the most dangerous, because the post no longer stands and no amount of client payment restores its compliance. The second is treating it as absence without leave, which mischaracterises the situation entirely — the person did not refuse to work, you are unable to deploy them. The third is dismissing on the spot, with no statutory process, which is almost certain to be treated as unlawful dismissal. The workable answer is a clause written in advance into the contract and handbook: deployment stops, a remedy period and the arrangements during it are stated, and if the credential is not restored the matter proceeds through statutory process. See notice and process in a dismissal and writing a Philippine employee handbook.

There is one management tool, and it is the highest-yield single control in this sector: an expiry calendar wired into the rostering system. Record every deployed person's credential expiry, training and refresher cycle, medical and any other recurring requirement, prompt well ahead, and have the roster refuse to assign anyone whose credential has lapsed. It sounds like an IT problem and it is a compliance problem: what goes wrong is never that nobody knew the requirement existed, it is that nobody owned the expiry date while the roster kept posting that person. For retention periods see payroll and time record retention.

Twelve-Hour Shifts and Hours Disputes: Common Is Not the Same as Lawful

Twelve-hour shifts are standard practice in this sector, and standard practice is not a defence — whether the arrangement holds depends on how hours beyond statutory normal hours are paid, how rest is actually provided, and whether three sets of records reconcile. Structure only below; no figures.

Start with how the premiums stack. Covering a day with twelve-hour shifts means every shift contains hours beyond statutory normal hours, payable under overtime rules; shifts crossing into night hours carry the night differential on top; shifts falling on a holiday or a rest day carry their own basis again. These layers stack rather than substituting for one another, and treating them as alternatives is the commonest computation error in this trade. For the mechanics see how overtime pay is computed and regular versus special holidays; for the limits on the rostering arrangement itself see lawful shift scheduling in the Philippines.

Hours disputes in this sector come from three places. First, the post is manned but the relief has not arrived: the outgoing guard cannot leave, and that time regularly disappears from the attendance record — which is also the easiest shortfall to prove, because the client site usually keeps its own entry log. Second, meals and rest: a guard on a single-officer post cannot in practice leave, so treating that period as uniformly unpaid rest is difficult to sustain in a dispute. Third, briefing and handover: roll call, equipment issue and handover notes occur reliably and take a predictable length of time, and scheduling them outside the shift generates a daily shortfall.

Then there is the structural problem: contractual hours drifting away from actual rostering. The contract states standard hours while the roster has run twelve-hour shifts for years. That gap stays invisible until one person resigns and files a claim, at which point it surfaces all at once and usually pulls in everyone on the same post — claims in this sector are rarely single-person matters. The fix is aligning contract, rostering policy and attendance records to one account of reality; where they disagree, the practice should change before the record does. For what inspections examine see what a labour inspection examines.

The unwelcome part: compliance cost here scales linearly with headcount, so buying volume by cutting rates does not work. Volume raises credentials to maintain, training to repeat, records to keep and overtime to fund in equal measure, and the rate you gave away does not come back. Real scale economies appear in deployment efficiency and management systems, not in compliance. The cost base is in Philippine labour cost structure and what one employee actually costs. For sectors with the same continuous-coverage problem, compare the companion pieces staffing an elderly care facility and staffing a pet services business. Take advice on your own facts; this is not legal advice.

Who Is the Employer at a Client Site: This Decides Who Pays, Who Pays First, and Whether It Can Be Recovered

When guards are deployed to a client site you remain the employer — wages, statutory contributions, working time and safety obligations do not transfer because the work happens on someone else's premises — and the client does not thereby become free of obligations either. This is the question to settle before signing, not after an incident.

The service contract must separate three things: who directs the work, who carries employer obligations, and who answers first to a third party with what right of recovery. The first is where it usually goes wrong: client-site managers directing your guards personally, sometimes arranging overtime, reassignment or discipline themselves. Once direction has in fact moved, the characterisation of the whole arrangement is open to review, and that is precisely the line between lawful contracting and labour-only contracting; see lawful contracting versus labour-only contracting and choosing an HR outsourcing model. Write the chain of command into the contract: the client raises requirements, your site supervisor assigns work, and the client does not instruct individuals directly.

One risk on the wage line is specific to this sector: when a client is late paying service fees, guards must still be paid on time. A client's non-payment cannot be passed through to employees in any circumstances, and wage underpayment is the category with the least room for explanation in an inspection. So design cash flow on that premise — treat wages and statutory contributions as fixed outgoings rather than something that follows collections. Working out the relationship between payment terms and payroll float before taking on a large client is more useful than explaining it afterwards.

Allocate liability in advance, because site defects should not fall wholly on the contractor. Lighting, entrance design, how mixed the site population is, and the existing security situation are conditions of the premises and outside your control. So a pre-engagement site risk assessment belongs in the contract, together with what falls to the client and what cooperation the client must provide. That assessment is covered from the bid-process angle in the supply side of a security services company; what belongs here is the next step — converting the assessment into post orders and job descriptions so the people on site know what they may and may not do. What a guard cannot do, and what an occupier cannot ask for, is in gun laws and security guards in the Philippines (written for occupiers engaging guards).

Employee safety is the layer most often overlooked: deployed staff are covered by your safety obligations while the site is not under your control. The workable answer is writing minimum conditions into the service contract — rest and toilet facilities, drinking water, lighting, means of communication, emergency contact and evacuation arrangements — and declining to post where they are absent. That is not a negotiating posture; it is a precondition of your own obligation. For the injury route see handling a work injury claim, and for what commercial cover closes see employer liability insurance, checking in particular whether night posts, lone posts and higher-risk sites are excluded, because standard wordings frequently exclude them.

The Contract Ends, the Post Disappears, the Person Stays on the Books: Off-Detail Is This Sector's Own Problem

When a client does not renew, the post vanishes but the employment relationship does not — the person goes off-detail, into what the trade calls floating status. The critical point is that floating status is not open-ended: leaving someone there beyond a reasonable period without redeployment can be treated as dismissal in substance. The applicable period, the test and the consequences follow current rules and the facts of the case, so no number appears here.

Why this is acute only in this sector: in other industries you create your own posts, whereas here the client buys them. A contract ends, a client switches supplier, a client relocates or downsizes, and the post is gone the same day — while the person remains your employee. The sector therefore carries a structural buffer pool, and everyone in that pool sits in a state of employment without a post. That state is not a legal blank: it has a clock and it has consequences.

Three things belong in the system. First, write floating status into the contract and handbook: what triggers it, the employee's reporting duty and contact arrangements during it, the priority rule for redeployment, and what the arrangements are meanwhile. Second, set an internal deadline and manage it actively — you drive it from a calendar rather than waiting for the employee to ask. Third, leave a trail: every offer of redeployment, every refusal or non-response, every attempted contact. The commonest reason employers lose these cases is not a defective policy but an absent record — the company says posts were always available and can produce nothing to show it.

Two failure modes to avoid. One is telling someone to go home and wait for a call, with no time limit and no record; that vague wait is the single largest source of subsequent disputes. The other is using floating status to push someone into resigning, which is easy to see through and tends to contaminate the claims of everyone else in the same cohort. Where a batch of client cancellations forces a collective arrangement, separate collective procedures apply; see handling collective workforce reductions and the worker checklist for closures and sector contraction. For final settlement components see final pay and separation pay, and for traps once a dispute becomes formal see common traps in labour arbitration.

The real fix is commercial rather than contractual: the more concentrated your client base, the higher your floating exposure. Staggering contract end dates, keeping the client count diversified, and making sales confirm roster capacity before committing do far more to reduce this risk than any clause. Conversely, relying on a contractual statement that floating periods are unpaid is the classic paper comfort of this trade. For an overall self-audit see the employment risk checklist. Take advice on your own facts; this is not legal advice.

Armed Posts: Additional Eligibility and Custody Accountability — Three Systems the Employer Must Build

Armed posts add two employment layers: a higher eligibility standard that must be continuously maintained, and custody accountability for firearms and ammunition that lands on named individuals. This section covers compliance duties and the systems an employer must build. It does not address acquisition routes, operational detail, or any workaround.

Boundaries first. The legal framework for firearms control, which regulator owns it, and the rules on possession and use at company and individual level are regulatory matters already set out in gun laws and security guards in the Philippines (written for occupiers engaging guards) and the supply side of a security services company. Neither is repeated here and no procedure is elaborated. Three things belong to the employment side: who may be assigned to such a post, how custody accountability attaches to a person, and how it is closed out when people move.

First, assignment eligibility. The standard for these posts sits above ordinary posts and must be maintained continuously rather than obtained once. Maintain a written list of the preconditions for assignment, owned by the compliance side and refreshed on a fixed cycle, and have the sales side check your own eligibility coverage before committing to a scope of service. Promising a service your eligibility does not cover produces a signed contract you cannot perform, which is worse than losing the bid — you also have to explain the failure to the client.

Second, custody accountability, where the system must answer five questions: who hands over to whom at each change, on which record it is signed, how the count is verified at the end of a shift, the reporting deadline and recipient when anything is irregular (missing, damaged, not stored as required), and who performs periodic reconciliation. All of these are continuing duties rather than one-off formalities at start-up. The employment-side addition is to write them into job descriptions and training records, so accountability stays legible after reassignment, leave and turnover — recorded in the system rather than held in a supervisor's memory is the only reliable version.

Third, closing out when people move. Reassignment, leave, entering floating status and resignation each need a defined return-and-verify procedure, completed the same day and recorded the same day. The concentration point for problems is the day someone leaves: the person has gone while the equipment and formalities trail by several days. Writing same-day completion with two signatures into the procedure is enforceable without any sophisticated system.

Finally, continuity: training and refresher training for these posts are a recurring cost rather than a one-off investment at hire. Treating training as discretionary spending tends to be repaid, with interest, as lapsed eligibility, client complaints or incident liability. For how a training commitment might be drafted to hold, see training bonds and service commitments — though the more effective answer is usually not locking people in but reducing turnover itself: predictable rosters, equipment that works, and supervisors who do not mistreat people beat any clause; see reducing staff turnover. This section states compliance duties and system design only, and provides no means of circumventing regulation; take advice on your own facts, and this is not legal advice.

Exit: Equipment Recovery, Deregistering Deployment Status, and Final Pay — Do Not Use Withholding as Leverage

Exits in security carry two extra steps over other sectors — recovering and verifying equipment, and deregistering the person's deployable status — and neither may be driven by withholding final pay or documents. Use the wrong tool and an administrative matter escalates directly into an employment dispute.

Fix the leaving-day checklist as a single form: recover uniform, communication equipment, keys and access cards and every post-related item; close system accounts and revoke deployable status in the rostering system; verify handover records; settle wages and everything else owing; issue the certificate of employment. That certificate is a document the employee may require and must not be used as leverage; see issuing a certificate of employment, and for what final settlement comprises see final pay and separation pay. Have two people sign the form — the person returning items and the person receiving them.

The commonest error is refusing pay or documents until everything is returned. State it plainly: wage deductions are subject to legal limits, and charging the value of unreturned items against final pay requires a clear basis, written consent or statutory authority, not an ad hoc decision. See how to pay wages compliantly and common payroll compliance mistakes. The sturdier design sits at the hiring end: issue equipment against a signed register from day one, and state the return obligation and the consequences of non-return in the contract and handbook. A record made in advance is far more useful — and far more likely to be accepted — than a deduction made afterwards.

Walking off the job is more frequent in this sector, especially on deployed posts, and it has to be handled by procedure rather than by temper. Send written notice to the registered address, give a period to explain, record each attempt at contact, then proceed under statutory process; see handling an employee who goes AWOL. Deleting the person from the system and keeping no documents is the least explicable course in any later dispute, because you cannot even establish that notice was given.

Deregistering deployable status is the step unique to this trade. After departure, the credential status tied to that person must be updated and the rostering system must no longer carry a deployable flag against them; every accountability item in their name — equipment, keys, signing authority on records, system permissions — needs a named transferee. Make this part of the leaving-day form rather than something a particular manager remembers. Same day, recorded, is the only reliable version.

Comparisons and close. Three companion pieces sit alongside this one: staffing an elderly care facility for round-the-clock rosters and minimum night presence, staffing a pet services business for overnight cover and credential-linked assignment, and staffing beauty and aesthetic clinics for credentials defining service scope and for exit handover. When to bring in help: drafting conditional engagement and credential-lapse clauses, aligning contract and roster under a twelve-hour pattern, allocating direction and liability in deployment contracts, building the floating-status policy and its record templates, and consolidating credential expiry, refresher training, equipment registers and payroll filings into one register. Yixing is a private consultancy with no affiliation to any government body and does not promise outcomes; its accreditations are SEC registration CS202009551, Bureau of Immigration Accreditation No. CA-202624381-1 (valid to 2027-06-30), DOLE accreditation and PRA accreditation. Consolidated payroll, credential and filing administration across contracts can be handed to compliance administration services; permits and status for foreign management roles fall under visa and workforce services. Take advice on your own facts; this is not legal advice.