# School software demo checklist

VASUYASHII | Reviewed 28 September 2026

A blank worksheet for comparing an agreed software demo. The rows describe questions to test, not a promise that every feature is included.

[Current service scope](https://www.vasuyashii.com/services/school-management-software)

## Prepare the session

Use synthetic records and role labels. Do not put student or patient details, client names, contact information, bank details, credentials or live invoices into this worksheet or the public enquiry form.

- Session date: ______
- Demo/product version: ______
- Business alias: ______
- First workflow to evaluate: ______
- Reviewer role: ______

- School-size band and relevant academic periods: ______
- Required roles and the first workflow to evaluate: ______
- Source-system and record-format names only: ______
- Configuration, hosting, migration, training and support responsibilities: ______

## Record the demonstration

Result choices: Not reviewed / Shown with sample data / Needs configuration / Needs confirmation / Out of scope. A shown result applies only to the tested version and scenario.

| Workflow | Ask to see | Result | Evidence reference or gap | Next action / owner role |
|---|---|---|---|---|
| Admissions | Create Synthetic Applicant A; review required documents; record the approval decision; inspect enrolment and the linked student record. | Not reviewed | — | — |
| Fees | Select a sample fee structure and inspect the resulting invoice. Check concessions, partial payments and reversals only when included in the proposed scope. | Not reviewed | — | — |
| Attendance | Request attendance for one sample class and date; inspect an authorised correction and the relevant report. Ask which devices or integrations require separate setup. | Not reviewed | — | — |
| Roles and portals | Compare the selected administrator, teacher and parent views using synthetic accounts. Ask who may view, correct or export each record. | Not reviewed | — | — |
| Academic changes | Discuss the required academic-year, class or section changes and how existing history is retained. | Not reviewed | — | — |
| Migration and recovery | Use a small synthetic import to agree field mapping, duplicate handling, validation and recovery responsibilities. | Not reviewed | — | — |

## Scope and quotation

- Included configuration and modules: ______
- Custom work and exclusions: ______
- One-time, recurring and third-party costs: ______
- Data transfer and verification responsibility: ______
- Hosting, backup and restore responsibility: ______
- Training and support coverage: ______
- Acceptance criteria and responsible role: ______

## Decision

- Findings still requiring evidence: ______
- Next step: Further demo / Scoped pilot / Proposal review / Not a fit
- Decision date and role: ______

Admission evidence on the service page shows a synthetic enrolment and selected fee invoice. It does not establish payment collection, every attendance workflow or a live school deployment.

Keep completed worksheets in your private project workspace. Use the public enquiry only for a non-sensitive summary of your requirements.