Pengadilan Negeri Kabupaten Madiun

1 / 5

Pengawasan Internal is a digital supervision platform built for Pengadilan Negeri Kabupaten Madiun to manage the entire court supervision lifecycle — from daily PTSP checks and weekly field monitoring to evidence documentation, multi-level verification, and executive reporting.

More than a digital form system, Pengawasan Internal was designed as a workflow platform that mirrors the court's actual supervision structure: six PTSP service points, five supervision item categories, morning and afternoon schedules, and a hierarchical approval chain involving supervisors, the Chief Judge, and the Vice Chief Judge.

The Problem

Court supervision at PN Kabupaten Madiun covers operational compliance and service quality across multiple organizational units. Before the system existed, this critical function relied entirely on manual processes.

Fragmented Documentation

Supervision results were recorded on physical forms and stored in various locations — filing cabinets, personal folders, and scattered digital files. When leadership needed to review past findings, assembling the full picture required hunting through multiple repositories. There was no single place where all supervision evidence lived.

Invisible Findings

The court had no way to answer fundamental questions about its own supervision:

• How many findings were recorded this quarter?
• Which service points had recurring issues?
• How many findings had been followed up versus outstanding?
• Which organizational units needed more attention?

These questions required manual counting and cross-referencing — work that rarely happened because it was too time-consuming.

Slow Reporting Cycle

Preparing supervision reports for periodic reviews meant collecting data from individual supervisors, reconciling different formats, manually counting findings, and assembling everything into a coherent summary. The process took days and was outdated by the time it reached leadership.

No Real-Time Visibility

Chief Judge and Vice Chief Judge had no way to see supervision activity as it happened. They learned about findings only when someone personally reported them or when a periodic report was assembled — creating blind spots in oversight.

Evidence at Risk of Loss

Photo evidence of supervision findings — damaged facilities, service irregularities, procedural deviations — existed on individual supervisors' phones. There was no centralized repository linking photos to specific findings, creating a real risk that evidence would be lost, deleted, or become impossible to associate with the right supervision activity.

The Solution Architecture

Pengawasan Internal solves these problems by treating court supervision as a structured digital workflow — not just a collection of forms.

The system was designed around the court's actual supervision hierarchy:

The Workflow Engine

The core architectural decision was to model supervision as a state machine with defined stages:

Each stage has automatic status tracking, timestamp logging, and actor attribution. This creates a complete audit trail from the moment a supervisor observes something to the point where it's resolved and reported.

How the System Works

1. PTSP Daily Monitoring

Each day, supervisors conduct structured checks across six PTSP (Pelayanan Terpadu Satu Pintu) service points:

Each supervision session follows a structured form:

• Morning and afternoon schedules — ensuring coverage throughout the operating day
• Five supervision item categories — covering the full range of internal supervision criteria
• Digital checklist — supervisors check compliance items specific to each service point
• Photo evidence — supervisors attach photos directly to the supervision form at the point of observation
• Finding descriptions — structured text fields documenting what was observed
• Digital signature — the supervisor signs the report digitally within the system

2. Weekly Field Supervision

Hakim Pengawas Bidang (Field Supervising Judges) conduct weekly evaluations of their assigned organizational units. The system supports:

• Periodic evaluation forms tailored to each field
• Finding documentation with supporting evidence
• Recommendation entries for process improvements
• Historical tracking of recurring issues per field

3. Monthly Comprehensive Review

Monthly supervision provides a higher-level evaluation covering all organizational units. Features include:

• Upload of monthly supervision reports
• Structured review process
• Historical evaluation records
• Trend visibility across months

4. Evidence Management

All supervision evidence is stored in a centralized repository:

• Photos — attached directly to findings at the point of observation
• Notes — structured finding descriptions
• Supporting documents — additional files relevant to specific findings

Every piece of evidence is linked to its originating supervision activity, creating a traceable chain from observation to documentation. This eliminates the risk of evidence existing on personal devices without institutional backup.

5. Multi-Level Verification Workflow

Supervision results follow a formal verification chain:

At each level, the reviewer can:

• Approve — the supervision result moves to the next stage
• Request revision — specific feedback is recorded and the supervisor can make corrections
• Add verification notes — institutional comments become part of the permanent record

This workflow ensures accountability at every stage and creates a clear chain of responsibility.

6. Executive Dashboard

The dashboard provides leadership with real-time visibility into supervision activity:

• Total supervision count — how many supervision sessions have been conducted
• Finding count — total findings recorded across all supervision types
• Follow-up status — how many findings are resolved versus outstanding
• Trend analysis — supervision activity patterns over time
• Statistics by field — which organizational units have the most findings
• Period comparison — current period versus previous periods

7. Automated Reporting

Reports can be generated based on:

• Time period — daily, weekly, monthly, or custom date ranges
• Organizational unit — filter by specific fields or service points
• Supervision type — daily PTSP, weekly field, or monthly comprehensive

Output formats:

• PDF — for formal documentation and archival
• Excel — for further analysis and data manipulation

Before vs After

Impact

For Supervisors

Structured Workflow — Supervision follows a consistent, repeatable process. No more wondering what to check or how to document findings.

Immediate Evidence Capture — Photos are attached at the point of observation, eliminating the information loss that happens when documentation is deferred.

Digital Signatures — No more printing, signing, and scanning. Reports are signed digitally within the system.

For Leadership

Real-Time Oversight — The Chief Judge and Vice Chief Judge can see supervision activity as it happens, not days later in an assembled report.

Data-Driven Decisions — Statistics on findings by field, by period, and by type enable evidence-based resource allocation and process improvement.

Accountability Chain — The multi-level verification workflow creates clear responsibility for every supervision result.

For the Institution

Audit Readiness — Complete documentation trail from observation through verification to resolution. Every action is timestamped and attributed.

Institutional Memory — Supervision evidence and findings are preserved in the system regardless of personnel changes.

Process Consistency — Standardized supervision forms ensure that all service points are evaluated against the same criteria.

Engineering Challenges

Multi-Level Workflow Design

The greatest challenge was designing a verification workflow that accurately reflected the court's organizational hierarchy while remaining usable. Each approval level needed clear visibility into what required their attention, what had been approved, and what needed revision — without overwhelming them with information.

The solution was a status-driven interface where each role sees only the items relevant to their current action, with clear indicators of what's pending, in progress, or completed.

Evidence-to-Finding Association

Linking photos and documents to specific supervision activities required careful data modeling. The system needed to support multiple evidence items per finding, maintain the association through the verification workflow, and make everything searchable for future reference.

Real-Time Dashboard Performance

The dashboard aggregates data across thousands of supervision sessions, findings, and verification states. Querying this data in real-time while maintaining system responsiveness required careful database indexing and query optimization.

Government Deployment Constraints

Like all Indonesian government systems, the platform needed to run on standard infrastructure without exotic dependencies. Laravel, MySQL, and standard PHP hosting provided the reliability and compatibility needed for institutional deployment.

Tech Stack

Lessons Learned

• Institutional systems must mirror institutional structure. A supervision system for a court cannot use a generic template. It must reflect the actual hierarchy, the actual service points, and the actual verification chain that the institution uses.

• Evidence capture at the point of observation is critical. The gap between observing a finding and documenting it later is where information is lost. Making photo evidence part of the supervision form — not a separate step — ensures completeness.

• Verification workflows build accountability. When supervision results pass through a formal approval chain with digital signatures and timestamps, accountability becomes structural rather than dependent on individual diligence.

• Dashboards transform data into decisions. Raw supervision data has limited value. When leadership can see trends, compare periods, and drill into specific areas, supervision data becomes a decision-making tool rather than just a record.