How Should LGUs Document Temporary Signing Authority for Remote Approvals?

Local government units (LGUs) should document temporary signing authority for remote approvals through a written, time-bounded authority record approved under applicable laws, local issuances, and office rules. The record should identify the regular and temporary signers, covered documents, exclusions, effective period, access conditions, and closure action. For teams using GoLGU digital signing support for LGUs, the digital process should follow the approved authority record. A system does not create legal authority.

This distinction matters when an approving official becomes unavailable because of travel, illness, or another authorized absence. A clear LGU signing delegation record shows who signs, which work is covered, and when the temporary arrangement ends.

Why Must the Authority Exist Before Remote Signing Starts?

A remote signature proves an electronic signing event. It does not answer every governance question behind the event. Staff still need to know whether the signer had authority over the specific document at the exact time of approval.

Republic Act No. 8792, or the Electronic Commerce Act of 2000, recognizes electronic signatures under stated identification, approval, reliability, and verification conditions. Section 18 addresses documents sent by a person authorized to act for an originator. These provisions support electronic transactions, but they do not appoint a substitute official or expand statutory powers.

Before granting access, the LGU should identify the proper authority, such as an applicable law, ordinance, executive issuance, office order, approved delegation, designation, or another valid instrument. Authorized legal or administrative personnel should confirm the basis.

What Does Temporary Signing Authority Cover?

Temporary authority answers a limited question: who will perform a defined approval duty while the regular signer is unavailable? It should not transfer every responsibility attached to the position.

A backup signer authorization should identify the approving source and the reason for the temporary arrangement. It should also separate authority over the decision from access to the digital tool. The authorizing official or office confirms the first. Information and Communications Technology (ICT) personnel administer the second according to the approved record.

Before activation, the LGU should settle four decisions:

Authority: Which law, issuance, order, or approved rule permits the temporary signer to act?
Coverage: Which document types, offices, amounts, transaction stages, or subject areas fall within the assignment?
Time: When does the assignment take effect, and what event ends it?
Closure: Who confirms the end of access and reviews approvals completed during the period?

These decisions align the temporary signer, Records personnel, ICT staff, and the originating office without treating access as proof of authority.

What Belongs in Temporary Signing Authority for Remote Approvals?

Temporary signing authority for remote approvals works best as a small record bundle. Together, its parts connect the authority decision with system administration and records custody.

1. The authority decision

The first record names the temporary signer, regular signer, issuing authority, reason, basis, and role limits. A job title alone does not show approval power over every office document.

2. The scope and time note

The second record defines the document scope for delegated signing through clear categories, limits, and exclusions. It also states the approval authority start and end date. If the end depends on an event, the record names who confirms it and how staff receive notice.

3. The system activation note

The third record connects authority to technical access. It identifies the administrator, activation time, approved scope, and source request. The temporary signer should use an individually assigned account and credential. Sharing the regular signer’s password, certificate, token, or account weakens identity evidence.

The system activation note belongs with the authority record, but it does not replace it. ICT staff should not decide who possesses legal signing power. Their role is to apply approved access settings and document the change.

4. The closure note

The fourth record confirms the closure event, who verified it, when access changed, and any unresolved document. It completes the delegated signing audit trail by connecting the authority basis, system action, signed records, timestamps, and closure evidence.

How Should LGUs Set the Document Scope for Delegated Signing?

The document scope for delegated signing should follow the actual responsibility being covered. Start with the office process, then identify the decision point normally assigned to the unavailable official. This approach prevents a temporary arrangement from extending into unrelated workflows.

Use recognizable categories instead of listing every expected file. For example, an authority record might cover routine certifications issued by one department during a five-day absence. It might exclude disciplinary actions, contracts above a stated threshold, documents requiring personal appearance, and matters reserved by law or policy for a named official.

Staff should also decide how to handle a document that changes category after review. If a routine request develops a legal issue or exceeds the approved limit, the temporary signer should stop the transaction and send it through the defined exception route. The remote approval continuity plan should identify the office that receives such exceptions.

What Should Happen When Access Begins and Ends?

The technical change should follow the authority record:

The designated office confirms the signed authority instrument.
The process owner identifies covered stages and excluded transactions.
ICT staff apply only the access needed for the approved period and scope.
The temporary signer and originating offices receive the limits, schedule, and exception route.
After the authorized office confirms closure, ICT staff end temporary access and Records personnel retain the linked evidence.

The approval authority start and end date should match across the authorizing record, access request, and closure note. A mismatch needs resolution before staff rely on the temporary arrangement for another approval.

