Making educational support easier to find, apply for, and manage
Institut Teknologi Bandung (ITB) is one of Indonesia’s leading state universities, with ambitions to strengthen its academic influence in Indonesia and across Asia. Its mission combines academic excellence with a commitment to social and human values—an ambition that includes helping qualified students access and complete their education.
Financial aid and scholarship management was an important part of that commitment. ITB’s existing SIX system allowed students to apply independently, but the wider process still involved manual steps, disconnected systems, and separate departmental workflows. Students could face uncertainty about where to apply, how to track their application, and what happened after submission.
Suitmedia partnered with ITB to develop a centralized financial aid platform. The system was designed as a “one-door” solution for scholarships, tuition assistance, fee waivers, and employment opportunities. It connected application, review, monitoring, selection, and aid management into a more coordinated process.
Financial support existed, but the path to it was fragmented
1. Administrative complexity was affecting access to education
Financial aid is not a secondary service for students who depend on it. It can determine whether they are able to enroll, continue their studies, or manage tuition obligations.
ITB already had a way for students to apply for scholarships through SIX. However, the broader process still involved manual steps and limited integration. Students could submit an application without having a clear view of what happened next.
When a process is difficult to understand, students may miss deadlines, submit incomplete information, or spend time contacting different departments for updates. Administrative friction can become an unintended barrier to educational access.
2. Scholarship programs were managed in separate systems
Different academic units, including undergraduate and postgraduate scholarship areas, operated independently with standalone systems.
This made it harder for ITB to build a complete view of its financial aid programs. Data could be distributed across departments, making it difficult to compare applications, coordinate decisions, or understand the overall allocation of support.
For students, separate systems created an inconsistent experience. The process for one form of assistance might differ from another, even when the student’s underlying need was similar.
3. Students needed one clear place to begin
A student seeking financial assistance should not need to know which department manages each scholarship, waiver, or work opportunity.
They need a clear starting point where they can understand what support exists, which option may suit their situation, and how to apply.
ITB wanted to create one entry point for all tuition assistance applications. This would reduce the burden of navigating institutional structures and make support more accessible to students with different needs.
4. Application status was difficult to manage without integration
A financial aid application moves through several stages: discovery, submission, review, selection, approval, and disbursement.
When these stages are managed across disconnected systems, students may not know whether their application is complete, under review, approved, or awaiting further action. Administrators also need to spend more time reconciling records and responding to status questions.
A more connected system could make progress visible to the people who need it while reducing repeated administrative work.
5. ITB needed to manage more than scholarships
The university wanted the system to support several forms of student assistance, including scholarships, tuition fee waivers, and employment opportunities.
This broader scope was important because financial need does not always have one solution. A student may benefit from direct financial support, reduced fees, or an opportunity to work while studying.
The platform needed to accommodate these different programs without forcing students to search across separate channels.
6. Administrators needed better coordination and oversight
ITB staff needed a way to publish assistance information, manage applications, track recipients, and evaluate program performance.
Without a shared system, each team could develop its own process and reporting method. This makes university-wide planning difficult and limits the ability to see whether support is reaching students efficiently.
A centralized platform could provide a common operational view while allowing different programs to retain their own requirements.
7. The system needed to connect with existing university technology
ITB already relied on several systems, including SIX, SIBPP, SISPRAN, HRIS, and Oracle.
The new financial aid platform had to work with this environment rather than create another isolated data store. Integration was necessary to reduce repeated data entry, improve consistency, and connect student, financial, academic, and employment information where appropriate.
This was a significant technical and governance challenge. The platform needed to connect systems while protecting data quality, access, and accountability.
8. The university needed a solution that could grow
Financial aid programs change. New scholarships may be introduced, eligibility rules may evolve, and monitoring needs may become more sophisticated.
ITB needed a system that could support these changes without requiring a complete rebuild every time a new initiative was launched.
The project therefore needed to create both an immediate improvement and a durable foundation for future student support.
Designing one financial aid journey from application to support
1. Establish a one-door model
Suitmedia designed the platform as a centralized entry and exit point for tuition assistance applications.
Students could begin from one place, explore available programs, submit applications, and receive information about outcomes. Administrators could manage the process through the same broader system.
The one-door model reduced uncertainty. Students no longer needed to decide which separate system or department to approach before understanding the available support.
2. Make assistance programs easier to discover
The platform was designed to communicate information about scholarships, tuition assistance, fee waivers, and employment opportunities.
This created a more complete picture of the help available through ITB. Students could compare possible forms of support instead of learning about programs only through separate announcements or personal networks.
Better discoverability also supports fairness. When information is centralized and visible, access depends less on whether a student happens to know the right office or person.
3. Design around student tasks
The core student journey included:
- Finding relevant assistance.
- Understanding eligibility and requirements.
- Registering or submitting an application.
- Tracking status.
- Reviewing selection results.
- Understanding the next step toward receiving support.
This task-based approach helped ensure the platform served students rather than mirroring the university’s internal structure.
The system needed to make each stage understandable. A student should know what to do now, what will happen next, and where to find an update.
4. Deliver the system in two phases
The project was divided into two phases to create a controlled path to launch.
The first phase focused on core functions: publishing information about assistance programs, enabling student registration, and announcing selection results. These features addressed the most urgent access and communication needs.
The second phase added supporting capabilities, including scholarship monitoring, recipient status updates, and analytics for program evaluation.
This sequencing reduced delivery risk. ITB could establish the essential student journey first, then develop deeper management and evaluation capabilities on top of it.
5. Use a monitoring dashboard for administrators
The monitoring dashboard gave ITB a clearer view of scholarship activity and recipient status.
A dashboard can turn dispersed records into a more useful management view. Administrators could see what was happening across programs instead of relying on separate reports from individual departments.
This supported faster follow-up and more informed planning. The university could identify where applications or decisions required attention and understand how programs were progressing.
6. Make recipient status more visible
Status information was included to help users understand where applications or awards stood.
For students, this reduced uncertainty. They could receive clearer information about the progress or outcome of their application rather than repeatedly contacting administrators.
For ITB, shared status information reduced the burden of answering routine questions and created a more consistent communication process.
7. Add analytics for program evaluation
The platform included analytics to support evaluation of scholarship and assistance programs.
Data could help ITB understand application volume, selection patterns, recipient distribution, and program activity. This information could support future decisions about planning, communication, and resource allocation.
Analytics turned the system into more than an administrative tool. It created a basis for learning whether financial aid programs were operating as intended.
8. Integrate with five existing systems
The financial aid platform was designed to integrate with SIX, SIBPP, SISPRAN, HRIS, and Oracle.
Each system could contribute information relevant to the student assistance process. Connecting them helped reduce duplication and created a more reliable flow of data.
Integration also improved the potential for a complete view. ITB could connect academic, student, financial, and employment information more effectively than if each program remained isolated.
9. Use integration to reduce manual work
Without system integration, staff may need to re-enter information, compare records, or request the same data from multiple departments.
The integrated platform reduced these repeated tasks. Information could move through the process more consistently, while administrators spent more time reviewing and supporting applications.
This created operational efficiency without removing the need for human judgment. Staff could focus on eligibility, decisions, and student support rather than clerical reconciliation.
10. Build the system on N-Tier architecture
The platform used an N-Tier architecture that separated the frontend, backend, and database layers.
This structure made the system easier to manage and improve over time. Changes to one layer could be handled with less risk of disrupting the entire application.
The architecture also supported better control of responsibilities. User interface design, business logic, and data storage could be developed and maintained more systematically.
11. Design for future redevelopment
A layered architecture created flexibility for future changes in policy, workflow, and user experience.
ITB could improve the interface or add new features without necessarily rebuilding the underlying data and business logic from scratch.
This was important because financial aid processes may evolve as the university introduces new forms of support or changes eligibility rules.
12. Protect information through structured access
A financial aid system handles sensitive student and financial information. Access needed to be managed according to the responsibilities of students, administrators, reviewers, and other stakeholders.
A centralized platform made it easier to establish consistent access rules than a collection of departmental systems and manual documents.
Security and privacy were therefore part of the system’s design responsibility, not separate technical concerns added later.
13. Use usability testing to improve the real experience
The platform needed to be tested with the people expected to use it.
Students could reveal whether program information, application steps, and status updates were understandable. Administrators could identify whether dashboards and workflows supported their daily work.
Testing helped ITB avoid creating a system that was technically integrated but difficult to use. It connected system success with user behavior.
14. Train ITB staff for long-term ownership
Training was important because the platform needed to remain useful after launch.
ITB staff had to understand how to manage programs, update information, monitor applications, and use analytics for evaluation.
Internal capability reduced dependence on external support for routine operations and helped preserve the quality of the student experience over time.
15. Make access to aid more transparent
A one-door platform could show students what assistance was available and how each process worked.
Transparency reduced the need for students to rely on informal information. It also helped create more consistent expectations about requirements, selection, and outcomes.
This supported ITB’s wider commitment to social and human values. Accessible education requires not only funding, but also clear pathways to that funding.
16. Create a feedback loop between support and planning
The platform’s data could help ITB understand how students use financial aid programs and where the process still creates difficulty.
This created a path for continuous improvement. The university could refine communication, timelines, program design, and administrative workflows based on evidence.
The system therefore supported both current applicants and future planning.
ITB gained a more coordinated way to support students
1. The university moved from isolated systems toward one integrated platform
Previously, undergraduate and postgraduate scholarship areas operated through standalone systems.
The new platform connected financial aid management through a more unified structure. This improved coordination between academic units and created a more complete view of assistance activity.
The result was a stronger foundation for university-wide scholarship planning and execution.
2. Students gained one place to explore support options
The one-door model made it easier for students to learn about scholarships, tuition waivers, and employment opportunities.
They no longer needed to understand which department managed each program before beginning their search.
This improved accessibility and reduced the risk that students would miss support simply because information was fragmented.
3. The application journey became more consistent
Students could register, apply, and receive selection information through a more structured process.
Consistency reduced confusion and made it easier for students to understand what was expected of them.
It also helped ITB standardize how different assistance programs communicated with applicants.
4. Administrators gained better visibility
Dashboards, status updates, and integrated information helped administrators monitor applications and recipients more effectively.
This improved coordination across different units and reduced the effort required to assemble a complete picture from separate systems.
The university could respond more quickly when an application, decision, or recipient record required attention.
5. Manual coordination and data handling were reduced
Integration with SIX, SIBPP, SISPRAN, HRIS, and Oracle helped reduce repeated data entry and disconnected record keeping.
This improved operational efficiency and reduced the risk of discrepancies between departments.
Staff could spend more time on reviewing needs and managing programs, rather than reconciling information manually.
6. ITB improved its ability to evaluate financial aid programs
Analytics provided a stronger basis for evaluating program performance and planning future initiatives.
ITB could use the data to understand demand, recipient activity, and areas where the process needed improvement.
This made financial aid management more evidence-based. Decisions could be informed by patterns across programs rather than isolated reports.
7. The platform improved transparency for students
Students gained clearer access to information about programs, application progress, and results.
Transparency can reduce anxiety during a financially important process. Students are better able to plan when they understand what stage their application has reached.
The improvement also strengthens trust in the university’s administration of support.
8. The system supported additional forms of student assistance
By including employment opportunities alongside scholarships and fee waivers, the platform reflected the different ways ITB could help students manage educational costs.
This gave students more options and helped the university present financial aid as a broader support ecosystem.
The approach recognized that accessible education may require several forms of assistance rather than one standard program.
9. The architecture improved scalability
The N-Tier architecture created a stronger foundation for future redevelopment and expansion.
ITB could add programs, refine workflows, and improve the user experience without treating every change as a complete system replacement.
This protected the long-term value of the project and supported future changes in student support policy.
10. ITB gained greater internal ownership
Training enabled ITB staff to manage the new platform more effectively.
This improved sustainability. The university could continue operating and improving the system with greater independence.
Internal ownership also strengthened accountability. ITB teams could maintain the accuracy and relevance of the information students relied on.
11. The university strengthened coordination across academic units
The integrated system helped connect teams that had previously managed scholarship processes separately.
This created more consistent planning and reduced the risk that important information would remain confined to one department.
Better coordination supported a more unified approach to student support across the institution.
12. The platform aligned financial aid with ITB’s educational mission
The project helped ITB make financial support easier to access, understand, and manage.
This directly supported the university’s commitment to an accessible and supportive academic environment. The technology was valuable because it helped reduce an administrative barrier that could affect whether students remained able to study.
13. The project received strong client approval
ITB described Suitmedia’s approach and execution as efficient, well planned, and impactful.
The university highlighted the benefits of improved scholarship planning and management, as well as Suitmedia’s experience in academic system development.
This qualitative feedback supports the operational value of the project. The system addressed a real institutional need and was delivered through a process ITB considered professional and effective.
14. The platform created a foundation for future initiatives
The integrated system can support future scholarships, tuition assistance programs, employment opportunities, and student support services.
The university now has a clearer structure for adding and managing these initiatives.
The second-order effect is greater institutional readiness. ITB can respond to changing student needs without returning to a fragmented administrative model.
The deeper lesson: financial aid access depends on administrative design
1. A scholarship is only accessible when the process is accessible
Funding may exist, but students can still struggle to benefit if the application process is confusing, fragmented, or difficult to track.
Digital design can reduce that hidden barrier by making information and next steps clearer.
2. One-door systems improve fairness
When all students can begin from the same platform, access becomes less dependent on informal networks or knowledge of departmental structures.
Centralization can make opportunities more visible and reduce the risk that eligible students are excluded by information gaps.
3. Integration turns administration into a coordinated service
Connecting student, academic, financial, and employment systems allows the university to manage support more comprehensively.
The result is better coordination, but also a clearer experience for students who may need more than one form of assistance.
4. Transparency builds trust during uncertain periods
Students applying for aid may already be under financial pressure. Clear status updates and predictable communication can reduce anxiety and improve confidence in the institution.
Transparency is therefore a student support function, not merely a reporting benefit.
5. Phased delivery can reduce institutional risk
Launching core functions first allows the university to address immediate access problems while creating room for more advanced monitoring and analytics later.
This approach supports learning and adoption. The system can grow based on real use rather than trying to solve every possible problem before launch.
6. Architecture should support policy change
Financial aid programs evolve as budgets, requirements, and student needs change.
A flexible architecture allows ITB to adapt the platform without repeatedly rebuilding its foundation. Technical design becomes a safeguard for institutional agility.
7. Analytics can improve the distribution of support
A centralized system creates information about demand, program reach, decisions, and recipient status.
Used responsibly, this data can help ITB understand whether support is reaching the students and situations where it is most needed.
8. Internal ownership sustains digital services
A platform cannot remain effective if only an external vendor knows how to operate it.
Training and clear management processes allow the university to maintain accuracy, update programs, and respond to student needs after implementation.
Strategic Insights for the C-Suite
- Treat financial aid access as a service design problem. Funding does not create access when students face fragmented applications, unclear status, or inconsistent communication. The process around the aid matters as much as the aid itself.
- Create one visible entry point for student support. A central platform reduces dependence on informal knowledge and helps ensure that eligible students can discover the assistance available to them.
- Integrate systems to improve both coordination and fairness. Connecting academic, financial, HR, and student records can reduce administrative duplication while creating a more complete view of each support process.
- Make status and outcomes transparent. Students under financial pressure need predictable information about their applications. Clear updates strengthen trust and reduce avoidable inquiries.
- Build aid platforms for policy and program change. Scholarships, waivers, and work opportunities will evolve. Modular architecture, analytics, and trained internal teams help universities respond without repeatedly rebuilding the system.
