A residential madrasa demo is best verified with one single fictional scenario: a new student from entry to end of first month — admission, room allocation, attendance, leave, fees, and the month-end report. Instead of being shown modules here and there, completing this one lifecycle exposes the software’s real quality. (The scenario is fictional — not a real customer example; run it with fictional data for verification.)
What to verify: one hostel scenario with evidence and limits
Name the scenario — “DEMO-031: the first month”. Turn the steps into verifiable questions:
| Step | Ask them to do | Verification question | Evidence |
|---|---|---|---|
| 1. Admission | admit DEMO-031 (40+ fields) | guardian + boarding data in one profile? | profile screen |
| 2. Room | room 3, two roommates | appeared in the room-wise list? | list |
| 3. Attendance | daily, first week | absence SMS went out? | SMS log |
| 4. Leave | one-day leave + return | reconciled with attendance? | leave record |
| 5. Fees | monthly partial via bKash | receipt and dues correct? | receipt PDF |
| 6. Report | month-end summary | everything combined on one page? | report |
After each step, fill the “Evidence” column — not in words, with a screenshot or a printed report. A step without evidence is not a pass.
A usable sample: the synthetic acceptance sheet
Make the acceptance sheet like this:
- Total steps: 6 — passed: __ — slow pass (took too long): __ — failed: __
- Time taken per step (minutes) — this estimates staff daily time cost.
- Do wrong on purpose: a wrong fee amount, a wrong room allocation — how easy is the correction, and does history survive?
- Export the data and open it — the door to leaving the system.
Decide the pass rule beforehand: five of six passed plus a passed correction test, otherwise reject — and write the decision inside the demo.
Residential demo: workflow steps and limitations
- Give the same scenario to two or three vendors — comparison is only possible on the same measurement.
- Have YOUR staff drive it, not the vendor’s demo specialist.
- Limitation: demo environments run faster than production — pad time estimates by 25%.
- What the scenario excludes (exams, library) — ask in separate small demos; do not force everything into one file.
Residential demo: questions to ask before your demo
- Are all six steps possible in one session?
- On wrong-entry correction, is history kept?
- Does the month-end report combine boarding and academic data?
For each module in the scenario: attendance, fees, madrasha management with boarding, and pricing as the evaluation yardstick. When ready, book a free demo and run it on your own data.
Residential demo FAQ
Where do we get DEMO-031-style sample data?
Make it — 2–3 fictional students and sample fees. Self-made data is the best way to understand a system.
If a vendor cannot perform a step, do we drop it?
No — write what happened (“done manually”, “done in Excel”). A partial solution is comparison data too.
Isn’t seeing all modules better than six steps?
No. Depth over breadth. Software passing six steps likely does the rest; software failing six does not — whatever the brochure says.