The SAG In-Scheme Monitoring Portal is a working front-end trial (Version 2.0) of a monitoring tool for a government sports scheme. It is delivered as a standalone HTML file (SAG_InScheme_Monitoring_Portal_Trial_v2.html) that Chirag Chaudhary and his reviewers download and open directly in Google Chrome or Microsoft Edge on a laptop, desktop, or mobile browser. The trial exists so that stakeholders can test the screens, roles, data-entry modules, reporting fields, and dashboard before the product is finalized as Version 3 for actual software development.
The audience is the scheme's operating staff: Project Managers and Assistant Managers who monitor trainers, attendance and medals; Junior/Senior MIS staff who enter data and produce reports; Sports Analysts who review attendance and medal records; Team Managers who review trainer and player attendance; and Trainers who record their own daily attendance, school PE and after-school reports, individual player attendance, and medal records.
The trial is explicitly not a live production portal. Sample entries are saved in the same browser using local storage. GPS verification, live selfie capture, secure login, a server database, and real photo uploads are not part of this version and remain backend work for Version 3. Role switching is for interface testing only and is not production security.
The current product is a single standalone HTML trial portal with four first-party surfaces: an anonymous Landing entry that explains the trial and offers the download, a Dashboard that shows the unique trainer name count and hosts the left-side Login Role dropdown, a Data Entry area where sample data is entered across the trainer, attendance, school PE, after-school, player and medal modules, and a Reports area where daily overall and monthly reports are generated and exported as Excel-compatible CSV or printed/saved as PDF.
All six accepted roles — Project Manager, Assistant Manager, Junior/Senior MIS, Sports Analyst, Team Manager and Trainer — operate the same trial file. The Login Role dropdown in the left rail switches the interface context for testing; it does not authenticate or restrict access. Sample entries persist in the browser's local storage so a reviewer can enter data, switch roles, and see the same records reflected in the dashboard and reports on the same device.
The provisioned scaffold (a shared FastAPI backend, a MariaDB database, and a React frontend) is infrastructure inventory only. It does not add product behavior, authentication, or domain persistence to this trial; the accepted trial behavior is the standalone HTML file with browser local storage.
Removed from scope
The trial is a downloadable, self-contained front-end artifact. There is no hosted application, no account, and no server round-trip: the reviewer downloads the HTML file, opens it locally in Chrome or Edge, and works entirely within that browser. Data entered during a review session is stored in that browser's local storage on that device, so it survives a page reload in the same browser but is not shared across devices or browsers.
Access is therefore anonymous and local by design. The Landing surface is the public entry that explains the trial and provides the download; the Dashboard, Data Entry and Reports surfaces are reached inside the opened file. The Login Role dropdown is an interface-testing control, not an access control — every role sees the same trial modules, and no role-based permission or visibility restriction is part of this version.
The boundary between current and future is explicit. Everything in this document describes the Version 2.0 trial. GPS verification, live selfie capture, secure login, a server database, and real photo uploads are future backend work for Version 3 and are not current requirements, pages, or acceptance criteria. The provisioned FastAPI/MariaDB/React scaffold is available for that future development but is not exercised by the trial's accepted behavior.
SAG_InScheme_Monitoring_Portal_Trial_v2.html, and a plain statement of the trial limitations (front-end only, local-storage sample entries, backend items pending).FR-1 — Responsive standalone trial file. As a reviewer, I should open the trial portal as a standalone HTML file in Chrome or Edge on laptop, desktop or mobile, so that I can evaluate it on the devices I use. (explicit) The file SAG_InScheme_Monitoring_Portal_Trial_v2.html is downloaded and opened directly; the layout adapts to laptop, desktop and mobile browser widths. Observable acceptance: the file opens and every module is usable at laptop, desktop and phone widths. Failure/recovery: if the file does not open, the reviewer re-downloads it and opens it in Chrome or Edge.
FR-2 — Download the trial from the Landing surface. As a reviewer, I should download Trial Portal v2.0 from the Landing surface, so that I have the file to open locally. (explicit) The Landing surface presents the download control and the "How to test" steps. Observable acceptance: activating the download saves the standalone HTML file. Failure/recovery: a blocked or failed download is retried from the same control.
FR-3 — Change Login Role from the left-side dropdown. As a reviewer, I should change the Login Role from the left-side dropdown, so that I can test each role's interface. (explicit) The dropdown lists Project Manager, Assistant Manager, Junior/Senior MIS, Sports Analyst, Team Manager and Trainer. Observable acceptance: selecting a role updates the active role shown in the left rail and the module interface context. This is interface testing only and grants no security or permission behavior.
FR-4 — Unique Trainer Name Count. As a Project Manager, I should see the unique trainer name count on the Dashboard, so that I know how many distinct trainers are recorded. (explicit) The count reflects distinct trainer names in stored sample data. Observable acceptance: adding a trainer with a new name increments the count; a duplicate name does not. Empty state: zero with a prompt to enter data.
FR-5 — Project Manager and Assistant Manager roles. As a Project Manager or Assistant Manager, I should operate the portal under my role, so that I can monitor trainers, attendance and medal records and produce reports. (explicit) Both roles are selectable in the Login Role dropdown and can reach the Dashboard, Data Entry and Reports surfaces. Observable acceptance: the role appears in the dropdown and the active role is shown.
FR-6 — Junior/Senior MIS, Sports Analyst, Team Manager and Trainer roles. As a Junior/Senior MIS, Sports Analyst, Team Manager or Trainer, I should operate the portal under my role, so that I can perform my part of the monitoring work. (explicit) All four are selectable in the Login Role dropdown. Observable acceptance: each role appears in the dropdown and the active role is shown.
FR-7 — Trainer daily attendance. As a Trainer, I should record my daily attendance, so that the day's attendance is captured in the portal. (explicit) The Trainer enters a daily attendance entry in Data Entry. Observable acceptance: the saved entry appears in the trainer attendance records and is available to reports. Failure/recovery: an incomplete entry is rejected with a visible message and the input is retained.
FR-8 — School PE and After-School reports. As a Trainer, I should record school PE and after-school reports, so that session activity is captured. (explicit) The Trainer enters school PE report entries and after-school report entries in Data Entry. Observable acceptance: saved entries appear in their respective module lists and are available to reports.
FR-9 — Individual player attendance. As a Trainer, I should record individual player attendance, so that each player's attendance is tracked. (explicit) The Trainer enters per-player attendance in Data Entry. Observable acceptance: saved entries appear in the player attendance records and are available to reports.
FR-10 — KMK, SGFI, Association and Federation medal records. As a Trainer, I should record KMK, SGFI, Association and Federation medal records, so that medal outcomes are captured against the correct medal body. (explicit) Each medal record is associated with one of the four medal bodies. Observable acceptance: the saved record shows its medal body and appears in the medal records available to reports.
FR-11 — Daily Overall and Monthly report generation. As a Project Manager, Assistant Manager, Junior/Senior MIS, Sports Analyst, Team Manager or Trainer, I should generate a Daily Overall report and a Monthly report, so that I can review the recorded data for the day or month. (explicit) The Reports surface offers both report types and builds output from stored sample data. Observable acceptance: the selected report renders for the selected period. Empty state: a notice when no data exists for the period.
FR-12 — CSV export in Excel-compatible format. As a reviewer, I should download report data as a CSV file in Excel-compatible format, so that I can open it in Excel. (explicit) The Reports surface provides a CSV export control. Observable acceptance: the downloaded file opens in Excel with the report data. Failure/recovery: a failed export shows an error and can be retried.
FR-13 — Print/PDF option. As a reviewer, I should use a print/PDF option on a report, so that I can produce a printable or PDF copy. (explicit) The Reports surface provides a print/PDF control. Observable acceptance: the browser print dialog opens with the report and can produce a PDF.
FR-14 — Sample entries saved in the same browser using local storage. As a reviewer, I should have my sample entries saved in the same browser, so that my test data persists across reloads on that device. (explicit) Entries are written to browser local storage. Observable acceptance: after a reload in the same browser, saved entries remain. Failure/recovery: if local storage is unavailable or full, the failure is shown and the reviewer frees space or re-enters after reload.
FR-15 — Front-end-only trial boundary. As a stakeholder, I should understand that this is a working front-end trial and not a live production portal, so that I evaluate it as an interface test. (explicit) The Landing surface states the limitations. Observable acceptance: the limitations are visible on the Landing surface.
FR-16 — Role switching is interface testing only. As a reviewer, I should understand that role switching is for interface testing, so that I do not treat it as production security. (explicit) The Login Role dropdown changes interface context only. Observable acceptance: switching roles changes the active role display without any authentication step or access restriction.
FR-17 — Open the downloaded file in Chrome or Edge. As a reviewer, I should open the downloaded file in Google Chrome or Microsoft Edge, so that the trial runs in a supported browser. (required_inference) Observable acceptance: the trial loads and all modules function in either browser.
FR-18 — Test each module with sample data. As a reviewer, I should try each module and enter sample data, so that I can evaluate the screens and reporting fields. (required_inference) Observable acceptance: each module accepts and saves sample entries that flow into the Dashboard and Reports.
The Project Manager oversees the in-scheme programme and uses the trial to judge whether the dashboard and reports give a trustworthy overview. Primary goal: monitor trainers, attendance and medal records and produce daily overall and monthly reports. Distinct responsibilities: reading the unique trainer name count, reviewing attendance and medal data across modules, generating Daily Overall and Monthly reports, and downloading CSV files. Inputs/decisions: decides whether the reporting fields and dashboard counts are sufficient before Version 3 is finalized. Interactions: relies on data entered by Junior/Senior MIS staff and Trainers; shares the review with the Assistant Manager. Observable success: the dashboard count and generated reports match the sample data entered.
The Assistant Manager supports programme oversight with the same monitoring and reporting scope as the Project Manager. Primary goal: monitor trainers, attendance and medal records and produce reports. Distinct responsibilities: reviewing module data, generating Daily Overall and Monthly reports, and downloading CSV files. Inputs/decisions: notes changes wanted in screens, reporting fields or the dashboard. Interactions: works alongside the Project Manager and depends on MIS and Trainer entries. Observable success: reports generate correctly and exports open in Excel.
The MIS user is the primary data-entry operator. Primary goal: enter sample data in the portal modules and produce reports. Distinct responsibilities: entering trainer, attendance, school PE, after-school, player attendance and medal records; generating reports; downloading CSV files in Excel-compatible format. Inputs/decisions: decides what sample records to enter to exercise each module. Interactions: supplies the data that Project Managers, Assistant Managers, Sports Analysts and Team Managers review. Observable success: every module accepts entries and the reports reflect them.
The Sports Analyst reviews attendance and medal records. Primary goal: examine attendance and medal data and produce reports. Distinct responsibilities: reviewing trainer attendance, player attendance and KMK/SGFI/Association/Federation medal records; generating reports; downloading CSV files. Inputs/decisions: assesses whether the recorded fields capture what analysis needs. Interactions: depends on Trainer and MIS entries. Observable success: medal records show the correct medal body and reports export cleanly.
The Team Manager reviews trainer attendance and player attendance records. Primary goal: check attendance records and produce reports. Distinct responsibilities: reviewing trainer daily attendance and individual player attendance; generating reports; downloading CSV files. Inputs/decisions: judges whether attendance capture is complete enough for team oversight. Interactions: depends on Trainer attendance entries. Observable success: attendance records are visible and reports reflect them.
The Trainer is the field recorder. Primary goal: record daily attendance and session reports. Distinct responsibilities: recording trainer daily attendance, school PE reports, after-school reports, individual player attendance, and KMK/SGFI/Association/Federation medal records. Inputs/decisions: enters the day's attendance and session and medal details. Interactions: supplies records reviewed by Team Managers, Sports Analysts, MIS staff and Managers. Observable success: entries save in the browser and appear in reports.
SAG_InScheme_Monitoring_Portal_Trial_v2.html is saved.The design follows the supplied creative direction: functional clarity after Dieter Rams, for a government sports-scheme monitoring tool that must give order, trust and fast reading of attendance and medal data.
Palette (light mode)
#E8E4DC (warm off-white ground)#F4F1EA (light panels)#1C1B19 (near-black)#2E2C29 (near-black controls)#E4570F (Braun orange — active role, key counts, report actions only)#6F6A61 (secondary labels)Typography
Shape and layout
Motion
Imagery
Avoid: no blue or indigo accents; no gradient blobs or glass panels; no hover-lift cards; no centred marketing hero; no playful illustration; no decorative motion.
Readable text and controls stay whole at 375 px, 768 px and 1280 px, wrapping or scaling (for example clamp()) to fit inside the viewport and their container.
The public entry (Landing) is a full-width warm grey field (#E8E4DC) with a 9-column Archivo headline at 64 px on the left: "Monitor every trainer, school and medal", with the subline "Test the SAG in-scheme portal on your laptop and phone." Under the headline sits a solid near-black bar (#2E2C29) carrying the call to action "Download trial v2.0".
Below the hero, a ruled data strip presents four counts in orange tabular numerals with small-caps labels, separated by 1 px rules — a Braun-style control panel that previews the dashboard's reading rhythm. The "How to test" steps and the limitations notice sit on light panels (#F4F1EA) divided by hairline rules. The concept recomposes only accepted content: the download control, the test steps, the included-features list and the limitations.
Interaction Model: Static Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
prefers-reduced-motion, the interface presents a usable static arrangement. (required_inference)SAG_InScheme_Monitoring_Portal_Trial_v2.html) with client-side scripting and browser local storage. (explicit)SAG_InScheme_Monitoring_Portal_Trial_v2.html opened locally in a browser.
Test the SAG in-scheme portal on your laptop and phone.
Scope of the standalone file: six operating roles, six data-entry modules, four medal bodies and two report types.
How to test
Work through the trial portal in order. Each step below names the control and the result you should see before moving on.
Download the HTML file on your laptop.
Check SAG_InScheme_Monitoring_Portal_Trial_v2.html saved to your machine
Open it in Google Chrome or Microsoft Edge.
Check Portal opens locally — no sign-in
Change Login Role from the left-side dropdown.
Check Interface switches for inline testing
Try each module and enter sample data.
Check Entries are saved in this browser’s local storage
Generate reports and download CSV files in Excel-compatible format.
Check CSV file downloads; print/PDF option available
For mobile, transfer the same file to your phone and open it in Chrome.
Check Same trial file, same modules at phone width
Trial Portal Version 2.0
09features in the trial build
Every module below opens from the same standalone file. Switch the Login Role to read each surface as its operating role would.
Production status — This is a working front-end trial, not a live production portal.
Where sample data lives — Sample entries are saved in the same browser using local storage.
Backend — GPS verification, live selfie capture, secure login, a server database and real photo uploads are backend items pending for Version 3.
First test this version on your laptop and phone. Note any changes you want in the screens, reporting fields or dashboard. We can then finalize Version 3 for actual software development.

