Problem
Documents, revision notes, and decisions can become scattered across channels. Teams struggle to identify the latest status, the next owner, and a reliable change history.
Back to all projects
Operations platform case study
SIPANDU
A document approval system that brings submissions, reviews, revisions, decisions, and audit history into one role-based workflow.
Laravel 12Vue 3PostgreSQLRedisDocker
The public demo is read-only and uses temporary seeded data. Sign in with admin@sipandu.test, penilai@sipandu.test, or pemohon@sipandu.test; every account uses Password123!. Data returns to its initial state whenever the instance is recreated.
Solution
SIPANDU gives Administrators, Reviewers, and Applicants dedicated workspaces with private documents, scoring, queue notifications, and activity records.
Impact
The approval process becomes more organized, transparent, and traceable without relying on manual follow-ups through chat or separate spreadsheets.
Core workflow
One status language for every role
Every change moves through an explicit stage so applicants, reviewers, and administrators share the same source of truth.
01
Draft
The applicant prepares information and documents before submission.
02
Submitted
The request enters the queue and reaches the appropriate reviewers.
03
Under review
Reviewers add scores, notes, and a recommendation.
04
Revision or decision
The applicant updates the document or a final decision is issued.
Real application gallery
Explore SIPANDU through three roles
Choose a role, then browse several menus that are genuinely available in the SIPANDU application.
Every screenshot comes directly from SIPANDU. The live demo runs in isolation on Google Cloud with temporary SQLite storage for safety and cost control; the original project architecture still uses PostgreSQL, Redis, and Docker.
Real application screenshot
Administrator
Monitor queues, users, reviewer assignments, and workflow compliance from one dashboard.
1 / 3
A summary of submission totals, status distribution, submission trends, and the latest activity.
Application architecture
Built for secure workflows that can grow
Application layers are separated so the interface, business rules, queue processing, and data storage can evolve and operate with clear responsibilities.
- ✓Role-based authorization across every process
- ✓Private documents are never exposed to the public gallery
- ✓Redis cache and database-backed queues for background jobs
- ✓Consistent Docker environment for development
User experienceVue 3Role-specific dashboards
Application & APILaravel 12Business rules and authorization
Data & queuesPostgreSQL + RedisRelational data and background jobs
EnvironmentDockerConsistent services
SP
From process to product
Discuss your requirements Still managing approvals manually?
Mikerni Studio helps map the process, roles, data, and risks before building the right operations platform.