# Parent–teacher meetings

Publish meeting slots, book families, record discussion outcomes and manage follow-up tasks.

Category: Community
Guide: https://avkul.in/docs/guides/module-ptm/
Guided sample demo: https://avkul.in/docs/demo/module-ptm/
Snapshot: 11 October 2026

## Features

- Teacher slots
- Family bookings
- Reschedule and cancel
- Meeting notes
- Family-visible follow-ups
- In-app reminders

## Access and setup

Intended access: Super Admin, School Admin, Principal, Vice Principal, Management, Teacher
- An assigned school account with the required permissions.
- The academic, student or staff setup used by this workflow.

Permission keys: communication:view, communication:create, communication:delete, communication:update

## Workflow

1. Create or choose the permitted teacher meeting slot.
2. Book the linked child and verify availability.
3. Record the meeting outcome with the correct note visibility.
4. Assign and complete any follow-up action.

## Fields and controls

- id (string, optional)
- staffId (string, declared required)
- date (string, declared required)
- startTime (string, declared required)
- endTime (string, declared required)
- capacity (number, optional)
- location (string, optional)
- isActive (boolean, optional)
- version (string, optional)
- slotId (string, declared required)
- studentId (string, declared required)
- notes (string, optional)
- status (string, declared required)
- reason (string, optional)
- privateNotes (string, optional)
- feedback (string, optional)
- bookingId (string, declared required)
- title (string, declared required)
- owner ("SCHOOL" | "FAMILY", declared required)
- dueDate (string, optional)
- force (boolean, optional)
- parentId (string, optional)

## Current limits

- Private staff notes and family-visible notes differ. Reminder actions do not guarantee external SMS, email or push delivery.

## Actual application access

- https://avkul.in/en/school/ptm

## API reference

- GET /api/v1/ptm/workspace — Read; communication:view
- POST /api/v1/ptm/workspace/slots — Slot; communication:create
- POST /api/v1/ptm/workspace/slots/:id/delete — Remove; communication:delete
- POST /api/v1/ptm/workspace/bookings — Book; communication:create
- POST /api/v1/ptm/workspace/bookings/:id/change — Change; communication:update
- POST /api/v1/ptm/workspace/bookings/:id/notes — Notes; communication:update
- POST /api/v1/ptm/workspace/follow-ups — Task; communication:update
- POST /api/v1/ptm/workspace/remind — Remind; communication:create
- GET /api/v1/ptm/slots — List Slots; communication:view
- POST /api/v1/ptm/slots — Create Slot; communication:create
- PATCH /api/v1/ptm/slots/:id — Update Slot; communication:update
- DELETE /api/v1/ptm/slots/:id — Remove Slot; communication:delete
- GET /api/v1/ptm/bookings — List Bookings; communication:view
- POST /api/v1/ptm/bookings — Create Booking; communication:create
- PATCH /api/v1/ptm/bookings/:id/status — Update Booking Status; communication:update

## Demo access

No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links.

Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow.