How Should HR Map Compensatory Time-Off Approval Before Portal Configuration?

Before configuring a portal, Human Resources (HR) staff should map the complete compensatory time-off approval workflow, from authorized overtime to final use of Compensatory Time-Off (CTO). The map should identify the overtime authority, Compensatory Overtime Credit (COC) record, employee request, current balance, schedule approver, HR verification, return or rescheduling path, and final attendance record. Portal settings should reflect the government's approved process rather than create a new approval rule.

For LGUs organizing LGU human resource workflow records, this mapping should happen before fields, roles, buttons, and status labels are configured. A portal administrator implements the route, while current Civil Service Commission (CSC), Department of Budget and Management (DBM), and LGU rules remain the source of authority.

What Should a Compensatory Time Off Approval Workflow Map Before Configuration?

HR should start with the decision route, not the screen design. CSC-DBM Joint Circular No. 2, s. 2004 separates authorized overtime, COC recording, the employee's CTO request, schedule approval, and actual CTO use. The 2015 CSC-DBM circular expressly covers Local Government Units (LGUs) and states that CTO is generally the form of overtime remuneration under the 2004 and 2005 CTO guidelines.

The portal should therefore represent an existing administrative sequence. It should not reduce CTO to a single generic request button without a source record or approval basis.

Which Overtime Record Should Create the Basis for CTO?

The first dependency is the authorized overtime record. Under the 2004 circular, the Head of Office or authorized official issues an Office Order authorizing overtime services and identifying the work to be completed. The employee then renders the authorized service.

A government overtime offset record should preserve the Office Order or equivalent authority, work period, employee, and resulting COC reference. The same government overtime offset record should not be treated as permission to use CTO on any date. Earning the credit and approving the CTO schedule are separate decisions.

How Should HR Verify the COC Balance Before Routing the Request?

Before the request reaches the schedule approver, HR should verify that the employee has a valid COC record and enough available credit under the applicable rules. The 2004 circular assigns HR the role of summarizing overtime services and equivalent COCs, while employees are responsible for monitoring earned COCs against those already used by the CTO.

The 2005 joint circular amended the earlier rules on the use of COCs. Portal logic should therefore reference the current policy instead of hard-coding a legacy assumption about availability or expiration. If the portal balance and the official HR record disagree, the request should be routed as an exception rather than approved automatically.

Who Should Submit the CTO Request?

The 2004 procedure places the request for approval of the CTO schedule with the employee. In a portal, the request should point to the verified COC source and include only the details needed for review.

Useful fields include the employee, requested date or schedule, number of CTO hours requested, source COC reference, and remarks required by the LGU's internal procedure. These fields form the core of compensatory leave request mapping.

A second use of compensatory leave request mapping is validation. HR should decide which fields come from official records and which details employees may enter themselves. Free-text entries should not replace the official COC source.

Who Should Approve the CTO Schedule?

The portal should route the schedule decision to the Head of Office or another authorized official recognized by the applicable rules and the LGU's valid internal procedure. The 2004 circular states that the employee first obtains approval for the CTO schedule and assigns the Heads of Offices the responsibility for approving or disapproving requested schedules without compromising service delivery.

The 2015 circular separately gives agency heads responsibility for internal overtime procedures and authority to approve requests to render overtime services. Those are related but different decisions. Approval to work overtime is not the same as approval of the later CTO schedule.

An HR offset approval route should identify the actual authorized schedule approver. The HR offset approval route should not substitute "immediate supervisor" or "HR administrator" unless the LGU's rules grant that role the required authority.

What Should HR Check Before the Request Reaches the Approver?

HR's pre-routing check should confirm the employee, overtime authority, COC source, available balance, requested schedule, and any duplicate or overlapping request. This is an administrative check, not a silent approval by HR.

If validation fails, return the request with a specific reason. Distinguish missing evidence, invalid COC reference, insufficient balance, duplicate request, and scheduling issues instead of hiding every problem under one generic rejection label.

Which Portal Statuses Should HR Define?

Statuses should describe real decisions. A practical setup might use the following statuses: Draft, Submitted, HR Verification, Returned for Correction, Pending Schedule Approval, Approved, Disapproved, Rescheduled, Availed, and Closed. These are recommended workflow labels, not mandatory national terms.

HR should define who may move a request into each status and what record changes at that point. "Approved" should mean the authorized schedule decision is complete. "Availed" should mean the approved CTO has been reflected according to the LGU's attendance-record procedure.

How Should Rejection and Rescheduling Work?

The 2004 rules recognize that service needs matter when a CTO is scheduled and that a schedule may be recalled and rescheduled when service exigencies require it. Portal design should therefore support more than approval and denial.

A returned or rescheduled request should preserve the reason, the originally requested date, the revised date when applicable, and the responsible role. This history helps HR explain why the final CTO date differs from the employee's first request.

Who Should Own Exceptions Before Go-Live?

