These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Schools/Tutoring CRM
- Features
- Tutoring Sessions
Tutoring Sessions
Record tutoring work against an opportunity and move submitted sessions through review.
OverviewMy Session Drafts×
Schools/Tutoring CRM · Tutoring Sessions
New
My Session Drafts
Tutoring sessions
| Session reference | Tutor | Session at | Status | Parent opportunity | |
|---|---|---|---|---|---|
| SR-173 | TTR-160 | 27 Oct | Draft | OPP-60982 | |
| SR-367 | TTR-605 | 16 Oct | Draft | OPP-78183 | |
| SR-339 | TTR-271 | 21 Oct | Draft | OPP-81320 | |
| SR-803 | TTR-263 | 20 Oct | Draft | OPP-65852 | |
| SR-555 | TTR-473 | 25 Oct | Draft | OPP-74216 |
6 of 6 records
SR-173Tutoring sessions · TS-80367
DraftTutorTTR-160
Session at27 Oct
Parent opportunityOPP-60982
What you can do
A session tied to the relationship
A tutoring session belongs to an opportunity and an organization. It can also name the account. The record holds its owner, tutor, session date, enrollment quantity, reference, purpose, revision and status. This keeps the work connected to the school or family agreement that led to it. The session record is where the Tutor describes what happened or is being prepared; the review decision is a separate record made by another person.
The Record Tutoring Session workflow begins with a Draft session. Submission moves it to Submitted, records an independent review decision, approves the session and writes an operation receipt. The status set also includes Rejected and Completed for the session lifecycle. A team should use the review decision and operation receipt together when checking a case. A status alone gives less context than the reviewer, decision date and reason held on the decision record.
How the work is organized
- Draft the session. Connect it to the opportunity and record the tutor, date, purpose and reference.
- Submit for review. Move the draft into the submitted state so the reviewer can evaluate the current revision.
- Keep the evidence together. Link supporting attachments and inspect the decision and receipt after review.
What to agree during setup
Agree what a session reference identifies and how the team counts enrolled students. A learner count on one session should be entered consistently, because Operations Coordinator may later compare sessions across an account. Decide who enters the tutor’s name and who owns the session record when those are different people. The Tutor role can be responsible for the record even if the named instructor changes.
Agree what evidence a reviewer expects before approving a session. A supporting document or note can be attached to the session. The reviewer should be independent of the person who prepared it and should record a reason when returning or rejecting a case. Decide how the team handles a corrected revision: the next decision should be checked against the current session revision, so an old approval is not mistaken for review of new information.
Check the handoff on an actual case
A school completes an exam preparation session. The Tutor creates a draft on the school’s opportunity, enters the date, the tutor’s name, the enrolled quantity and a session reference, then attaches a supporting note. After submission, the Session Reviewer inspects the case and records an independent decision. An approved case carries the Approved status and an operation receipt. Operations Coordinator can compare the session, decision and receipt before using the case in a later reconciliation discussion.
What your team sees
- My Session Drafts — Sessions owned by the Tutor, including drafts ready to submit.
- Sessions Awaiting Review — Submitted work with its reference, date and linked opportunity.
- Approved Sessions — Reviewed sessions the team can trace to their decision and receipt.
Follow the work through
Read session submission and review and the data model.
What it keeps track of
Data model- Tutoring sessions
- Tutoring session records: tutor, session date, quantity, reference number and review lifecycle.
- Opportunities
- A potential deal with an account, used to track its value, stage, and chances of closing.
- Accounts
- A school, district, or family account, used to track who the team sells to and manage the relationship.
- Review decisions
- A verdict on a submitted receipt or session, used to approve or reject it before it counts toward billing.
- Operation receipts
- A logged proof that something happened, like a session or payment, used to confirm work actually took place.
- Record attachments
- A file or link tied to a deal or session, used to keep supporting documents easy to find.
Who uses it
Permissions- Tutor
- Prepares and submits the session.
- Session Reviewer
- Makes the independent decision.
- Operations Coordinator
- Checks evidence across linked records.
Set up Schools/Tutoring CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.