This guide walks you through everything you need to do to review the JTG Bursary Platform and give your sign-off that it is ready for use.
You are not here to test code. You are here to confirm that the system works the way you need it to work — from the perspective of the staff who will use it every day, and the applicants who will apply through it.
| Account | Password | When you use it | |
|---|---|---|---|
| Tshidi — Super Admin | superadmin@jtg.org.za | password123 | Phase 1 account check, Phase 4 audit review, Phase 5 sign-off |
| Gomolemo — Programme Admin | programmeadmin@jtg.org.za | password123 | All programme setup and management — your main account |
| Learner — Thabo Mokoena | thabo@example.com | password123 | Role tour: learner applying for a bursary |
| Learner — Lerato Dlamini | lerato@example.com | password123 | Role tour: waitlisted learner |
| Reviewer — John Reviewer | reviewer@jtg.org.za | password123 | Role tour: scoring an application |
| Verif. Officer — Sarah Verifier | verifier@jtg.org.za | password123 | Role tour: verifying documents |
| Sponsor — ABC Corporation | sponsor@jtg.org.za | password123 | Role tour: sponsor dashboard |
superadmin@jtg.org.zaPassword:password123As department head and super admin, your focus is on confirming the system is set up correctly and giving final sign-off. You are not expected to run the day-to-day testing — Gomolemo handles that. Your two hands-on moments are Phase 1 (confirming all accounts are ready) and Phase 4 (reviewing the audit trail).
superadmin@jtg.org.zaPassword:password123superadmin@jtg.org.zaPassword:password123programmeadmin@jtg.org.zaPassword:password123As bursary administrator, you are running the day-to-day workflow — the same work you will do every time a new bursary cycle opens after go-live. This is the most important part of the review. If anything in the workflow feels wrong, unclear, or more complicated than it should be, note it.
reviewer@jtg.org.za).thabo@example.comPassword:password123lerato@example.comPassword:password123verifier@jtg.org.zaPassword:password123reviewer@jtg.org.zaPassword:password123sponsor@jtg.org.zaPassword:password123Tick each item as you confirm it during testing. All items must be ticked (or marked N/A with a reason) before sign-off can be given. Use the Notes column for any observations.
| ✓ | The system correctly… | Notes |
|---|---|---|
| Sends an email verification link when a new account is registered. | ||
| Requires email verification before a new account can be used. | ||
| Assigns each user to the correct part of the system based on their role. | ||
| Prevents a user from accessing a portal they are not supposed to see. |
| ✓ | The system correctly… | Notes |
|---|---|---|
| Allows a programme to be created with a name, deadline, fund amount, and eligibility criteria. | ||
| Shows the restricted programme only to eligible learners — ineligible learners cannot see or apply. | ||
| Shows a universal (open) programme to all learners regardless of their profile. | ||
| Saves the application form with conditional field logic (a field appearing only when a specific answer is chosen). | ||
| Allows a scoring rubric to be created with weighted criteria summing to 100%. | ||
| Automatically assigns the correct reviewer when an application reaches "Approved for review" status. | ||
| Saves a contract template with correctly labelled merge fields. |
| ✓ | The system correctly… | Notes |
|---|---|---|
| Allows a learner to save an application as a draft and resume it — including after logging out and back in. | ||
| Sends a confirmation email to the learner when their application is submitted. | ||
| Allows a learner to upload all three required documents. | ||
| Shows the learner clearly which documents have been submitted and which are outstanding. | ||
| Sends the learner a notification when their application status changes. |
| ✓ | The system correctly… | Notes |
|---|---|---|
| Shows the verification officer a queue of applications waiting for document review. | ||
| Allows a document to be marked as verified. | ||
| Allows a document to be rejected with a written reason that the learner can see. | ||
| Automatically moves an application to "Under review" once all three documents are verified, without the admin manually triggering it. |
| ✓ | The system correctly… | Notes |
|---|---|---|
| Requires a conflict of interest declaration before a reviewer can score an application. | ||
| Calculates the weighted score automatically as the reviewer enters scores. | ||
| Prevents a reviewer from changing their scores after submission. | ||
| Ranks shortlisted applications by their weighted score. | ||
| Sends the learner a notification when they receive an award offer. | ||
| Generates the offer letter PDF with the learner's real details — no placeholder text. | ||
| Allows a learner to accept an award and generates a contract with correct details. | ||
| Automatically promotes the next person from the waitlist when an award is declined. |
| ✓ | The system correctly… | Notes |
|---|---|---|
| Generates a signed contract with the learner's name, amount, and programme name correctly filled in. | ||
| Records the date and time when a contract is signed. | ||
| Allows the admin to search for a contract by learner name in the contract repository. | ||
| Processes a data access request (POPIA) and allows the data export to be downloaded. | ||
| Sends deadline reminder emails without sending duplicates to the same recipient. | ||
| Records all significant actions in the audit log with the correct user and timestamp. |
Use this to note anything that doesn't look right. You don't need to be technical — just describe what you were doing and what you saw. The developer will review everything logged here.
Must fix before go-live — something is wrong or showing incorrect information · Should improve — it works but could be clearer · Minor — cosmetic only (spelling, layout)
| # | Phase | What I was doing | What happened / what looked wrong | How serious? | Status |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 | |||||
| 6 | |||||
| 7 | |||||
| 8 | |||||
| 9 | |||||
| 10 | |||||
| 11 | |||||
| 12 | |||||
| 13 | |||||
| 14 | |||||
| 15 |
Answer these questions after completing the walkthrough and role tours.
| Question | Your answer |
|---|---|
| Does the application journey feel clear and straightforward from the learner's perspective? | |
| Is the programme admin workflow efficient enough for daily use by the bursary team? | |
| Are emails and notifications sending correctly and worded appropriately? | |
| Is there anything in the system that would confuse a staff member or applicant without training? | |
| Any features you expected to see that are missing or not working as expected? |
Complete this when all must-fix issues are resolved and all checklist items are ticked.
| System | JTG Bursary Platform — Milestone 1 |
| UAT completed | |
| Outstanding issues (if any) |