Skip to content
Dakila

What onboarding asks of your office.

The module library defers a good deal to your own agency — your salary schedule, your rating weights, your leave categories, the form your office actually submits. Here it is in one place.

What loads from your records

These arrive from your own files. The employee master, opening leave balances and plantilla items are pre-flight checked as a whole batch before any row loads.

  • Your employee master, opening leave balances and plantilla items

    You map your spreadsheet onto our columns; we run the load. The batch is checked as a whole before any row is written.

    Described on:Architecture and data

  • Your salary schedule

    From the National Budget Circular that governs your agency. We ship no salary grade and step peso matrix, here or in the product — the schedule is re-issued annually and the authorised amount is your own instance data.

    Described on:Government payrollStep increment and NOSI

  • Your bonus amounts, and the months they fall in

    No bonus component ships pre-filled. The Mid-Year Bonus, Year-End Bonus and Cash Gift load with your salary structure.

    Described on:Government payroll

  • Your deduction component names

    The remittance register reads your deduction components by name, which is why the mapping to your own names is settled at onboarding. Your member numbers, employer numbers and branch codes come from your own fund enrolment, and the GSIS, PhilHealth and Pag-IBIG portal upload files are prepared with you rather than generated here.

    Described on:Contributions remittance register

What your office decides

None of these is a default we could pick for you. Two of them say so on the screen while they wait: without your agency category the publication register counts days and applies no statutory minimum, and until a night-shift rate is set the hours are measured and the amount reads as a dash.

  • Your agency category

    National agency, SUC or GOCC, or local government unit — the publication register cannot run the 10-or-15-day clock without it. PRAISE needs a finer answer than that one: central office, regional office, municipal, city or provincial, state university or college, or GOCC.

    Described on:Recruitment and onboardingPRAISE — awards, nominations and incentives

  • Your approval arrangement

    Simple, where the supervisor decides in one step, or routed through named stages with your names on the buttons. Offices with a division chief and an HRMO signing in sequence usually want routed. A document request is separate: HR fulfils it in one step, and any stages you want on one are configured at pilot rather than shipped.

    Described on:How work moves

  • Your competency model

    The Commission names the competencies; the behavioural indicators and level descriptions ship empty, because the behaviours your agency observes are yours to write. We ship no assessment instrument, no questionnaire and no scoring — an assessment records the approach used and the level it produced, and nothing computes that level for you.

    Described on:Competency profiles and the gap

  • Your SPMS variant, rating weights and calibration rules

    The weight column is on the form and ships empty — the circular fixes no weights. Any Division layer is yours as well: the Commission prescribes the office and individual forms and no Division form.

    Described on:Strategic Performance Management System

  • Your feedback categories

    Loaded with you before go-live, because until they exist the form has nothing to offer the person filling it in.

    Described on:Employee self-service and approvals

  • Your night-shift rate and coverage exclusions

    The law fixes a ceiling rather than a rate, and the product ships none. Exclusions ship empty, so until they are set the register includes every employee with night hours and says so on its own face. The separate floor that applies to public health workers is recorded rather than enforced — only the ceiling is.

    Described on:Night-shift differential

  • Your leave monetisation amounts

    Monetisation is labelled an estimate wherever it appears, because the approval routing and the authorised amounts are your agency's to set.

    Described on:Leave and the CSC leave card

  • Your minimum-wage designation and salary components

    Which of your employees are minimum-wage earners is your agency's designation. The product applies the treatment to the ones you designate and never decides who qualifies. Of that designation's exempt items only the night-shift differential is classified today; basic, holiday, overtime and hazard pay follow once your own salary components are mapped, and the de minimis treatment is confirmed with you at deployment.

    Described on:BIR annual filings

  • Your SALN transmittal

    The statement itself is filed with your agency and the Ombudsman, and how it reaches them is configured with you. The register derives the obligations it can, and does not apply the exemptions the law allows — an employee the law might excuse still appears as a filer, and the screen says so.

    Described on:SALN filing status

What gets checked against your own forms

Every generated document carries a stamp marking it unverified until it has been diffed, field by field, against the form your agency actually submits. The layouts are built to the published CSC and BIR revisions; matching the copy a particular agency files is a different thing, and it is what a pilot settles.

  • Each form, once, per agency

    The stamp comes off per agency and per form, after that diff has been run. It is on the published files today.

    Described on:The filings

  • The Service Record's form number

    Pinned against your agency's prescribed form. The certified positions-held and compensation history we do not generate at all — its fill-up procedure is not obtainable.

    Described on:201 file and document requests

What we scope against your equipment

One is quoted only after we have looked at what you own. The other is configuration on a shipped integration.

  • Your biometric terminals

    The endpoint that accepts a check-in exists and is authorised already. What does not exist is the connector to your terminals, and it depends entirely on which you own and what they can export.

    Described on:Biometric device integrationAttendance and daily time record

  • Sign-in against your agency directory

    Wired up at deployment as configuration. The engine ships the integration; there is no custom build.

    Described on:Architecture and data

What the law needs before real data loads

An HRIS holds the most sensitive record set an agency keeps, and RA 10173 is part of the engagement rather than a clause in it.

  • A Privacy Impact Assessment

    Before real employee data is loaded. A data sharing agreement where one is warranted, and contractual breach obligations on us. Because the system runs on your infrastructure, your agency remains the personal information controller throughout.

    Described on:Architecture and data

There is no timeline on this page

We publish no onboarding duration and no estimate of the work involved. How much of the list above already exists in writing differs by agency, and we have not measured it.

A walkthrough runs about half an hour on a fictional bureau. If you would rather spend it on the list above than on a tour, say so when you request one.