Test the SAG in-scheme portal on your laptop and phone.
Scope of the standalone file: six operating roles, six data-entry modules, four medal bodies and two report types.
How to test
Work through the trial portal in order. Each step below names the control and the result you should see before moving on.
Download the HTML file on your laptop.
Check SAG_InScheme_Monitoring_Portal_Trial_v2.html saved to your machine
Open it in Google Chrome or Microsoft Edge.
Check Portal opens locally — no sign-in
Change Login Role from the left-side dropdown.
Check Interface switches for inline testing
Try each module and enter sample data.
Check Entries are saved in this browser’s local storage
Generate reports and download CSV files in Excel-compatible format.
Check CSV file downloads; print/PDF option available
For mobile, transfer the same file to your phone and open it in Chrome.
Check Same trial file, same modules at phone width
Trial Portal Version 2.0
09features in the trial build
Every module below opens from the same standalone file. Switch the Login Role to read each surface as its operating role would.
Production status — This is a working front-end trial, not a live production portal.
Where sample data lives — Sample entries are saved in the same browser using local storage.
Backend — GPS verification, live selfie capture, secure login, a server database and real photo uploads are backend items pending for Version 3.
First test this version on your laptop and phone. Note any changes you want in the screens, reporting fields or dashboard. We can then finalize Version 3 for actual software development.
No comments yet. Be the first!