Trường Số PRD
Implementation-grade requirements for Trường Số as a center-management platform for English centers and small private schools in Vietnam. The set extends the live admissions CRM at b2c.truongso.net into students, classes, attendance, finance, staff, parent communication, inventory, reports and administration.
Key facts, origin and limits
Agent #1 — Product Research & PRD. Build the PRD at roadmap.truongso.net/prd. Log into the product above and scan 100% of its features and functionality. Fully analyze the product structure, workflows, user flows, and functions. Create all necessary PRDs based on the functionality of the PSEONE product. Make the PRDs detailed enough to serve as a complete specification for Agent #2 to implement.
The in-app survey of the reference product did not take place in this session (the automated login was withheld pending a permission decision), so the set was written from public sources and the FLYER codebase, and the Key facts, origin and limits box at the top of each page lists the items still to verify in-app.
Drafted by an AI assistant in a single session on 10/09/2026 from: the public PSE ONE site (pse4.one), the live staging /v3 OpenAPI specification (182 paths), a read of the center-crm-frontend codebase, the Cloud theme frames, and the earlier Trường Số CRM prototype. It is an original specification for Trường Số, not a reproduction of any competitor’s product.
This is a proposal for team discussion, not a decision. The ten items in section 3 are open until ratified.
Sources
- A second scan of PSE ONE's public sources on 16/09/2026 (features page, pricing, the ten user-guide articles: plan upgrade rules, inventory, Zalo configuration, exam score entry, ZNS templates, vouchers, automatic email, curriculum and lessons, data onboarding, expense vouchers; and the product articles) is the basis for PRDs 13 to 19. Those sources name features and a few steps only; the detailed specification in each PRD is Trường Số's original design.
- Public competitor research (pse4.one: home, features, pricing, user guides on data import, Zalo and ZNS, vouchers, expense vouchers, score entry, inventory) as of 10/09/2026. Pricing observed: Basic 199,000 VND/month up to 100 students, Pro 400,000 up to 300, Business 700,000 up to 500, Enterprise 1,000,000 unlimited; add-on storage 2,500,000 VND/year per 40 GB.
- Codebase read of
center-crm-frontend(routes, features, i18n, API layer, permissions, dashboard). - Staging OpenAPI
/v3/openapi.json: 182 paths, 504 schemas (Crm 148, Teacher 73, Parent 5, Payment 1). - Cloud theme reference and frames (trang-chu, hoc-sinh, lop-hoc, giao-bai) and the earlier Trường Số CRM prototype (pipeline board, contacts, deal detail, reports, wizard).
- The EXISTING / EXTEND / NEW tags in each PRD API contract and the backend column in section 2 come from a comparison with the staging
/v3specification of 10/09/2026.
Limits
- Every PRD and companion document in the section 2 index is at Draft status.
- The "Proposed design" section at the top of each PRD was added on 16/09/2026.
Browse the feature catalogue by group →
1How to read this set
Each PRD has the same eleven parts: purpose and scope, personas and roles, user stories with Given/When/Then acceptance criteria, screens with columns and fields, business rules, data model, API contract marked EXISTING / EXTEND / NEW, permissions per role, analytics events, edge cases, open questions, and the items to verify once the competitor's application can be surveyed in-app (in the Key facts, origin and limits box at the top of the page). Tables are the primary form; prose is kept short. Labels in the product are Vietnamese; the glossary is the source of truth for wording. Every PRD opens with a "Proposed design" section: numbered, captioned mockups of its screens in the Cloud design system, so the team sees the product before reading the specification.
Start with 00 for the tenancy and role decisions that every other page relies on, then 11 for the entity map. Build order follows the phase plan in 00 section 7.
2PRD index
| # | PRD | Module (VI) | Backend state | Phase | Scope in one line |
|---|---|---|---|---|---|
| 00 | Overview and architecture | Toàn hệ thống | none | P1 | Vision, personas, tenant = center and branch = school, role matrix, navigation map, existing vs new, phasing, decisions to ratify. |
| 01 | Admissions CRM | Tuyển sinh | existing + new | P1 | Pipeline, sources, channels, call log, callback queue, do-not-call, trial bookings, placement tests, conversion wizard to enrolled student. |
| 02 | Students (SIS) | Học viên | extend | P1 | Student record, guardians and consent, status lifecycle, enrollment history, documents, notes, learning data, transfer, anonymise. |
| 03 | Classes and scheduling | Lớp học | extend | P1 | Courses, levels, rooms, classes with patterns generating sessions, conflicts, enrollments, substitutes, make-ups, timetable views. |
| 04 | Attendance | Điểm danh | new | P1 | Four statuses, phone-first teacher sheet with offline queue, corrections with audit, guardian notification, package consumption, reports. |
| 05 | Tuition and finance | Tài chính | existing + new | P1 / P2 | Fee plans and session packages, invoices, cash and SePay payments, receipts, debt aging, vouchers, refunds, expenses, cash book, e-invoice hook, reports. |
| 06 | Teachers and staff | Nhân sự | new | P2 | Staff directory, contracts, pay rules, timesheets from attendance, evaluations, documents. |
| 07 | Parent communication | Sổ liên lạc | extend | P1 / P2 | Message routing over Zalo ZNS, OA, app, email; transactional messages; announcements; progress reports; parent portal with OTP; consent. |
| 08 | Inventory | Kho | new | P2 | Catalog, per-branch stock ledger, issue to student or class linked to finance, transfers, counts, low-stock warnings. |
| 09 | Reports and dashboards | Báo cáo | extend | P1 / P2 | Executive dashboard with drill-downs, role home pages, report library, digests, exports. |
| 10 | Settings and administration | Cài đặt | extend | P1 | Tenant, branches, users and invitations, unified roles and scopes, catalogs, finance and notification policies, integrations, audit log. |
| 11 | Data model and API | Nền tảng | none | P1 | Entity catalog and relationships, API conventions, existing vs needed surface per module, Excel migration toolkit in fixed order. |
| 12 | Non-functional requirements | Nền tảng | none | P1 / P2 | Performance targets, security, Decree 13/2023 compliance, RBAC rules, audit log, backup and recovery, vi/en localisation, accessibility. |
| 13 | Exam scores and learning results | Đào tạo | existing + new | P1 / P2 | Assessment periods per class, class-wide or per-student score entry by skill, comments, attachments, publish with approval, parent notification, report cards, re-grading history; certificates in P2. |
| 14 | Curriculum, lessons and digital resources | Đào tạo | new | P1 / P2 | Versioned curriculum tree of units and lessons; lessons mapped to sessions in order; the teacher's teaching log; a digital resource library with storage quota and permissions. |
| 15 | Targets and performance | Điều hành | existing + new | P1 / P2 | Targets per period and per scope (centre, branch, individual); actuals computed from existing data; top-down cascade; progress, forecast and alerts; bonus linkage in P2. |
| 16 | Internal tasks, reminders and leave requests | Vận hành | extend + new | P1 / P2 | Tasks assigned to staff and linked to customers, students, classes, invoices; system-generated tasks; reminders and the notification centre; leave requests with approval; incident reports from teachers. |
| 17 | Mobile applications | Nền tảng | existing + new | P1 / P2 | One codebase with role-specific shells for managers, teachers, consultants and parents; PWA first, native wrappers in P2; push, offline work, device registry, feature matrix. |
| 18 | Online learning and test preparation | Đào tạo | existing + new | P1 / P2 | Learner and class links to FLYER LMS, homework bound to lessons, results sync, sellable test-prep packages with entitlement on payment, single sign-on from the parent portal; centre-authored courses in P2. |
| 19 | Service plans and subscription | Nền tảng | new | P1 / P2 | Plan catalogue and limits, tenant subscription lifecycle from trial to termination, enforcement points, upgrades with the 12-month proration formula, subscription invoices, a plans page in settings. |
| none | Cloud theme — interface conformance report | Giao diện | none | none | The CRM interface audited against the Cloud design system: deviations found, how they were handled, a token conformance table, six screens before and after, and rules for the components the specification does not cover. |
| none | Vietnamese UI glossary | Từ điển thuật ngữ | none | none | VI label, EN term, definition and owning module for every term used in the product. |
| none | Test plan seed | Kiểm thử | none | none | Per PRD: flows to cover, high-risk areas, cross-module scenarios, automation priority. |
3Decisions awaiting ratification
- Tenant = CRM Center; Branch = FLYER School; the existing accessible-schools list is the branch scope.
- One role catalog extending CRM roles with scopes own / branch / all; school role derived.
- Lists first: every new module ships a table view; the pipeline Kanban remains optional.
- An enrolled student always has a FLYER learner profile, created or linked at conversion.
- Sessions are materialised rows; attendance, packages and pay attach to sessions.
- Finance reuses Tuition and GroupInvoice; session packages are a fee plan type with a maintained balance.
- Guardian channels in order Zalo ZNS, app push, email; SMS not built.
- Existing CRM routes stay under /crm; new modules are root routes in the same shell; settings consolidate under /settings.
- Vietnamese product language with a complete English locale; all strings in message files.
- Phase 1 is the daily loop (enroll, schedule, attend, collect, report); inventory, staff pay and e-invoice are phase 2.
Trường Số (truongso.net) · FLYER internal