Mandaue DTS Staff sign in
Built for RA 12254 · E-Governance Act

Every document. Every hand-off. On the clock.

Every letter that reaches the City Planning Office gets a number, a deadline and a trail. You can see where yours is; the office can see what it is sitting on. Both answers come from the same record.

3 · 7 · 20
working-day tiers, enforced
0
editable audit rows
6
departments, one configuration

Public tracker

Track your document

Enter the tracking code printed on your receipt or sent to you by SMS.

The code on your receipt slip — not the log number staff quote internally. Its last character is a check digit, so a mistyped code will not match. Deadlines are counted in working days under RA 11032.

Holding a document this office issued and want to know it is genuine? Check its verification code.

57 documents registered · 109 indorsements recorded

Zero missed statutory deadlines
At-risk alerts fire at half the tier, not after the breach.
Full audit trail
Every hop is an Indorsement — append-only, timestamped, named.
One system, six departments
CPDO first, then the Assessor’s Office, Legal and the rest.
The phone stops ringing
Applicants check their own reference instead of visiting.

The 3-7-20 rule · RA 11032

A clock that only counts working days — and pauses when it should.

Each document type carries a statutory tier. The clock starts at registration, skips weekends and holidays, pauses while a document is returned for compliance, and warns the division at the halfway mark.

Working days elapsed example
2 of 3
Remaining
1 working day
At risk
Clock pauses
1
not charged to the office
Half the tier is spent. The division head is notified before the breach, not after it.

How it works

Follow a letter through the office.

A letter arrives at the counter. Somewhere between there and an answer it used to disappear into a tray. Here is where it goes instead — pick a stage, or press play and watch it travel.

Receive and encode

receiving

It is opened, logged and given its number. You get that number on your receipt — it is what you type into the tracker.

Who has it
The counter
What you see as the sender
Received
The clock
No separate limit — the deadline for the whole document keeps running

Director approval

director_approval

They decide which unit should handle it. Nothing moves until they do, so the trail always shows who sent it where.

Who has it
The department head
What you see as the sender
Under review
The clock
No separate limit — the deadline for the whole document keeps running

Unit head action

unit_head

They put it on a named person's desk. Until they do, it belongs to the unit rather than to anybody in particular.

Who has it
The unit head
What you see as the sender
Being acted on
The clock
No separate limit — the deadline for the whole document keeps running

Action by assignee

staff_action

The actual work — the site visit, the checking, the drafting. Their answer is what closes it.

Who has it
The officer handling it — and their unit head has to confirm the name before work can start
What you see as the sender
Being acted on
The clock
No separate limit — the deadline for the whole document keeps running
Every stage above is read from the live workflow, not drawn by hand.

The same journey, from above

Everybody can see whose desk it is on.

One row per person. The two gold boxes are the points where somebody has to agree before it moves — the head approves the routing, and the officer accepts the work before starting. After that it is in several hands at once, and it only finishes when the last of them reports.

ARRIVES LOGGED APPROVED ASSIGNED DONE RELEASED You The counter Department head Unit head The officer Hands it in Signs for it Logged and numbered Approves the routing Signs and releases Puts it on a named desk Accepts, then does the work one branch per unit — all at the same time
Nothing reaches a unit until the head has approved the routing, so the trail always shows who sent it where. The number you are given at the counter tracks all of it.

What it is for

Four people, four different problems.

The same record answers all of them, which is the whole point of keeping it in one place.

If you sent the letter

“Has anyone even looked at it?”

Type your number into the tracker. You get the stage it has reached and the date it got there — no phone call, no trip to the office.

If you work at the counter

“Where did that one go?”

Every hand-off is written down as it happens, with a name and a time. Nothing is remembered, and nothing is somebody's word against somebody else's.

If you run a unit

“What is my team sitting on?”

One list of what is on whose desk and how long it has been there. The system warns you at the halfway mark, not after the deadline has gone.

If you sign things

“What is waiting on me?”

Your approvals in one queue, the document itself attached to each. Sign, send it on, or send it back with a reason — all three are recorded.

Backlog-risk dashboard

See the breach before the applicant does.

Documents in motion, SLA compliance by type, and a “needs your action” list sorted by tightest deadline — the division head's morning in one screen.

Documents in motion

A 30-day trend of what arrived against what went out.

SLA compliance by type

Share of released documents that met their tier — measured, with unmeasured ones excluded rather than counted as successes.

Needs your action

Sorted by the tightest statutory deadline, not by arrival.

Sign it. Find it. Hand it over.

Signature block

Prepared by, recommending approval, noted by, approved by — one immutable row per slot, with a field reserved for the national PKI so approvals do not need retrofitting when PNPKI lands.

Archive and search

Completed documents stay findable by reference, title, applicant, type or date. The completed view states whether each one met its statutory tier — the archive is the compliance record.

Records disposal

Retention runs off a file plan, and disposal is a reviewed workflow carrying a National Archives authority reference. Nothing is ever deleted outright.

Compliance

The law describes a DTS. This is one.

RA 12254's IRR took effect on 9 April 2026 and mandates digitalised, tracked, verifiable document workflows. The clocks are running — the once-only interoperability deadline is 9 April 2028.

RA 12254 — E-Governance Act
Digitalised workflows from creation through routing, tracking, verification and archiving. Unique reference identifiers, and an API layer designed to the PGIF for once-only data exchange.
IRR §15.12 · §34
RA 11032 — Ease of Doing Business
The 3-7-20 working-day tiers are enforced per document type, with clock pauses for compliance returns and declared work suspensions.
3 · 7 · 20
RA 10173 — Data Privacy Act
Department-private by default, a personal-data access log covering ordinary reads and not only transfers, and a Privacy Impact Assessment reviewed annually.
NPC · PIA
RA 9470 — National Archives
Retention and disposition run off a NAP-approved schedule. Disposal requires a recorded authority; there is no path that deletes a record outright.
RDS · NAP

Why this one

Built around how CPDO already works.

Your routing, your document types, your deadlines — configured to the office rather than the office adapted to the software, and yours to change the week something changes.

Mandaue DTSA general-purpose system
Routing built for CPDO zoning and permit workflows Configured to your rules Generic document flow
3-7-20 SLA clock with working-day logic Enforced, with pauses and at-risk alerts Manual tracking
Cross-department transfer within Mandaue One core, one query One office at a time
Change a route or add a document type Same week, by MISO A change request in a queue
Local support and customisation OmniSystem, Cebu-based A remote helpdesk
Data residency and control PH cloud, your tenancy A shared platform

Start with CPDO. Roll out to the city.

A 45-minute walkthrough with your division heads and MISO. We bring the sandbox loaded with your document types.

Hosted in the Philippines CTO Cloud · Clark + Manila
ISO 27001ISO 27018SOC 2RTO 4h · RPO 24h

Correspondent data never leaves the country. Geo-redundant backups, disaster-recovery drills, and an annual Privacy Impact Assessment review under the maintenance contract.