Case 01 · Portfolio

Renaming 12,000 certs without typing a single name.

Diagnose the workflow. Define the requirement. Direct the build.

Bottleneck

12,000 PDFs renamed by hand each cycle

Requirement

Rename at scale — operator-safe, reversible, no coding

Outcome

~40 hours saved per cycle

~/Certificates · 12,000 files

📄scan_0001_AlFajr_export_final_v2.pdfBEFORE

📄scan_0002_AlFajr_export_final_v2.pdfBEFORE

📄scan_0003_AlFajr_export_final_v2.pdfBEFORE

↓ Step 1 — Preview · Step 2 — Commit ↓

✓1587 - Ahmad Hassan.pdfAFTER

✓1588 - Siti Khadijah.pdfAFTER

✓1590 - Yusuf Ibrahim.pdfAFTER

Impact

What it saved per cycle

Before

~1 work week

~40 hours of one staff member doing nothing but renaming files.

After

~20 minutes

Two double-clicks. Operator scans the preview while the kettle boils.

Saved per cycle

~40 hours

Reclaimed for higher-value work — customer ops, quality checks, planning.

Workflow analysis

Before

Receive 12,000 PDFs from printer

→

⚠ Bottleneck Manual rename × 12,000 days of work · error-prone

→

Email-send pipeline

After

Receive 12,000 PDFs from printer

→

✓ Step 1 Preview Rename OCR extract · no files touched

→

✓ Step 2 Commit Rename idempotent · safe to re-run

→

Email-send pipeline

Requirements

01

Extract Order ID and recipient name from each cert

Both fields are already printed on the certificate — no manual data entry needed.
02

Run without coding knowledge

A non-technical operator must be able to launch it without ever opening a terminal.
03

Preview every change before committing

Operator sees the full rename plan first; nothing on disk changes until they confirm.
04

Safe to re-run

Already-renamed files are skipped, so partial cycles or re-runs cause no damage.
05

Filename format must stay in sync with downstream systems

The email-send pipeline and the cert lookup site both parse this filename. Any change propagates.