HR should identify who resolves balance mismatches, incorrect overtime references, employee record errors, schedule changes, and routing failures. One person does not need to own every exception.

Balance issues may belong to HR records staff, approval questions to the authorized official, and technical routing problems to the portal administrator. Technical access should not transfer policy authority to the administrator.

What Should the Portal Administrator Configure?

The administrator should translate the approved map into roles, fields, permissions, routing conditions, notifications, and audit history. Good employee portal approval configuration begins only after HR confirms the procedure.

The administrator should know who may submit, verify COC records, approve schedules, return requests, reschedule requests, and correct system data. The employee portal approval configuration should prevent users from bypassing required stages merely because they have broad technical access.

What Records Should Stay Connected After Approval?

After approval, keep the request linked to the overtime authority, the COC certificate or equivalent HR source, the approval history, the schedule, and the attendance entry. The 2004 circular assigns HR responsibility for reflecting CTO applications on time records and for reporting overtime services and equivalent COCs.

The digital record should answer three separate questions: How was the COC earned? Who approved the CTO schedule? When was the CTO actually used?

Which Test Cases Should HR Run Before Portal Go-Live?

HR should test cases that force the route to make a clear decision:

• valid COC record with enough available credit

• no matching overtime authority

• request above the available COC balance

• duplicate request for the same schedule

• request returned and resubmitted

• approved request later rescheduled because of service needs

• request routed to the wrong approving role

• completed CTO with no corresponding attendance update

These tests validate compensatory time off approval workflow behavior while also checking permissions, notifications, status transitions, exception handling, and audit history.

What Example Shows a Configuration-Ready CTO Route?

Example: An LGU department issues an Office Order for overtime on a time-sensitive activity. After the authorized work is rendered, HR records the COC, and the required certificate or source record is issued. The employee later requests CTO for a specific date.

HR verifies the COC source and balance, then routes the request to the authorized schedule approver. The date is approved, but a later service requirement forces rescheduling. The portal keeps the original request, approval, rescheduling reason, revised date, and eventual attendance update connected.

This is a workflow example, not a new government rule. The LGU still follows current CSC-DBM circulars and its valid internal procedures.

What Mistakes Should HR Avoid Before Configuration?

• Do not configure CTO as a generic leave request without a source COC record.

• Do not treat approved overtime as automatic approval of the CTO schedule.

• Do not let technical administrators create approval authority.

• Do not use an employee-entered balance as the official COC source.

• Do not hard-code an old CTO rule without checking later amendments.

• Do not combine HR verification, schedule approval, and actual CTO use into one status.

• Do not erase return or rescheduling history.

• Do not mix this route with payroll preparation or broad attendance-correction workflows.

Frequently Asked Questions

Is CTO the same as overtime pay?

No. The 2015 CSC-DBM circular states that CTO is generally the form of remuneration for overtime services, while cash Overtime Pay is allowed under specified conditions and limitations.

Can an employee use CTO without an authorized overtime record?

The CTO route should trace back to authorized overtime and the resulting COC record under the applicable rules. A portal request alone should not create the underlying credit.

Should HR approve every CTO request when the employee has enough COC?

No. A valid balance supports the request, but schedule approval remains a separate decision and must follow the authorized process.

Can the portal administrator choose the CTO approver?

The administrator may configure the role as specified in the LGU's authorized procedure. Technical access alone does not create authority to decide the CTO schedule.

What if the approved CTO date needs to change?

Keep the original schedule, the revised schedule, the reason, and the authorized action connected. The 2004 rules recognize recall and rescheduling when service exigencies require it.

What should HR verify before go-live?

HR should verify the overtime authority, COC source, balance source, requester permissions, approver role, return and rescheduling logic, attendance update, exception ownership, and audit history before employees use the portal.

What Is the Practical Takeaway?

A reliable compensatory time off approval workflow starts before portal configuration. HR should map the authorized overtime source, COC record, employee request, balance verification, schedule approval, return and rescheduling path, final attendance update, and exception ownership. The portal should enforce those relationships without inventing legal authority or replacing current CSC-DBM and LGU rules.

If your LGU is reviewing how HR records, timekeeping, and approval routes should fit into a digital system, schedule a GoLGU consultation to discuss system requirements.

Reference

• CSC-DBM Joint Circular No. 2, s. 2004, Non-Monetary Remuneration for Overtime Services Rendered

• CSC-DBM Joint Circular No. 2-A, s. 2005, Amendments to Joint Circular No. 2, s. 2004

• CSC-DBM Joint Circular No. 2, s. 2015, Policies and Guidelines on Overtime Services and Overtime Pay for Government Employees

Disclaimer

This guide provides operational workflow-planning guidance for Philippine local government HR teams. It does not replace CSC-DBM circulars, Civil Service Commission rules, Department of Budget and Management issuances, valid LGU internal procedures, employment rules, or legal advice. CTO eligibility, COC records, approval authority, scheduling, and record treatment should follow the current rules applicable to the employee and LGU.