How the queue works

Three keys. Three actions. Three audit-logged outcomes.

a

Approve

Confirms note quality. Note becomes immutable; signature event written to the activity log. Bulk approve is gated by ConfirmDialog with a safety count.

r

Return for revision

Returns the note to the supervisee with reason text. The supervisee sees the request in their dashboard. The audit log records the return event.

f

Flag for discussion

Non-blocking. The note remains where it is, but is marked for the next supervision meeting. Useful for clinical patterns that don't warrant a return-for-revision.

For supervisees

Sign your own work. Supervisor reviews after the fact.

Praxnote's default model lets supervisees sign their own notes, with the supervisor reviewing after the fact in the queue. Practices that need a pre-signature gate can configure it; the model is per-practice.

Why post-signature review is the default

Most practices we've talked to want supervisees fluent in clinical decision-making, including the act of signing their own work. The audit trail and the queue make sure nothing falls through.

Why pre-signature gating is configurable

Some training programs require it. Some licensures imply it. Practices set the gate; clinicians don't have to think about it.

I was clearing thirty supervision items in a Friday afternoon. With Praxnote, twenty minutes. The keyboard navigation alone gave me back two hours a week.
Dr. Patel, Clinical Supervisor, mid-size group practice

See the queue on real notes

A demo for supervisors, on supervisor terms.

Bring (or use ours) a sample queue. We'll walk j/k navigation, bulk approve with ConfirmDialog, return-for-revision with reasoning, and flag-for-discussion. About fifteen minutes.