Board fit for schools in India
Schylva is a school management system for CBSE, ICSE and State Board schools that connects people, classes, attendance, fees, timetables, communication, exams and published results in one platform. Each school still needs its exact academic structure, grading scale, report-card format and role responsibilities confirmed during evaluation and configured before rollout.
There is no separate Schylva product edition for each board. School-specific configuration is still required; the board name alone does not prove fit.
Schylva targets a response to demo and custom-quote requests within two working days. Working days exclude weekends and public holidays.
The distinction that matters
An evaluation guide—not a configuration screen or a statement of board approval.
Three evaluation contexts
Each school still needs an exact demonstration and confirmed configuration.
Board context
Confirm the academic year, grades, assessment pattern and expected result.
Decision checkpointValidate one exam-to-result workflow before rollout.
Bring to the evaluation
Board context
Demonstrate the intended subjects, assessment rules and result format.
Decision checkpointRecord what works, needs configuration or remains unresolved.
Bring to the evaluation
Board context
State Board is not one universal academic model. Confirm the named board, grades, medium or language, rules and output.
Decision checkpointEvaluate the named school; do not infer every State Board format.
Bring to the evaluation
Seven evaluation areas
Use the school’s real structure and expected output to decide fit. Read across each area before deciding fit. These are evaluation questions, not a score or an automatic eligibility decision.
| Evaluation area | Connected in Schylva | Confirm for your school | Current boundary |
|---|---|---|---|
| School structure | Academic year, classes, sections, subjects and linked records. | Board, grade range, calendar and class model. | The board name alone does not define the configuration. |
| Roles and access | Role-aware access for four school roles. | Who prepares, reviews, publishes and receives each record. | No arbitrary custom roles, SSO, SCIM or unrestricted permissions claim. |
| Attendance, fees and communication | Attendance, fee records, payments and circulars. | Operating rules, handoffs and payment path. | WhatsApp and non-login SMS are not school workflow-notification channels. |
| Timetables and academics | Timetables, subjects, homework and study materials. | Periods, subjects, timetable ownership and academic workflow. | No automatic timetable, curriculum delivery or full LMS claim. |
| Exams, marks and published results | Exams, schedules, marks, results and supported publishing. | Exam structure, components, checks and role responsibilities. | No advanced components, moderation, multi-stage approval or publishing-history claim. |
| Grading and report-card format | Configurable grading scales and board-specific report-card formats for CBSE, ICSE and State Board requirements. | Availability and setup of the exact scale and report-card format. | No arbitrary grading, every-format or report-card PDF claim. |
| Implementation and validation | Written plan, configuration, initial migration, training and validation. | Sources, owners, migration scope, checks and school approval. | No universal migration format, unlimited scope or one timeline. |
All seven areas stay visible on every screen size. No board name, check mark or screenshot substitutes for the school’s exact demonstration and sign-off.
Assessment to published result
The exact structure, grading scale and report-card format remain configuration decisions. This is an explanatory workflow, not an interactive product simulation.
Academic context
Define the representative structure for evaluation.
Check the boundaryThis does not claim curriculum delivery.
Exam and schedule
Connect the exam, subjects and schedule to the academic context.
Check the boundaryConfirm required assessment components.
Marks and result
Keep marks and results with the selected exam and Student.
Check the boundaryNo arbitrary grading or advanced-components claim.
Review and publish
Review the result before an authorised user publishes it.
Check the boundaryReadiness is not moderation, multi-stage approval or publishing history.
Parent or Student view
The linked Parent or relevant Student reviews the published result.
Check the boundaryPublished does not imply report-card PDF generation.
Product evidence
Focused sample screens show only the evidence described below. Review the administrator context separately from the Student’s published record. These captures are not a matched end-to-end transaction.
School-side context
Sample result set, assessment year and published status.
Actual Schylva web product screen · publication-safe focused derivative · sample school data. Static web UI, not a native app.
This focused Administrator screen does not prove saved marks entry, grading configuration, support for every board format, analytics, PDF generation, moderation or publishing history.
A result set is visible as published, while the marks, processing and report-card areas still prompt for selection. The Marks button does not establish saved entry or configured grading.
Review exams and results evidenceStudent-side outcome
Sample grade, totals and subject-level Student result.
Actual Schylva web product screen · publication-safe focused derivative · sample school data. Static web UI, not a native app.
This is not a Parent view and does not prove grading configuration, support for every board format, PDF generation, moderation or publishing history.
The sample 100%, A+ and 200/200 are fictional example values, not school performance claims. The visible grade bands do not establish the exact rules for your school.
Review exams and results evidenceSupported, confirm, boundaries
Keep support, confirmation and boundaries visible together.
Product scope
School-specific review
Do not infer or promise
Configuration path
Use redacted inputs and explicit approval checkpoints. Demonstrate, configure and validate against the same representative requirement.
Identify
Name the board, year, grades, subjects, assessments, grading and report.
CheckpointThe requirement is understood consistently.
Demonstrate
Record what works, needs configuration or remains unconfirmed.
CheckpointEvidence is separated from proposed work.
Configure
Prepare the agreed structure, roles, grading and report-card context.
CheckpointRepresentative records are ready for review.
Validate
Review records and role handoffs before activation.
CheckpointThe school owns the final readiness decision.
Prepare a board-fit demonstration
Use one representative academic scenario. A fictional or redacted report-card example gives the discussion a concrete starting point.
Book a board-fit demoWhich board, state and academic year apply?
Which grades, classes, sections and subjects apply?
Which exam, term, schedule and components apply?
Which marks, grade bands or pass rules apply?
What must staff and recipients see? Bring a redacted example.
Who prepares, reviews, publishes and receives results?
Which language, device, connectivity, migration or timing constraints matter?
Board-fit questions
Confirm exact academic and reporting needs in a demonstration.
Schylva supports these contexts, configurable grading scales and board-specific formats. Confirm the exact structure, scale, format and roles during evaluation and implementation.
No. One product connects common operations, but school-specific configuration is still required.
Schylva supports configurable grading scales. Bring the approved scale to confirm setup; arbitrary grading logic is not promised.
Schylva supports board-specific formats. Confirm the exact format; not every format or downloadable report-card PDF is promised.
No certification, affiliation, accreditation, approval or legal-compliance claim is made. Board names describe evaluation context.
Supported scope covers exam setup, schedules, marks, results and publishing. It excludes advanced components, moderation, multi-stage approval, publishing history and report-card PDF generation.
No universal claim is made. Name the state, board, language, rules and report-card expectation for evaluation.
Bring the board, structure, exam, grading scale, roles and a fictional or redacted report-card example. Do not share production Student or personal data.
Make the decision concrete
Separate demonstrated support, configuration and open questions.
Schylva targets a response to demo and custom-quote requests within two working days. Working days exclude weekends and public holidays.
The board-fit context stays attached to your demo or quote path. Do not send live school records or credentials.