C1. Employee ID & VPM Access Password
To protect the login gate that guards every company and client record.
- Issuance. HR issues one Employee ID per employee before the first working day. The ID is personal, non-transferable, and never reissued to another person.
- Two credentials. Every login requires the Employee ID and the personal VPM access password created on first sign-in. Both are required; neither substitutes for the other.
- Prohibited sharing. Credentials are never shared with a teammate, a head, a family member, or a client, and are never stored in a note, chat, or spreadsheet.
- Device hygiene. The employee locks the screen when stepping away and does not leave an authenticated session open on a shared or public device.
- Failed attempts. Five (5) consecutive failed attempts lock the account. Unlocking is done by HR and every unlock request is logged.
- Loss or compromise. Reported immediately. Access is suspended, an audit of the account is performed, and a replacement is issued after the audit.
- Attribution. Activity performed under an Employee ID is presumed to be the holder's. Credential sharing that results in unauthorised access or financial loss is a zero-tolerance offense.
C2. Onboarding, Work Information & Contract Deadlines
To close the gap between joining and being fully documented.
- First day. The Work Information form is completed within the first shift, and the employment contract is signed within five (5) working days of the start date.
- Documents. Two valid government IDs, NBI or police clearance, TIN, bank account details, SSS, PhilHealth and Pag-IBIG numbers, diploma or transcript, and a 2x2 photograph, uploaded to the platform.
- Deadlines. Incomplete documents by day five (5) delay regularization. Beyond day ten (10), release of pay may be held until the documents are complete, and the hold is documented in writing to the employee.
- Contract authority. The contract version stored in VPM Hub is the governing version. Any amendment is issued as a new version requiring fresh acknowledgement; verbal promises do not amend the contract.
- False declarations. Falsified documents, credentials, or experience are grounds for dismissal for loss of trust, with any resulting overpayment recovered.
C3. 360-Degree Assessment Policy
To define how the assessment module is used and to keep it developmental, not punitive.
- Participation. All regular employees participate in each cycle as both reviewer and subject. Participation is a compliance requirement, not optional.
- Anonymity. Feedback is shown to the subject anonymously. Reviewer identities are visible only to HR and only to prevent duplicate or retaliatory submissions.
- Use of results. Results inform coaching, training plans, and team composition. They are never the sole basis for promotion, demotion, or discipline.
- Deadline. Each cycle runs for seven (7) days. Non-completion is recorded and escalated to the Team Leader.
- Access to one's own results. Shown to the employee only when HR enables the visibility setting for that cycle.
- Misuse. Retaliatory ratings, coordinated down-voting, or sharing assessment questions outside the platform is a conduct offense.
C4. Team of the Month Scoring Policy
To put the actual computation on record and make the award contestable on facts.
- Metrics. Four metrics carry twenty-five percent (25%) each: Perfect Shift Attendance and Punctuality; On-Time Dual EOD Submission; Operational Error and Rework score; Policy Compliance and zero disciplinary notices.
- Excluded metrics. A metric that does not apply to a team (for example a team not required to upload a backend report) is excluded and its weight is redistributed proportionally across the remaining metrics.
- Error logging. Heads log each error within twenty-four (24) hours with date, description, client, and impact. The team is notified and may contest an entry in writing within five (5) days; contested entries are reviewed by HR before scoring.
- Bonus points. Discretionary bonus points may be granted only by the CEO or COO, with a documented reason. Each entry is recorded separately and summed into the total.
- Publication. Scores become visible company-wide after the period closes. Unpublished scores remain admin-only.
- Ties. Ties are broken by attendance rate, then by EOD submission rate.
- Award. The winning team is announced at the start of the following month and its recognition is recorded permanently in the company's recognition history.
C5. Kudos Board Usage
To keep the recognition board positive, work-related, and safe.
- Purpose. The board is for genuine appreciation of a specific act of help, quality, or effort by a colleague.
- Allowed. Public or anonymous posts, with or without a tagged colleague and an optional photo of the work or occasion.
- Prohibited. Criticism, jokes at someone's expense, personal or romantic messages, client-identifying details, and information covered by confidentiality.
- Anonymity. Anonymous posts still record the author for moderation. HR and the CEO may identify the author when a post is reported.
- Reset. Posts are scoped to the current month and reset each month. The board is not a performance record and is not used in evaluation.
- Moderation. HR may remove a post that breaches this policy. Repeated misuse is a conduct offense.
C6. Internal Polls & Voting Integrity
To make company-wide votes credible and anonymous.
- Scope. Polls are created by administrators for recognition, culture, and engagement matters. Polls on compensation or disciplinary outcomes are not permitted.
- One person, one vote. Multiple votes, shared accounts, or voting on another's behalf invalidates the ballot and is a conduct offense.
- Anonymity. Individual choices are never disclosed to anyone, including administrators; only aggregates are reported.
- Campaigning. Soliciting votes, vote buying, or pressuring colleagues in group chats is prohibited.
- Results. Results are shown to voters only when the administrator enables it. Recognition polls that determine an award are binding once closed; other polls are advisory.
C7. Support Ticket & Helpdesk Service Levels
To give employees a defined response time and to keep the helpdesk from being used to bypass the chain of command.
- Categories. Leave and attendance, payroll and invoice, IT and access, client escalation, HR case, and equipment.
- First response. Within four (4) working hours for standard tickets and within the same hour for urgent matters (client down, payroll cut-off, access lock-out).
- Resolution targets. One (1) working day for routine requests, three (3) working days for complex requests, and five (5) working days for matters requiring investigation.
- Clarifications. The requester answers a clarification within twenty-four (24) hours, otherwise the ticket may be closed with the reason recorded.
- Not a substitute. Routine operational instructions still follow the chain of command. Duplicate or frivolous tickets are tracked and addressed with the employee.
- Escalation. A ticket that breaches its target is escalated automatically to the Team Leader and HR, and to the COO after a further forty-eight (48) hours.
C8. Acknowledgement Deadlines
To stop important notices from sitting unread.
- Deadlines. Announcements: forty-eight (48) hours. Memos and notices to explain: within the period stated in the document. Policy and handbook updates: seven (7) calendar days from publication.
- Meaning of acknowledgement. Acknowledgement confirms receipt and understanding. It is not agreement, except where the handbook expressly requires consent.
- Blocking prompts. Unacknowledged memos, contract changes, and policy updates appear as blocking prompts on the next login and cannot be dismissed without action.
- Non-compliance. Three (3) consecutive missed acknowledgement deadlines are recorded as a written notice and escalate under the Disciplinary Sanction Matrix if repeated.
- Informational items. Popups carrying purely informational content may be dismissed, and the dismissal state is kept per user.
C9. Internal Messaging & Screenshot Protection
To define what internal messages are for and how protection is respected.
- Records. VPM Hub messages are company records and are used for work communication. Personal, romantic, and grievance conversations do not belong here; grievances go through the HR Helpdesk.
- Protection. Screenshot and recording protection is enabled on internal conversations. Bypassing it through screen photography, external recorders, or a second device is prohibited.
- Sharing. Work information is shared only with people who need it for the task. Client details are never forwarded to anyone outside the engagement.
- Review. HR and the CEO may review conversations during an investigation, limited to the matter under review.
- Retention. Messages are retained for two (2) years. Deleting or altering messages to obstruct an investigation is a zero-tolerance offense.
C10. Error Logging, Quality Assurance & Rework Accountability
To make error records fair, contestable, and useful for coaching.
- Logging. Heads record an error within twenty-four (24) hours with the task, client, impact, and rework time.
- Notice and contest. The employee is notified of the entry and may contest it in writing within five (5) working days. Unresolved contests are reviewed by HR and then the COO.
- Counting. One error is counted once even when it affects several tasks. A systemic error caused by missing or contradictory instructions is logged against the process, not the person.
- Effect. Confirmed errors feed the Team of the Month score and any performance plan only after the contest window closes.
- Good faith. Voluntarily reporting one's own error does not remove it from the log but is recorded as mitigation. Concealing an error is a separate offense.
C11. Client Hour Logs & Invoice Dispute Windows
To set firm cut-offs so pay is predictable and disputes are time-bound.
- Daily logging. Client hours are logged the same day. Corrections are allowed within three (3) working days of the affected date.
- Cut-offs. Invoice submissions close on the fifteenth (15th) and the last day of each month. Late submissions roll into the next cycle.
- Query window. Payslip and invoice queries must be raised within five (5) working days of release; after that the computation is deemed accepted.
- Disputed amounts. Disputed hours are held while undisputed amounts are released on schedule.
- Reconciliation. Where the client's confirmed hours differ from the logged hours, the client-confirmed record prevails, and the difference is explained to the employee in writing.
- Overstatement. Deliberately inflating hours or duplicating a claim is a zero-tolerance offense.
C12. Statutory Benefits Enrolment
To fix who submits what and when, so SSS, PhilHealth, and Pag-IBIG coverage is never delayed by paperwork.
- Enrolment window. SSS, PhilHealth, and Pag-IBIG enrolment is completed within thirty (30) days of the start date. Dependents' documents are submitted within sixty (60) days.
- Employee duty. The employee submits the numbers and documents within ten (10) working days of joining. If the numbers are unavailable, HR records a provisional status and deductions are applied retroactively once enrolment completes.
- Tracking. HR updates the enrolment status of every employee in the statutory benefits tracker. Only the CEO, Finance, Senior Administrative Manager, and Junior Administrative Manager may view the tracker.
- Notification. Any change in status from not enrolled to processing to enrolled is communicated to the employee in writing.
- Queries. Contribution or coverage questions are raised through the HR Helpdesk and answered within five (5) working days.
- Accuracy. Falsified benefit documents are handled as a false declaration under the onboarding policy.
C13. Team Membership, Transfers & Leader Designation
To make team moves predictable and to keep scoring fair when someone moves mid-period.
- Definition. Teams are defined in Team Groups by HR and the COO. Membership is the basis for Team of the Month scoring and for Team Leader visibility.
- Effective dates. Transfers and additions take effect on the first (1st) or sixteenth (16th) of the month.
- Scoring effect. Attendance and EOD are counted for a member only from the date they were added to the team, so a mid-period move is scored proportionally in each team.
- Removals. A member removed during a period remains eligible for periods already scored, and their contribution is not retroactively removed.
- Employee-requested transfer. Filed thirty (30) days in advance through the HR Helpdesk, endorsed by both Team Leaders and approved by the COO. Operational transfers may be immediate.
- Leaders. Team Leaders are designated by the COO in writing. The designated leader is the attributing head for team recognition and accountability under Section 3.13.