The rule for parent-teacher discussion records: topic, decision, responsibility, deadline — four fields on one page; and restricted access to the record. Without a record, the next discussion starts from zero — the only antidote to “I never said that” disputes is a written record.
What to verify: topic, duty, deadline and restricted access
The discussion-record sheet:
| Field | Example | Why |
|---|---|---|
| Date + participants | 18 Nov, ustadh-B + guardian | knowing later who said what |
| Topic | “slow progress in maths” | one line |
| Decision | “2 extra drill days weekly” | what was agreed |
| Responsibility split | drill — ustadh; home watch — guardian | both sides’ share |
| Deadline | re-evaluation in 15 days | the measure of closure |
| Result | 30 Nov: improvement seen | cycle closed |
Restricted access: this record is seen only by the involved ustadh, the office, and the guardian — not other teachers or outsiders; family-sensitive information (medical, discipline) does reach here.
A usable sample: the meeting follow-up template
After a discussion, the office/ustadh fills:
- Date, place, participants.
- Topic (one line).
- Decision (one line).
- Duty split (task → who → by when).
- Re-evaluation date.
Another discussion needing it? A new entry — the old record is not updated; cycles stay separate.
Follow-up records: workflow steps and limitations
- Before the discussion, open the student’s record — attendance, marks, earlier discussions.
- The record is entered by office/ustadh within 10 minutes of the discussion — while memory is fresh.
- A passed re-evaluation date should surface a note — written-and-forgotten is the most common loss.
- Limitation: the record is not a full transcript — it documents decisions and duties; every spoken sentence need not be written.
Follow-up: questions to ask before your demo
- Are discussion records attached to the student profile?
- Can access be restricted by role?
- Does the re-evaluation date produce a note/reminder?
See discussion records and role limits in madrasa operations and student management features; reviewing earlier records in the Hifz tracking documentation.
Follow-up FAQ
Can discussions stay on paper?
They can — but a lost file is lost in handover; in a system it stays attached to the student profile.
If the guardian wants to see the record?
Show it — showing written decisions builds trust; editing rights stay with the institution.
The guardian did not come?
Record “absent, recall date” — the discussion cycle must not be dropped.