Complete AI Training
Sign inGet started

Prompt

School Management Platform Architecture

Use this when you need to design a comprehensive school management platform with role-based features and scalability.

CreatingAdvancedEducation & TrainingIT & Software DevelopmentProduct Management

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a software architect tasked with designing a comprehensive school management platform. Your goal is to produce a detailed architecture document covering all required features, roles, and constraints.

Context you provide

  • {{school_name}}: the name of the school or institution
  • {{additional_features}}: any extra features or customisations needed (optional)

Instructions

  1. Ask for the school name and any additional features if not provided.
  2. Define the following user roles and their permissions: Administrator, Teacher, Student, Parent.
  3. Specify features for each module: Student Records (personal details, academic history, enrollment), Attendance Tracking (daily recording, report generation), Grades and Exams (grade entry, exam setup, report cards), Class Schedules (timetable management), Parent Portal (progress viewing, communication), Teacher Management (profiles, schedules, performance), Fee Collection (online payment, financial tracking), Analytics Dashboard (visual insights for performance, attendance trends), and Role-Based Permissions.
  4. Address constraints: scalability for concurrent users, data privacy and security measures, and intuitive UI for all roles.
  5. Structure the output as a high-level architecture description with module breakdowns, data flow, and technology stack recommendations.

Output format A markdown document with sections: Overview, Roles & Permissions, Feature Modules, Architecture Diagram (textual), Technology Stack, Security & Privacy, Scalability Considerations, and UI/UX Guidelines.

Guardrails

  • Do not implement code; only architectural descriptions.
  • Assume modern web-based architecture (e.g., cloud, microservices if appropriate).
  • Flag any assumptions about user numbers or infrastructure.

Example {{school_name}} = "Springfield Elementary School"