Certindo Request — a paper workflow, digitized.

What the project is

Certindo's calibration requests previously depended on a paper-first process. Client details, equipment lists, staff review, and formal document preparation all created repeated manual work and made the flow harder to track from one stage to the next.

How I approached it

I translated that operational process into two connected experiences. Clients complete a guided three-step form covering company information, calibration services, and equipment before reviewing their submission. Staff then work from an authenticated dashboard where requests can be searched, filtered, evaluated, completed, and archived.

From interface to system

I built the full-stack system with Next.js, Prisma, PostgreSQL, and NextAuth. Submitted request and equipment data is validated and stored as structured records with generated letter numbers and clear processing states. After staff approval, the system maps the approved data into an existing DOCX template and generates the completed document in memory with the required signature already included.

How the pieces connect

A simplified view of the implemented product flow—not a claim about infrastructure that is not public.

1. 01

   Request

   Guide clients through company, service, and equipment data

   Next.js
2. 02

   Validate

   Store structured submissions and generated letter numbers

   PrismaPostgreSQL
3. 03

   Review

   Let authenticated staff evaluate and update each request

   NextAuth.js
4. 04

   Generate

   Map approved data into the formal signed document

   Docxtemplater

What changed

The live companion system replaces the paper-first handoff with one connected workflow from client intake through internal review and document generation. Staff no longer need to retype the same request into a Word document, while each application remains visible through its current status.

What I learned

This project strengthened my full-stack thinking because the core challenge was not an individual page—it was preserving one reliable flow across validation, relational data, authentication, review states, document templates, and two very different user interfaces.