Operational logbooks for education providers

Compliance Logbooks for education providers

Keep recurring student and operational records in one searchable, institution-scoped workspace with follow-up and due-date reminders.

Compliance Logbooks gives provider teams four focused record types: Pre-Training Review Call, Warning Letters, Intervention Strategy, and Student Request Logbook.

How Compliance Logbooks helps provider teams

  • Record entry, follow-up, and due dates alongside student identity and notes.
  • Capture type-specific details for calls, warnings, intervention plans, and student request outcomes.
  • Search across entries, filter by logbook and date range, and generate reminder emails for active users in the institution.

Provider outcomes

  • Replace disconnected operational notes with a shared institution-scoped record of recurring student and compliance workflows.
  • Make follow-up ownership and due dates visible without mixing different logbook types together.
  • Give institution users a practical create and edit workflow while keeping deletion restricted to institution administrators.

How it works

  1. Choose a logbook type: Open the logbook workspace and select Pre-Training Review Call, Warning Letters, Intervention Strategy, or Student Request Logbook.
  2. Record the operational details: Add the entry date, follow-up date, due date, student details, notes, and the fields specific to the selected logbook type.
  3. Search and maintain the record: Use Search entries, the logbook filter, and date filters to find records. Institution users can create and edit entries; deletion is restricted to institution administrators.

Common questions about Compliance Logbooks

Which logbooks are included?

The workspace includes Pre-Training Review Call, Warning Letters, Intervention Strategy, and Student Request Logbook.

Do follow-up and due dates send reminders?

Yes. Follow-up and due dates generate email reminders for active users in the same institution.

Are the logbooks institution-scoped?

Yes. Logbook reads and writes are scoped to the authenticated user’s institution, and deletion requires institution-admin access.