Apps & Software
Public Service Applications for Agencies: Submission, Tracking, and Archive
A good public service portal means applicants never have to call an officer to learn the status of their request. This guide maps the features an agency needs to prepare, from submission forms to the archive, along with the rules behind them.
SEO and Content Specialist
9 min read
Short answer: a public service application for a government agency needs at least six features: a step-by-step submission form, a registration number issued when the request is received, status tracking and notifications, a searchable document archive, role-based access with an activity log, and reports on the number of requests and how long they took. Two requirements apply across all of them: it must be usable by people with disabilities (with WCAG 2.2 as the reference) and it must protect applicants’ personal data under Law 27/2022.
Many agencies already have an official website, yet requests still arrive by email, WhatsApp messages, and at the front desk. Officers record them in a spreadsheet, and applicants phone in to ask about the status. A public service application replaces that chain with one recorded flow: the request comes in, gets a number, is handled by the right role, and its status can be checked by the applicant directly.
This guide is written for service managers, Information and Documentation Management Officers (PPID), and agency IT teams who are drafting requirements for a new portal or assessing one that is already running. The result can be used directly as input for an application requirements document before choosing a developer.
The legal basis that shapes a public service application
Most public service portal features are not a matter of taste but follow from legal obligations. Three laws most often determine what goes in:
| Regulation | Provision | Feature that follows |
|---|---|---|
| Law 14/2008 Article 13(1) | Public bodies appoint a PPID and build a system for providing information services quickly, easily, and fairly | A PPID role in the application, an information request flow |
| Law 14/2008 Article 22(4), (7), (8) | Proof of receipt in the form of a registration number when the request is received; written notice no later than 10 working days, extendable by no more than 7 working days with written reasons | Automatic registration numbers, a working-day deadline counter |
| Law 14/2008 Article 12 | Each year, announce the number of requests, time to fulfil them, number granted and refused, and reasons for refusal | An annual report drawn from application data |
| Law 14/2008 Articles 35-36 | Objections filed within 30 working days, answered by the PPID’s superior within 30 working days | An objection flow separate from the request flow |
| Law 25/2009 Article 23(4) | The public service information system includes at least the provider and staff profiles, service standards, service declaration, complaint handling, and performance assessment | Service information pages and a complaints module |
| Law 25/2009 Article 29 | Special treatment for vulnerable groups, including people with disabilities and the elderly | Interface accessibility |
| Law 27/2022 Articles 16, 46, 53 | Data collected in a limited and specific way; a data protection failure notified within 3 x 24 hours; processing for public services requires appointing a personal data protection officer | Minimal form fields, an activity log, a data protection officer role |
The procedure for information requests is further regulated by the Information Commission (Law 14/2008 Article 22(9)), so check the details against the technical rules that apply to your agency before the flow is locked.
Feature 1: a step-by-step submission form
A good submission form breaks the fields into several short steps and only asks for data the service actually needs. For information requests, Law 14/2008 Article 22(2) already lists the core fields: the applicant’s name and address, the subject and format of the information, and the requested delivery method.
What to prepare:
- Service type first. The applicant chooses the type of service, then the form adjusts its fields.
- Attachments with clear rules. File types and maximum size are stated before the applicant uploads, not after an upload fails.
- A summary before sending. The applicant reviews every field on one screen.
- Officer entry for non-written requests. Article 22(3) requires non-written requests to be recorded. Front desk and phone officers should enter those requests into the same system, so every request gets a number and appears in reports.
- No repeated fields. Data already entered in an earlier step is not requested again.
Feature 2: registration number, tracking, and status notifications
A registration number is proof that a request has been received, and for information requests submitted in person or by email it must be issued when the request is received (Law 14/2008 Article 22(4) and (5)). In the application, this means the number is generated automatically as soon as the form is submitted and sent immediately to the applicant’s email.
Request statuses should be few and meaningful to the applicant:
| Status | Meaning for the applicant | System note |
|---|---|---|
| Received | The request is recorded and numbered | The deadline starts counting |
| Under verification | Completeness is being checked | Can return to the applicant if something is missing |
| In progress | The information or service is being prepared | The handling officer is recorded |
| Extended | The time has been extended | A written reason is mandatory |
| Completed or Refused | The result or refusal is delivered | A reason for refusal is mandatory |
| Objection | The applicant files an objection | Moves to the PPID superior’s flow |
Three details that are often missed:
- Tracking uses the number plus one other piece of data, such as the email address, so someone guessing numbers cannot read other people’s requests.
- Deadlines are counted in working days, so the system needs a holiday calendar the admin can update every year.
- Notifications are sent whenever the status changes, plus a reminder to officers a few days before the deadline.
Feature 3: a searchable document archive
A document archive is where public information is stored and found again, by officers and by the public. Law 14/2008 Article 7(3) asks public bodies to build an information and documentation system so that public information is easy to access, and Article 11 requires certain information to be available at all times, including a list of all public information they hold.
A useful archive has:
- Fixed metadata: number, title, date, document type, owning unit, and validity status.
- Layered search: keywords, then filters by type, year, and status.
- File preview without having to download.
- An openness level per document: public, internal only, or exempt.
- Redacted versions. Article 22(7)(e) allows exempt parts to be blacked out with reasons. Make sure the text is truly removed from the file, not merely covered by a black box over text that can still be copied.
Feature 4: role-based access and an activity log
Role-based access means each account can only see and change the parts that belong to its job. Design the roles from the way work is done, not from job titles:
| Role | What it can do |
|---|---|
| Applicant | Submit, track, download results, file objections |
| Service officer | Record non-written requests, verify completeness |
| PPID or service manager | Decide, extend with reasons, send results |
| PPID superior | Handle objections |
| Personal data protection officer | Review access to applicant data and the activity log |
| IT admin | Manage accounts and configuration, without access to request content unless needed |
An activity log records who changed what and when. This log is what gets used during objections, audits, or a suspected data breach. For internal accounts, add two-factor authentication.
Accessibility: WCAG 2.2 as the reference
WCAG 2.2 is the W3C’s web content accessibility guideline, a Recommendation since 5 October 2023 and updated on 12 December 2024. It has three conformance levels: A, AA, and AAA. Law 25/2009 Article 29 requires special treatment for vulnerable groups, and a portal that is hard for people with disabilities or the elderly to use shuts the service off for them.
A checklist that matters directly on a service portal:
- Text contrast of at least 4.5:1 (criterion 1.4.3, level AA).
- Buttons and links at least 24 x 24 CSS pixels (2.5.8, AA), important for applicants on phones.
- No re-entering information already provided in the same process (3.3.7, A).
- Login without memory or transcription tests. A password field that refuses paste or blocks password managers does not meet criterion 3.3.8 (AA), unless another method is available.
- Help in the same place on every page, for example an officer contact (3.2.6, A).
Protecting applicants’ personal data
A public service portal processes personal data for public service purposes, and Law 27/2022 Article 53(1)(a) requires a data controller in that situation to appoint an official or officer who carries out the personal data protection function. The impact on application design:
- Collect only what is needed. Article 16(2) asks for data collection to be limited and specific. Do not ask for a national identity number or a photo of an ID if the service does not need it.
- Set a retention period. Data is deleted or destroyed after the retention period ends, unless regulations say otherwise (Article 16(2)(g)).
- Prepare the trail for incidents. If a data protection failure occurs, written notice must be given within 3 x 24 hours to the data subject and the authority (Article 46). The activity log and a list of stored data speed up preparing that notice.
- Assess the impact when the scale is large. Article 34 requires an impact assessment for high-risk processing, including large-scale processing.
The order in which to build a public service application
A service portal does not have to launch complete all at once. A safe order:
- First stage: the form, registration numbers, statuses, notifications, and basic roles. This is what immediately reduces calls to officers.
- Second stage: the document archive and the objection flow.
- Third stage: the annual report under Article 12, the complaints module, and performance assessment.
Time estimates and the factors behind them are discussed in How Long Does It Take to Build a Web Application?.
How Legia does it
Service portals with submission and tracking flows, searchable document archives, and a management dashboard are the type of system built under the Web Application Development service. Security covers role-based login, an activity log, automatic backups, and security checks, with the scope agreed from requirements mapping onward. The system is built in stages with a version you can try every two to three weeks, and a mid-sized system generally takes 3-6 months until full use. The application can be installed in the cloud or on the agency’s own servers, and the source code is stored in a repository in the agency’s name from day one. Other services in this pillar are on the Applications & Software page.
Frequently asked questions
Can the service portal be built into the agency’s existing website?
Yes, as long as the request part is an application with a database, roles, and an activity log, not just a form that sends an email. An email form provides no registration number, status, or reports.
How does the system count the 10-working-day deadline?
For public information requests, the system counts working days from the day the request is received, skipping weekends and the holidays entered by the admin. The 7-working-day extension can only be selected if the written reason is filled in.
Do applicants need to create an account?
Not always. Tracking can work with the registration number plus an email address. An account is useful when applicants submit often or need to see their request history.
Who decides whether the application runs on the agency’s server or in the cloud?
The agency, following the data placement policy that applies in its environment. This choice is best made during requirements mapping, because it affects backups and monitoring.
Sources
- Law Number 14 of 2008 on Public Information Disclosure, JDIH BPKperaturan.bpk.go.id
- Law Number 25 of 2009 on Public Services, JDIH BPKperaturan.bpk.go.id
- Law Number 27 of 2022 on Personal Data Protection, JDIH BPKperaturan.bpk.go.id
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2w3.org
- W3C WAI, Understanding Accessible Authentication (Minimum)w3.org
- W3C WAI, Understanding Target Size (Minimum)w3.org