How Should LGUs Handle an Urgent Exception?

An urgent request does not erase authority limits. If the document falls outside the approved scope, staff should use the designated escalation route rather than asking the temporary signer to proceed informally.

The exception note should describe the stopped transaction, the reason it sits outside scope, the office that received it, and the next authorized action. It should avoid passwords, private signing keys, or unnecessary personal information. The goal is to preserve the decision path without creating another sensitive record.

A remote approval continuity plan should define this route before an urgent case appears. It should also name an alternative official or process when no authorized temporary signer exists. Paper, electronic, or mixed handling must still follow the applicable authority and records requirements.

How Does GoLGU Support Temporary Signing Authority Records?

GoLGU provides a facility where requestors and approvers use digital certificates to sign remotely in the system. This supports the electronic signing step after the LGU has confirmed the signer’s authority, the covered documents, and the effective period.

For a temporary arrangement, the LGU should connect its approved authority instrument with the access request used for the GoLGU signing process. The named office should confirm the backup signer authorization before technical access changes. The system supports the signing activity, while the LGU’s valid laws, issuances, and internal rules govern who is authorized to act.

Implementation teams should test the approved route with a non-sensitive sample before live use. The test should confirm that the expected signer receives the right document, excluded items follow the exception path, and closure responsibility has a named owner. This preparation focuses GoLGU use on the approved operational need without treating software configuration as legal delegation.

What Does a Practical LGU Example Look Like?

Suppose a department head will attend an official activity outside the municipality for four working days. The office expects routine certifications to continue, while contracts and personnel actions remain outside the substitute signer’s role.

The authorized office issues a time-limited record naming the acting official and covered certification category. The note excludes contracts, personnel matters, and any transaction above the stated authority. ICT staff then apply access based on the approved request, and originating staff receive the effective schedule and exception contact.

During the period, the acting official signs one routine certification and returns another item that falls outside scope. When the department head resumes duty, the responsible office confirms the return, ICT staff close access, and Records personnel connect both outcomes with the closure note. The delegated signing audit trail stays focused on one authority period.

What Should LGUs Review After Each Temporary Assignment?

A short review should test whether the authority decision and completed work stayed within approved boundaries.

Did each signed document fall within the approved category and period?
Did staff route excluded documents to the named office?
Did system activation follow the signed request?
Did the signer use an individually assigned account and credential?
Did the closure action occur after the authorized office confirmed the end event?
Do retained records identify the signer, document, date, time, authority basis, and final status?

Republic Act No. 8792 addresses the reliability, authentication, attribution, and retention of electronic documents. Republic Act No. 12254 covers LGUs, back-end digital operations, records management, public service continuity, and the responsibilities of government agency heads. These laws support disciplined electronic processes, while the LGU must still apply the specific rules governing the authority involved.

What Should the LGU Decide Next?

Before another absence or disruption, assign one office to maintain the LGU signing delegation record and one authorized owner to confirm closure. Then review temporary signing authority for remote approvals against the actual document categories, statutory limits, and local issuances used by each department.

GoLGU should enter the process only after those decisions are clear. LGUs that want to review the connection between authority records and digital signing routes may request a GoLGU workflow consultation. Bring one current authority form, one document category, and one past exception so the discussion stays tied to a real office process.

Frequently Asked Questions

Does remote signing access give an employee temporary signing authority?

No. System access lets a user perform permitted technical actions. The LGU must establish authority through the applicable law, issuance, order, designation, or approved rule before the person signs.

What is the difference between an authority record and a signing credential?

The authority record explains why a person is permitted to approve defined documents. A signing credential helps identify and authenticate the person during the electronic signing event. Both serve different purposes.

What should an LGU signing delegation record show?

An LGU signing delegation record should show the authorized temporary signer, regular signer, issuing authority, basis, covered work, exclusions, effective period, access request, and closure evidence.

Should the backup signer use the regular signer’s account?

No. The backup signer authorization should lead to individually assigned access and credentials. Account or credential sharing weakens signer identification and makes later review less reliable.

What records support a delegated signing audit trail?

For temporary signing authority for remote approvals, a delegated signing audit trail should connect the authority instrument, access action, signed document, relevant timestamps, exception outcome, and closure evidence. Retention should follow applicable laws and the LGU’s approved records policy.

References

Disclaimer

This guide provides general operational information. LGUs should confirm signing authority, records duties, and system access with their authorized legal, administrative, Records, and ICT personnel.