Internship Management System

Problem

From application to final decision, a student's internship passes through four parties: the student, the internship committee, the KPTO office and the host company. When applications, insurance paperwork, daily logs and company approvals are spread across email, paper and other channels, it becomes hard to tell whose desk a task is waiting on.

Approach

I split the process into four roles and designed screens where each role sees only its own work. Application, insurance, daily tracking, company approval and the committee decision run as linked stages; the next stage does not open until the previous one is complete.

Access is checked not only by role but also by record ownership: a company can only see the logbooks of its own interns. Accounts are activated through time-limited, single-use email invitations. I developed the application with feedback from advisors and user testing, deployed it to Render with Docker, and keep the database and documents on Supabase.

Highlights

• Term setup and application management for Internship 1 and Internship 2
• KPTO reviews SPAS records and tracks insurance entries from a single screen
• Daily attendance logs and internship reports downloadable as Word documents
• Companies approve the internship logbook or request corrections for selected days
• Document-attached correspondence between companies and KPTO, plus in-app notifications
• Submission of the paper evaluation form and the committee's final pass decision