8 min readcapstonecivic techdelivery
You Don't Have to Write the Code to Be the Reason It Works
What I learned leading delivery on a civic tech capstone
Nearly 1.9 million Filipinos work in an industry that earned over $40 billion in 2025 serving companies around the world. Yet as of 2024, only 113 of the country’s 1,634 local governments had fully set up the electronic one-stop shop for business permits that the law requires.
If that’s where things stand for a service the law requires to go online, picture one no law covers. A student in Pasay City lines up with a paper form and eight documents to keep their city scholarship. One document is missing, so they’re sent home to try again another day. Next semester, they do it all over again. That’s how a ₱20 million program serving about 1,700 scholars ran for years.
That scene wasn’t abstract to us. All three of us on the team were scholars ourselves, through DOST (the Department of Science and Technology) and a city scholarship program, and we knew what those lines cost: a missed class, an afternoon that should have gone to studying or catching up, sometimes just the rest a busy student needs.
So when my capstone team was choosing a topic and project, I pitched a platform that would give scholars that time back. We spent a year building it. It passed every test. Its testers rated it 4.74 out of 5.
It never launched. And the reason had nothing to do with the code.
Finding my job
I’ll be upfront: I didn’t write the code. Our team lead led development, and our Product Owner handled communications with the bureau and helped with documentation. That left an open question: where could I add the most?
What was missing was someone whose main focus was three things: whether the platform worked, whether it would be ready on time, and whether real people could use it. So I took that on. I wrote the test cases and kept the fix list, set and chased internal deadlines, and ran user acceptance testing. I also wrote most of the final paper and presented it with the team at the defense.
It wasn’t the work I pictured when I signed up as a developer, and none of it is glamorous. But I’d rather fill the gap a team actually has than hold out for the role I imagined. And this is the work that separates a project that demos well from one that holds up.
The best decision wasn’t ours
Before designing anything, the team interviewed bureau staff and applicants. The platform uses OCR to read uploads, especially application forms, and we could have let it approve matching documents automatically. The staff pushed back: certified true copies of grades still need a human check, because that’s what keeps an award legally sound. They would be the ones running the system every day, and they were right.
So the OCR stayed, but the platform and the reviewers decide together. The system does what software is good at: reading uploads, checking applications against the eligibility rules, and flagging anything missing. The reviewers do what only people can: judging the documents and deciding who receives an award. It’s slower than full automation, but every award can be traced to the person who approved it. It’s my favorite decision in the project.
From there, our team lead built it into a working platform: online applications, renewals pre-filled from last semester, role-based approvals with two-factor sign-in, and one-click reports.
Turning failures into a fix list
I wrote functional test cases for all seven modules, from registration and login to status tracking, notifications and session handling. Most of them failed the first time I ran them, which is exactly what they were for. Each failure became a line on our fix list, and our team lead worked through them one by one until, by the final round, every test passed. I’m the person on a team who keeps the list, so nothing that’s been flagged gets forgotten. That’s the part of my work I’m proudest of.
Then came the real test: people. I ran user acceptance testing with 30 testers from nine cities: students, teachers and administrative staff, including staff from Pasay City. They used the live platform on their own phones and laptops and rated it through a questionnaire our adviser and the bureau had reviewed. The overall score was 4.74 out of 5. The lowest category, interface and performance, still scored 4.66, and it’s the first thing I’d improve, since many applicants rely on their phones.
Why it never launched
So here’s the reason I promised. Our platform passed every functional test, earned a 4.74 from its testers, and was recommended for adoption as the bureau’s official system. Then the defense ended. We reached out to the bureau afterward, but our messages went unanswered. Today the code sits in a repository, working and unused.
The code was never the problem. What the platform didn’t have was a person inside the bureau whose job was to keep it alive, and a plan for handing it over. We didn’t secure either before the defense. And honestly, after a year-long marathon, all three of us were too tired to push harder.
Looking back, that’s what changed how I see this work. I used to think the hard part of civic tech was building. Now I think it’s everything after: finding an owner, earning trust, and making a new system part of how an office actually works.
The good news is that the country is moving. In September 2025, the E-Governance Act put national agencies and local governments alike on the path to digital services. The government’s eGovPH app has passed 56 million downloads and 800 million transactions, with usage up 700% in a year. People clearly want this.
But demand is only half of it. When usage surged in April 2026, eGovPH had intermittent outages for nearly two days, and the department behind it admitted it was short on cloud resources. Building something people want is the start. Keeping it running, funded and owned is the real work.
That’s where I think the next wave of Filipino tech talent belongs. Volunteers built BetterGov.ph, which grew from four volunteers to about 2,400 in a few months. Groups like WeSolve Philippines have spent years building coalitions between government and citizens. The talent is clearly there. What’s missing is the bridge between what we build and what actually gets used, and that’s the skill I want to get better at next.
I didn’t write a single line of this platform’s code. I’m still part of the reason it worked. Next time, I want to be part of the reason it gets used.
If you’re starting your capstone
Let me be your kuya for a second. We made it, but with more last-minute scrambling than I’d like to admit. If I could do my capstone again, I’d walk in on day one with a completely different playbook. So if you’re about to start yours, here’s what I wish someone had sat me down and told me.
Be honest about your time. You’re not just a capstone student. You’ve got classes, maybe a scholarship to keep, maybe an org you’re running. We had all of that, and our plan pretended we didn’t. Set weekly goals and leave room for the bad weeks, so you don’t end up cramming everything into the last month.
Practice project management, whatever your role. Don’t leave the planning to your leader alone. Whether you’re leading or a member, know the timeline, track your own tasks, and speak up early when something slips. A capstone runs best when everyone is hand in hand on it.
Agree on roles and expectations first. Sit down in week one and decide who owns what: development, testing, documentation, talking to your client. Then say out loud what each of you expects from the others, before anyone commits. A lot of team friction comes from expectations nobody said.
Make testing someone’s job. Not “we’ll test it later.” Give testing an owner, and don’t call a feature done until it passes its test. Trust me, testing you push to the end becomes your problem at the end.
Don’t let one person hold all the code. If only one teammate understands the system, every deadline runs through them, and that’s a lot of pressure on one person. Pair up, review each other’s work, and make sure at least two of you can explain every part. If you’re in computer science or IT, this matters even more: your capstone is your best chance to show you can build, so make sure everyone gets real time in the code.
Show your work early, even when it’s rough. Demo to your adviser and your client every few weeks, not just at the defense. It’s much easier to hear “this part’s wrong” in a casual check-in than in front of a panel.
Set checkpoints inside your team. Between those demos, set small targets, like a feature working by Friday or a chapter drafted by next week. That way everyone keeps moving instead of waiting for the deadline to start.
If you want it used, plan for life after the defense. Not every capstone needs to outlive graduation, and that’s okay. But if you want yours to actually help people, start asking early: who on your client’s side will run this once you’re gone? Who keeps it updated next semester? If nobody can answer, the project can end at the defense no matter how good the code is. Ours did.
So if you’re choosing a capstone, don’t pick it just to get through the defense. Pick a cause you or your group genuinely stand for, and a problem real people actually have. Then build something they’ll still be using after you graduate. Your capstone can be more than a requirement for your diploma. Ours stopped at the defense. Yours doesn’t have to.
Thank you so much to my two teammates, our team lead and our Product Owner, for a year of building this together, last-minute scrambles and all. What a wild journey it was. Thank you too to our adviser, for guiding us through it. I’m proud of what we made, and prouder of what it taught me.
For the full breakdown of the system, testing and decisions, read the PSP Pasay Scholarships case study.
Send a signal
end of the-reason-it-works.md. next: psp.pasay-scholarships.md