Progress, timeline, and remaining work

Document: SDD-13
Status: Working draft
Date: 19 September 2026
Source: Student Portal and CMS Daily Checklist, downloaded 19 September 2026. Faid Zamin shared that sheet in the working-group chat on 18 September 2026 and said the student portal v1 frontend was still being built.

Local copy: materials/docs/working-group/.

1. What changed in the latest sheet

Status cells did not move. The download has the same 112 detailed rows, the same Frontend / Mobile / Backend values, and the same TBC owners and target weeks as the 18 September copy.

The only newer timestamp is CAP-35 on the student portal (accessibility), last updated 9 September 2026. Its status is still Demo. Every other detailed row was last touched 7 September 2026.

The chat after the 18 September meeting records that the meeting ended. It does not record a new date, a new owner, or a status change.

Completion, using the sheet’s own word: a row is complete only when it is Live. Live count is 0. Demo, Partial, and Placeholder are not completions. The simplified tab’s “Frontend ready” (23 grouped rows) is the same work the detailed tab calls Demo or Partial.

2. Milestone progress

Applicable rows exclude Frontend = Not applicable. “Started” means Demo, Partial, or Placeholder. Backend is Needs checking on every applicable row, including the ones with a started frontend.

By portal, detailed tab:

The student UI is ahead of the sequence. Product priority on the Timeline tab is still admissions before the core student portal. Four admissions rows have a student-side frontend start (sign-in Placeholder, accessibility Demo, privacy Partial, and the mobile shell is Not applicable). The applicant and staff halves of admissions are not started.

3. Timeline

From the Timeline tab, fetched 19 September 2026. Kickoff is TBC. Backend commitment is TBC. Every milestone target is TBC. There is no agreed week to put on a calendar.

The bars below are the order only. Their length is not a duration the group has agreed. Do not read the dates as a plan.

gantt
    title Sequence only. Kickoff and every target on the sheet are TBC.
    dateFormat YYYY-MM-DD
    axisFormat %d %b
    section Order
    M1 Confirm rules and integration     :m1, 2026-09-21, 7d
    M2 Admissions launch                 :m2, after m1, 21d
    M3 Core student portal               :m3, after m2, 28d
    M4 Lesotho pilot acceptance          :m4, after m3, 14d
    M5 Campus expansion                  :m5, after m4, 21d

4. Gantt of progress

Each bar is the share of applicable rows, not time. Filled means the frontend has been started. Nothing in the filled part is Live.

gantt
    title Frontend started versus not started. Snapshot 19 Sep 2026. Not a calendar.
    dateFormat YYYY-MM-DD
    axisFormat %d
    section M2 Admissions
    Started 4 of 18                         :done, a1, 2026-09-01, 4d
    Not started 14 of 18                    :active, a2, after a1, 14d
    section M3 Core student
    Started 16 of 51                        :done, b1, 2026-09-01, 16d
    Not started 35 of 51                    :active, b2, after b1, 35d
    section M5 Expansion
    Started 12 of 34                        :done, c1, 2026-09-01, 12d
    Not started 22 of 34                    :active, c2, after c1, 22d

M1 and M4 have no frontend rows. They are still open: rules and owners are TBC, and Cyberjaya has not accepted a pilot.

5. Tasks still to do

Before any milestone can be called Live

• Name the next-action owner on each row. All 112 are TBC.
• Agree a target week. All 112 are TBC.
• Agree kickoff and the backend commitment on the Timeline tab. Both are TBC.
• Move backend off Needs checking. That is every applicable row.

M1 — confirm rules and integration

• CAP-42. Copyright and provider approvals. Non-software. Not started as an operating check.

M2 — admissions launch

These are the tasks on the critical path. Applicant and staff rows are Not started. Student rows listed here are not Live.

M3 — core student portal

16 of 51 rows have a student frontend start. 35 are not started, including every lecturer row and the staff path for the same capabilities. A student Demo does not close the row. Lecturer publish, attendance, and marking, and the staff approval path, are still to do. See SDD-11.

M4 — Cyberjaya acceptance

CAP-41 staff training and operating readiness. Not a screen. Not started.

M5 — campus expansion

22 of 34 applicable rows are not started. Includes quizzes, live class, library, visa, housing, scholarships, and online payment. Do not pull these forward of admissions.

6. Related documents

• Milestone definitions: SDD-03
• Full rows: SDD-11
• Sheet: working-group source