You’re probably here because you’re searching for capstone project ideas and your title defense is closer than you’d like. Third year? Don’t worry, I got you. Been there.

I graduated with BS Information Systems and my capstone was an Alumni Management Information System. We may not have the same university, but the process is mostly the same everywhere, and so are the mistakes. I made a lot of them, so this post is the version of the advice I wish someone gave me before we picked a title.

Before you pick an idea, answer these four questions

A capstone is not a coding project. It’s a solution to a problem. Panels don’t fail you because your UI is ugly. They fail you because you can’t explain why your system needs to exist.

So before you fall in love with an idea, make sure you can answer these:

1. What problem are you solving? Not “they don’t have a system.” The actual pain. Someone is doing this by hand, in a notebook, three times a week, and it takes them two hours every time.
2. Who are your users? Be specific. Not “the school.” The registrar staff who encode requests, the students who follow up, the department head who signs off.
3. What data do you need? Where does it come from, who owns it, and will they actually give it to you. This one kills more capstones than bad code.
4. What manual process are you replacing? If nothing manual exists, there’s probably no problem, and you’re building something nobody asked for.

If you can answer those four clearly, you already have half of Chapter 1 written.

22 capstone project ideas for IT students

I grouped these by where the problem lives. Pick the one where you can actually talk to real users, because that’s the difference between a system you can defend and a system you made up in a group chat at 2am.

Campus and school

1. OJT and practicum monitoring system. Coordinators track student deployment, hours, and evaluation forms in spreadsheets and printed logs. Users: OJT coordinator, students, company supervisors. Data: student records, partner companies, daily time records, evaluation scores.
2. Document request and tracking system. Students line up at the registrar with no idea what stage their TOR request is in. Users: registrar staff, students, cashier. Data: request types, fees, processing stages, release dates.
3. Laboratory and equipment reservation system. Double booked rooms, borrowed equipment that never comes back. Users: faculty, lab custodian, students. Data: inventory, schedules, borrow and return logs.
4. Alumni management information system. This was mine. The school had no centralized record of its graduates, so every tracer study started from zero, usually through Facebook messages.
5. Student organization membership and event system. Membership fees, attendance, event registration, and officer turnover records that currently live in one person’s laptop.
6. Scholarship application and monitoring system. Applications on paper, grade requirements checked manually every semester, renewal deadlines missed.

Barangay and local government

7. Barangay resident information and clearance system. Records in logbooks, clearances typed one by one in Word. Users: barangay secretary, residents, captain. Data: household records, resident profiles, clearance and certificate history.
8. Health center patient record and immunization tracker. Midwives tracking immunization schedules on index cards and wall charts. Users: health workers, residents. Data: patient profiles, vaccine schedules, follow up dates.
9. Disaster preparedness and relief distribution system. Who lives in which zone, who needs assistance first, who already received relief goods. Users: barangay officials, responders.
10. Livelihood and business permit tracking. Small businesses renewing permits every year with no record of last year’s filing.

Small business

11. Inventory and sales system for a sari sari store or agri supply. The owner tracks stock by looking at the shelf and finds out something is out only when a customer asks for it. Users: owner, helper. Data: products, stock movement, sales, supplier records.
12. Booking system for a small service business. Resorts, salons, and equipment rentals that take bookings through Messenger and lose track of double bookings.
13. Order and delivery management for a home food business. Orders in one chat, payments in another, delivery schedule in someone’s head.
14. Repair or service job order tracking. Shops that accept units for repair and write the job order on carbon paper.

If you want the AI angle

Don’t bolt AI on just because it sounds impressive. The panel will ask why, and “because it’s trending” is not an answer. Use it where it replaces a judgment call someone is currently making by hand.

15. Document classification and auto routing. Incoming requests or complaints sorted by type and sent to the right office automatically.
16. FAQ chatbot trained on your school’s actual handbook. Enrollment, requirements, deadlines. The questions the registrar answers fifty times a day.
17. Resume and job matching for graduating students. Score student profiles against posted openings and rank the matches.
18. Demand forecasting for the inventory system. Predict reorder points from sales history so the owner stops guessing.

If you want the IOT angle

Same rule. The sensor has to solve something. A sensor that just displays a number on a dashboard is a science fair project, not a capstone.

19. Water level and quality monitoring for a fishpond or small farm. Alerts when readings go past safe range.
20. RFID or QR attendance at campus gates with parent notification. Entry and exit logged, SMS or push notification sent home.
21. Temperature and humidity monitoring for storage rooms or poultry houses. Logged over time, with alerts.
22. Soil moisture monitoring with automated irrigation. Small farm, real crop, real farmer you can interview.

My capstone, and what I’d do differently

Mine was an Alumni Management Information System. The problem was real. The school had no centralized system for its alumni, and that’s genuinely how we came up with the idea. There was a problem, and it needed a solution. That’s the whole origin story, and that’s all it has to be.

Tech stack: PHP, MySQL, XAMPP, Bootstrap, Hostinger, and spaghetti code. I’m a frontend developer now and I still think about that codebase sometimes.

Here’s what I’d change:

• Plan your database schema first, and properly. Everything downstream breaks if this is wrong. This is the single biggest thing on this list.
• Do the flowchart before you write code. It takes an afternoon and saves you a month.
• Prioritize backend. I’m a frontend developer and I’m still telling you this. For a project like this, functionality is what gets graded. A beautiful page that doesn’t save anything will not survive defense.
• One feature at a time. Finish it, then improve it. Don’t start five things and have none of them working the week before final defense.
• Don’t over engineer it. Nobody is asking for microservices.
• Don’t add features without a reason. Every feature needs a justification you can say out loud when a panelist asks “why is this here.”
• Use a stack you’re comfortable with, not the one that sounds impressive. You have two semesters. That is not enough time to learn a new framework and build a system in it.
• Use modern frameworks, though. Laravel, Django, whatever your group can actually handle. You’ll learn more and the code will still make sense to you a year later.

And for the love of God, stop using XAMPP if you can help it.

The process, roughly

At my school there were four checkpoints: Thesis and Project Proposal, Project Proposal, Pre Defense, and Final Defense.

First semester was the manuscript, Chapters 1 and 2. Second semester was development plus Chapters 3 to 5, including the surveys and the tally. We were two people per group.

One small thing that saved us: take photos of everything, especially the surveys. Documentation is part of your grade and you will absolutely not remember to do it later.

Pick the problem first

The idea comes second. If you can name a specific person who is currently doing something by hand and would thank you for your system, you have a capstone. If you can’t, you have a title.

Take note, this is all my personal experience, not a rulebook. Your school’s process might be different. The part about the database schema is not, though.