Feature PRD catalogue

The full specification for the Trường Số centre-management platform: 20 PRDs, each with the same eleven parts (purpose, current state, user stories, screens, business rules, data model, API contract, permissions, analytics, edge cases, open questions). Every page opens with a Proposed design section: 154 numbered, captioned mockups in the Cloud design system.

Key facts, origin and limits

Contents: 20 PRDs + 3 companion documents
Design: 154 screens, 28 mobile
Languages: Vietnamese · English
Status: Draft v1, awaiting ratification

Catalogue assembled by an AI assistant from the Trường Số PRD set, under the original request quoted verbatim on the PRD hub page. A proposal for team discussion, not a final decision.

Sources

The set was written from public competitor research, the center-crm-frontend codebase and the staging /v3 OpenAPI specification.
Screen counts per PRD are counted from the design image folders on every build.

Limits

Every PRD is at Draft v1, awaiting ratification.

The daily loop

The loop a centre runs every day, from the first enquiry to the fee being collected.

Admissions (CRM) 10 screensCustomer pipeline, call log, trials, placement tests, the conversion wizard to an enrolled student.
Students (SIS) 8 screensStudent and guardian records, status lifecycle, pauses, branch transfers, learning data.
Classes and scheduling 9 screensCourses, classes generating sessions from a pattern, conflict detection, enrolment, substitutes, make-ups.
Attendance 8 screensA phone-first sheet with an offline queue, four statuses, guardian notification, package consumption.
Tuition and finance 7 screensFee plans, invoices, cash and SePay payments, debt aging, vouchers, cash book, expense vouchers.
Parent communication 8 screensRouting over Zalo ZNS, OA, app and email; transactional messages; progress reports; the OTP parent portal.

Teaching

What is taught and what comes back: curriculum, scores, and the online layer linked to FLYER.

Curriculum and resources 10 screensA versioned curriculum tree, session-to-lesson mapping, the teaching log, a resource library with quota.
Exam scores and results 8 screensSkill-based assessments, a class-wide score grid, review then publish, report cards, certificates.
Online learning and test prep 10 screensClasses linked to the FLYER LMS, homework bound to lessons, result sync, sellable test-prep packages, SSO.

Management

For owners and branch managers: people, figures, goals, and the work queue.

Reports and dashboards 7 screensAn executive dashboard with drill-downs, role home pages, a report library, the weekly digest.
Targets and performance 9 screensTargets per period, cascaded centre to branch to individual, pace forecast, ranking.
Teachers and staff 9 screensStaff directory, contracts, pay rules, timesheets computed from attendance, periodic evaluations.
Tasks and leave 11 screensTasks assigned to staff, system-generated work, reminders, leave requests with approval, incident reports.
Inventory 8 screensItem catalogue, per-branch stock ledger, issue to a student linked to finance, stock counts.

Platform

The decisions every module rests on, and the system-wide requirements.

Overview and architecture 6 screensTenant and branch, the role matrix, the navigation map, phasing, decisions awaiting approval.
Settings and administration 11 screensCentre, branches, users and invitations, roles and scopes, catalogues, integrations, the audit log.
Mobile applications 7 screensOne codebase with role shells for managers, teachers, consultants and parents; PWA first.
Service plans and subscription 8 screensPlan catalogue and limits, subscription lifecycle, enforcement points, prorated upgrades, invoices.
Data model and APIEntity catalogue, API conventions, existing versus needed surface, the Excel migration toolkit.
Non-functional requirementsPerformance, security, Decree 13/2023, RBAC, audit, backup, localisation, accessibility.

Open the full PRD index →

Trường Số (truongso.net) · FLYER internal