How a manual encoding bottleneck inside a 320-person nationwide credit investigation team became a Google Workspace system that lifted client turnaround from 50% to 80% and doubled daily output per employee.
I supervised a nationwide credit investigation team of 320 people serving 10 banking clients, processing 500 to 1,000 cases a day. A manual encoding step was quietly capping how fast the whole operation could move. No one had been assigned to fix it, so I built the fix myself: a Google Sheets and Forms system that automated the encoding step, standardized it into a new SOP, and trained the team on it over a phased rollout. Client turnaround went from 50% to 80% on-time completion, and daily output per employee roughly doubled. The system is still in use today.
GDD Documentation Services Inc. runs nationwide credit investigations for banking clients across the Philippines. I joined as an Internal Credit Investigator, coordinating field dispatch for around 25 investigators, and was promoted to Supervisor within 8 months. In that role I directed operations across 270 field investigators deployed nationwide and 50 Head Office staff, supporting 10 banking clients and 500 to 1,000 active cases every day.
Field investigators send their findings in constantly, by phone and by messenger, from locations across the country. Every one of those reports has to become a clean, client-ready document before a bank ever sees it. That encoding step sits at the center of the whole operation, and it was entirely manual.
Every field report had to be manually converted into a client-ready document. At scale, across hundreds of cases a day, this step alone was capping how fast the team could close a case.
With cases distributed across 270 field investigators, there was no single, real-time view of case status. Bottlenecks were invisible until a client asked why turnaround had slipped.
The bottleneck was well known but nobody had been formally assigned to fix it. It had become an accepted cost of doing business.
I designed a Google Workspace system to replace the manual encoding step, built around three pieces working together:
The rollout was phased over roughly two months, not switched on all at once. I standardized the new process into a formal SOP and built training materials so the system would work the same way regardless of who was running it.
A ~2-month phased rollout let the team adjust gradually and let me catch problems in one region before they hit all 270 field investigators.
I wrote the SOP and training materials as part of the build, not after. That's what let the system survive being run by different people on different shifts.
Nobody had been assigned to fix the bottleneck. Rather than wait for it to become someone else's project, I built the fix within my own role.
Client turnaround improved to 80% on-time completion
Daily completed tasks per employee, same headcount
Employees trained on the new workflow; coached individually through the change
Beyond the numbers: case status became visible in real time instead of only at the point a client complained, and the workflow standardized how every region handled encoding, not just the ones I supervised directly. The system is still in use today.
Documentation is what makes an improvement outlast the person who built it. The training materials and SOP mattered as much as the Sheets system itself, since the goal was never "I can run this faster," it was "any of us can run this the same way." I'd also start the phased rollout even smaller next time. Two months to full nationwide adoption worked, but the early feedback from the first region would have been just as useful a few weeks sooner.
This system was built for and remains in use by GDD Documentation Services Inc. It's real operational work, not a public codebase, so there's no repository link here the way there is for BrightFlow. Details above are shared consistent with client confidentiality; happy to go deeper on the specifics in a conversation.