
01
The short answer
ScholarDesk is an online demo app for tracking scholarships after they have been awarded: payment requests, session reports, scholarship recipient files and a payment register. Open the preview without an account, then compare what is there with how your program works. Your organization’s rules, forms and steps still need to be defined by adapting the app.
02
What does the ScholarDesk demo app contain?
ScholarDesk is an online app model. To assess whether it could be a useful starting point, review the sections and information shown in the live preview. The app covers the tracking of requests after scholarships have been awarded.
- Payment requests
- The app provides for four request types: tuition, living expenses, study or internship stays, and emergency assistance. Each type includes an amount, a due date, an invoice and the account to be paid.
- Review and payment
- Requests move through four stages: “Submitted,” “Under review,” “Approved” and “Paid.” The office can approve, return or reject a request with a note, then record the payment, its date and a note.
- Scholarship recipient file
- The file brings together the person’s studies, contact information, bank account and payment ledger. These items are grouped in one file.
- Session report
- Each request includes a session report with the average, credits, transcript, well-being information and reflections. Session information is therefore presented with the payment request.
- Universities and sessions
- Each university has its own page, session calendar and programs. The periods when requests open and close follow the sessions.
- Register and alerts
- The register shows totals by stage and university. Alerts cover approaching due dates, low averages and emergency requests. The app also includes Excel and CSV exports.
Review the ScholarDesk live preview and compare its sections with your process: expense types, documents to review, session information and payment tracking. Note what matches your needs, what would require adaptation, and which information or decisions your program needs to handle differently.
03
What is not included in the tracking shown?
The demo shows scholarship tracking after awards have been made. If your organization needs to receive applications, assess files and make award decisions in the same app, check the preview to see whether those steps are included or would need to be added by adapting the model.
The office can record a payment, its date and a note in ScholarDesk. This documents the tracking of a request and payment; it is not the same as carrying out a banking transaction. Your organization must keep its existing payment process and specify when information is recorded in the app.
The preview helps you examine the model, but it does not determine your program’s rules or the choices to make for your production environment. Before deployment, define who can view bank details and files, what information is necessary, how it will be retained and who will handle support requests. These matters are part of adaptation and implementation.
04
What should you adapt for your program?
Start by comparing the model with your written rules. Identifying gaps is generally more useful than asking teams to change their work to fit an existing form. The items below are examples of what we add when adapting the app; they are not necessarily configured to match your current rules in the demo.
- Program criteria
- Specify which expenses are eligible, what supporting documents are required, when applications can be submitted and what rules determine whether a request can be reviewed. Describe exceptional cases that require verification.
- Decision process
- Identify who reviews a request, who can approve it and who handles corrections. If you need multiple roles or approval levels, document them before defining the stages to add or adapt.
- Reports and alerts
- Decide which session information is useful for your tracking and what thresholds should trigger a review. An alert is a signal for the responsible people to examine, not an automatic decision about a scholarship recipient.
- Languages and terminology
- Have the terms, instructions and communications adapted for your audience reviewed. This is particularly important if the program serves multiple countries, languages or institutions.
- Data and access
- Determine what information is truly needed, who needs to view it and how existing files will be transferred. Bank accounts, transcripts and well-being information require particular care in these decisions.
To prepare for adaptation, describe a typical process from start to finish: a request, its supporting documents, the decision to be made and the recording of the payment. Have someone from administration and someone representing scholarship recipients review the description. This review can reveal ambiguous fields, rules that are difficult to apply or steps that need clarification before the app is configured.
05
How do you choose between a model, subscription software and a custom app?
The right choice depends mainly on the gap between your process and what already exists, as well as your team’s ability to operate and maintain the tool. A model like ScholarDesk provides an app foundation you can examine before deciding. It does not mean your program is already configured or that all your requirements are covered.
- Subscription software
- This option can work if a specialized product already covers your needs, its configuration options suit you and you prefer a service managed by its publisher. Before choosing, check the features, recurring costs, data export and terms that apply to your organization.
- Theme template
- A theme may work for styling a website or information pages. Do not confuse it with an app that manages a database, accounts and a payment tracking process.
- App model
- This is worth considering if the information and main steps in ScholarDesk resemble your work. There are three ways to get it: buy the source code, have TECHMA adapt the model, or have TECHMA build and manage the app.
- App built from scratch
- A custom app may be a better fit if your process is very different, you have specific requirements or no model is close enough. A custom app may also be worth considering if your process is very different or no model is close enough. There is no need to replace software that already meets your needs.
A model can also be a starting point rather than a solution to adopt as-is. With ScholarDesk, the live preview lets you judge whether the way requests, reports and payments are organized is close to your process. You can then compare buying the source code, having it adapted, or having TECHMA build and manage an app. No price is published in this article.
06
How do you organize a deployment step by step?
- 1Open the ScholarDesk live preview without creating an account. Review the information shown in the register, payment requests, files and session reports. Compare these sections with the tasks your program needs to support.
- 2Map your current process. Note the people involved, the documents received, decisions, due dates and tools used. Separate essential rules from work habits that could be simplified.
- 3Make a list of the gaps. Distinguish the items shown in the demo from those that need adaptation, such as an application stage or approval rules specific to your program.
- 4Define access and data needs. Choose the necessary fields, roles, retention rules and method for transferring existing files. Have the people responsible for your organization’s privacy and security review this plan.
- 5Prepare to check the adapted version before it goes live. Define the scenarios to review, including complete or incomplete requests, returns for correction and recording a payment that has already been made. Use appropriate test data and avoid real personal information until the handling conditions have been established.
- 6Prepare the launch and support. Explain to scholarship recipients how to submit a request under the chosen process and to teams how to review it. Plan a way to report problems and a way to correct instructions if anything remains unclear.
This process helps you assess the model and clarify what your organization needs to add or decide. The live preview lets you examine the app; configuring your program and preparing to put it into service are separate steps. We can then discuss the three ways to get ScholarDesk: buy the source code, have TECHMA adapt the model, or have TECHMA build and manage the app.
Sources
The pages the facts in this guide come from. Each link was checked when the guide was written.

